Discussion Changing depth causes unexpected behavior

[psyke]

So, I found something that is really bothering me, it might be a bug, I don't know.

Look at this code:

This code creates a new enemy and attachs it to the monster from the top, as you can see in the screenshot below:


Everything was working fine in GM 1.4, but when I ported my game to GM 2, this error started to happen:



This is the event where the error happens:


If I remove the line: "Load.depth += 1", it stops causing the error.
Sorry if I was not clear, this is something really strange and I don't know what is happening.

 

[Tthecreator]

If you remove the line "Load.depth += 1", then is the variable Corpse at line 6 inside gmlObject_objUnit_other_10 still equal to -4?

 

[psyke]

If you remove the line "Load.depth += 1", then is the variable Corpse at line 6 inside gmlObject_objUnit_other_10 still equal to -4?

Man, I think you nailed it.
When I started reading your comment, something came to my mind:

If I change the depth of the monster, it will move the instance to a temporary layer (with NO NAME).
The Corpse uses the LAYER of the Owner, I think that's why it's causing the error. I will try to create the corpse using DEPTH instead of LAYER.

 

[Tthecreator]

@psyke Yea, I've also had problems porting over some stuff to the new way depths work, but got it running eventually.

Just let me know when you fixed it!

 

[psyke]

@psyke Yea, I've also had problems porting over some stuff to the new way depths work, but got it running eventually.

Just let me know when you fixed it!

Yep, that was the error after all:


I replaced the AddObject function to a new function called AddObjectDepth, instead of passing the layer to the Corpse, it passes the depth. Now everything is working fine =)