I pushed a fix, so now if a new scene is created, a new corresponding zoom renderable will be associated with it (initially undefined, but it will get defined if a zoom block is used, making a new scene essentially have the zoom extension reset). Now, since the zoom renderable corresponds to the current scene, that means that if you pop a scene, the popped scene’s renderable will be destroyed along with it, and the old zoom layer will still be there upon returning to the previous screen.
To upgrade the extension, simply go into the javascript menu and click to open the Explorer, then scroll down to the extension and click the version number. It will then update it. The old version is v2.0.1 as shown below, and the new one is v3.0.3.
In the process of fixing this, I cleaned up stuff and made the extension mostly self-contained within a namespace (the enum is still separate to keep compatibility, so changes to the code of programs do not need to be made). So variable names and such within code should no longer conflict with the extension’s code.
Ok yes thanks @teaeat100. For any games you have made remember the 1:1 resolution ratio, please. For example: 1f you have a game that is 160x160, great. If the game is instead 160x120, like the normal screen, set it to the bigger number, please.
For shield points, we need to add an icon for it. Once I finish working on it, I’ll send an image. Also, we need to note down the value of Shield Points. For example, getting 10 shield points for each hard achievement would make 60 shield points worth a lot. If getting 200 shield points for each hard achievement, we might as well consider 1200 quite a lot. Hope this brings more ideas.
I Lost The LinK And Forgot To Put It, I Dont Have It 
