Reply to Re: trouble with void touch proc.
If you don't have an account, just leave the password field blank.
You wanted to know why you have to add sp_touch_damage? I didn't really understand what you where trying to say but I'll explain that (If that's not it try to make your question clearer).
sp_touch_damage gives a value of how much a sprite will hurt dink upon touch, and is 0 by default. Touch damage of zero means that it wont hurt dink upon touch; it wont even check it for touch and therefore it wont run void touch(). With a value of -1 however the sprite will not hurt dink but still check for touch. DinkC is designed this way because the game would run to slow (maybe not run at all) if the engine had to check if dink is colliding with everything all the time.
If you didn't wait before resuming the touch damage it would call the void touch all the time over and over again and the game would crash (I think).
sp_touch_damage gives a value of how much a sprite will hurt dink upon touch, and is 0 by default. Touch damage of zero means that it wont hurt dink upon touch; it wont even check it for touch and therefore it wont run void touch(). With a value of -1 however the sprite will not hurt dink but still check for touch. DinkC is designed this way because the game would run to slow (maybe not run at all) if the engine had to check if dink is colliding with everything all the time.
If you didn't wait before resuming the touch damage it would call the void touch all the time over and over again and the game would crash (I think).
