Reply to Pixel problem! (solved)
If you don't have an account, just leave the password field blank.
Imagine two sprites with similar scripts attached to them named e1.c and e2.c, both are exactly 50x50 pixels large.
I place these sprites exactly next to each other in the editor, x-coord.
I use buttonon and buttonoff on both of them, like a pressure plate thing. When Dink stands on top of one, the sprite's frame will change and when Dink leaves it, the frame changes to something else. It is just like the mouse pointer in the menu, but Dink is the pointer.
When Dink walks over the first sprite, e1, from the left, the frame changes. BUT if Dink positions himself riiiight on pixel 50 in x coord, e2 will call buttonon!
e1 won't buttonoff until Dink is on pixel 51 which makes sense. But why does the other dang e2 buttonon at pixel 50 when it is located one pixel away from e1?! Any ideas on why this is happening? It works if I nudge e2 to start at 51, but I don't want that gap.
I haven't tried to work around it yet as I ain't able to do it right now, but any other solutions are welcome.
I place these sprites exactly next to each other in the editor, x-coord.
I use buttonon and buttonoff on both of them, like a pressure plate thing. When Dink stands on top of one, the sprite's frame will change and when Dink leaves it, the frame changes to something else. It is just like the mouse pointer in the menu, but Dink is the pointer.
When Dink walks over the first sprite, e1, from the left, the frame changes. BUT if Dink positions himself riiiight on pixel 50 in x coord, e2 will call buttonon!
e1 won't buttonoff until Dink is on pixel 51 which makes sense. But why does the other dang e2 buttonon at pixel 50 when it is located one pixel away from e1?! Any ideas on why this is happening? It works if I nudge e2 to start at 51, but I don't want that gap.
I haven't tried to work around it yet as I ain't able to do it right now, but any other solutions are welcome.
