smitchell
not so random... what do you mean?
As a rule of thumb, if you end up with repetition of code, you're doing things wrong.
here is how you properly do things
arrowGame.capx
Develop games in your browser. Powerful, performant & highly capable.
revealGhost.capx
need the canvas plugin
wallHugMovement.capx
You can make a layer visible or invisible by event (:
fixedHoodie.capx
nest the 4th event under the 3rd event
Didn't you try what I wrote ?
+System: For "groundX" from 0 to worldWidth Local variable pickUID=-1 +System: For "groundY" from 0 to worldHeight ->System: create object item on layer 0 at...... ->worldArray: set value at (loopindex("groundX"),loopindex("groundY") to 1 ->System: set pickUID to item.UID +worldArray: value at(loopindex("groundX"),loopindex("groundY") = 1 +item: pick instance by UID pickUID -> item:set animation to 3
Two remarks:
1/ As far as I know, the item created is picked only in the action block in which it is created. In the next event only the picking by condition is used.
2/ 'Current value' as well as 'Current X', 'Current Y' and 'Current Z' should only be used in an 'Array foreach element' loop. That's what the "current" is about.
I would probably do it like that
fadeDissolve.capx
also I can't download your capx
You do not have permission to view this post
Member since 31 Dec, 2010