Not sure if this is a bug or not implemented yet,
I'll post it here just for the heck of it.
1. Action/Condition that involved layer, doesn't do a double check whether the layer exist on the layout
(except "Layer is Visible" Condition)
To repro, use "MyNewLayer" or layer 30:
System->Compare opacity -> "MyNewLayer" / 30
Mysprite->Is on Layer "MyNewLayer" / 30
etc... try other conditions that involved Layer
System->Set layer "MyNewLayer" / 30 opacity to 0
System->Create object MySprite on layer "MyNewLayer" / 30
MySprite->Move to layer "MyNewLayer" / 30
etc... try other actions that involved Layer
(System -> Layer is Visible seems to work correctly.)
2. Renaming Layer / Group doesn't update all the reference
Casually renaming one of the Layer/Group can break your project without you realizing it. (until it's too late).
This happens to me quite often recently and it's a pain to search for the mistake.
Event 2: Layer "SpriteLayer" doesn't exist
Event 3: Group "MY GROUP" doesn't exist
Develop games in your browser. Powerful, performant & highly capable.
I got bit by the second part a couple times, once was such a big one, I change the name back to the default, and left it.
Speaking of "That does not exist" errors, would it be difficult to have the error offer to create the missing part?
I.E. "That Layer doesn't exist, would you like to create it?" or "That Global variable doesn't exist, would you like to create it?" (or does this promote bad practice?)
Not wanting to bring up an old post, but this post really helped me!! I was having the exact same problem for the second part.
Haha I kept thinking that I must have typed the layer name wrongly.....even though the layer name is Objects <img src="smileys/smiley17.gif" border="0" align="middle" /> Anyway, changed to the layout number and it worked perfectly.
So far, only two events have this problem in my game which deal with that layer. The others work fine though.