I have been using Makecode Arcade in my classes for over a year and I am delighted. For a few months, every time we open a game that has already been created and we are going to edit it, it is very common to find that the game does not load because it detects an error in the control block, like this:
This error always happens to us with Google Chrome (Edge works fine), and to fix it in chrome it is enough to delete the block and insert it again. The issue is that in classes with many children it is not so easy for them to change this block if they have never used the platform, and using edge in some schools is not possible for us.
If you hover your mouse over the black warning triangle it will show you a pop-up with the warning message in it. What does that say? BTW, some types of window image capture can fail to get those pop-ups.
I see, this is an issue with the translation in crowdin for the on button pressed block; the translator reordered the variables on a block that does not currently support that due to legacy issues
(if anyone seeing this has experience with authoring blocks, this is the main reason for the change from using % to $, since with the new behavior for $params we are able to support reordering the values but it required breaks in behavior to support it - in this case, the two parameters are getting swapped when changing languages, producing invalid blocks. We added some logic to detect and reject these blocks when we ran into this before, and in this case it’s actually correctly getting rejected in beta due to a fix for a similar issue in micro:bit)
In this case, the issue is popping up when you switch from spanish translation to english translation in a new browser session (probably cookies being cleared) – if you switch back to spanish they should work again.
I’ll need to poke at this a bit to see how we can handle this issue for now in a way that ideally doesn’t break existing projects when fixing it
@apares8 I have pushed out a release that should fix this issue; you will likely notice that the translation for this block is no longer applied in the new version, as that will need to be retranslated correctly on crowdin before it goes out again (e.g. link in previous post).
It’s possible that the issue might occur one more time when opening up their previous projects now; I added some upgrade logic to try and fix it but that only works if it can be detected. For that to apply you’ll want to make sure they are in the correct language before loading up the project, and hopefully it’ll be fixed & ready to go with no more issues. Thanks again for pointing this out!
