It maybe a bug, but you need to believe, using UID or IID is not a big deal, specially because what you discovered was cited on these tutorials as a knew issue (and I suggested this read about 2 times for you on this forum, take a time and read tutorials, not only these, on the tutorial section have many good and helpful tutorials.)

@Asley: i bumped because this could be a base bug in the uid system, which 'could' have priority. and if so, i can not continue my (simple) project because this old uid object instancing feature. (so glad c2 currently works on my laptop, and got some time ^^ )

Should i wait for feedback before continue working (and trying to fix) on the project?

PS: I think a status indicator would be useful for any bug-report, to get feedback about its relevance, and if you are working on it. Some people are using c2 in a productive environment, and dont have weeks time for eventually getting an answer

@telle: i've been reading this stuff long ago, if i could understand why the uid's does not work in this project, i would not have had posted Please download the capx, and try yourself.xeed2012-12-19 18:54:57

It's not a problem with UID, it's your events. Two things. When movementDirection = 2 then event 8 changes it to 1 and then event 9 changes it back to 2. So the enemy will turn right but never left. You need an else in there.

The other problem is in event 6. When the enemy is overlapping the object or standing next to a wall the change direction function gets called repeatedly. Every tick you'll be switching directions until you move away. So you need a trigger once in there.

For event 9, how can i leave the function instead of adding the else condition?[/quote]Don't think you can.[quote]and for event 6, i guess a "wait" action should fix this too, right?[/quote]Nope with wait you'd just be queueing up many function calls to happen after x seconds because the event is still going to run every tick. [quote]at least, do you know why the enemy UID kicks up this way?[/QUOTE] Not sure what you mean about the enemy UID. Every object has a different UID, every sprite, text object, etc. You have 55+ objects in your layout so it's not surprising that the enemy UID could be 55 or 56.