Reply to Re: Why Can't I Quit You, DinkC?
If you don't have an account, just leave the password field blank.
My guess would be it has something to do with ¤t_sprite having the wrong value. To debug, I'd start freedink from a commandline window with debugging enabled (or press alt-D until it is). It outputs lots of info to the commandline then, including which scripts are started at which position (counted in bytes, I think, which is hard to read, but better than nothing).
You may also print variable values (using debug() to the console, or say() to the game window (and the console)) to see which parts of the code are being executed, and what the values of the variables are at those times. IME this is the fastest way to find out why code isn't doing what you expect; once you know on which line its values start to deviate from your expectations, it's usually easy to understand why.
You may also print variable values (using debug() to the console, or say() to the game window (and the console)) to see which parts of the code are being executed, and what the values of the variables are at those times. IME this is the fastest way to find out why code isn't doing what you expect; once you know on which line its values start to deviate from your expectations, it's usually easy to understand why.
