Reply to Re: ok, lets have a poll, for tnh with buttons
If you don't have an account, just leave the password field blank.
: F5 quicksave
: F6 quickload
: F8 dinkspeed menu, it makes dink go slower if you have speed problems
: should I use them, or change them. I need to know, btw,
: quicksave and quickload are enabled when you kill a boss in tnh, this will get rid of those nasty and expensive, space using savescrolls!
First of all, quicksave and quickload could cause more problems than they solve. For example, say you're fighting an enemy and press the quicksave key. You die. So you press quick-load, and the enemy has full health and is in its original position, not where he was when you saved it.
And more problems could happen when (if) you have other scripts running in the screen, and saving/loading kills them. And during boss battles quicksave would be horrid.
You could, of course, check to see if there are any enemies that are alive on the screen, and refuse to save if they are. But, the 'time' of the save game is added if you quit the game... so it is feasible you could quickload the game after quitting and end up having a slayer right on you, killing you.
As for 'F8 dink speed menu'... what exactly does that solve? Besides a few cases where people can't play Dink or any D-Mods thanks to speed issues (and are therefore unlikely to play TNH), Dink's speed is automatically adjusted depending on a variety of factors. While sp_speed() seems to be more questionable, Dink's actual speed fluctuates quite a bit, so Dink speed 3 for me is most likely the same for you too, even if sp_speed(&x,2); may not.
: F6 quickload
: F8 dinkspeed menu, it makes dink go slower if you have speed problems
: should I use them, or change them. I need to know, btw,
: quicksave and quickload are enabled when you kill a boss in tnh, this will get rid of those nasty and expensive, space using savescrolls!
First of all, quicksave and quickload could cause more problems than they solve. For example, say you're fighting an enemy and press the quicksave key. You die. So you press quick-load, and the enemy has full health and is in its original position, not where he was when you saved it.
And more problems could happen when (if) you have other scripts running in the screen, and saving/loading kills them. And during boss battles quicksave would be horrid.
You could, of course, check to see if there are any enemies that are alive on the screen, and refuse to save if they are. But, the 'time' of the save game is added if you quit the game... so it is feasible you could quickload the game after quitting and end up having a slayer right on you, killing you.
As for 'F8 dink speed menu'... what exactly does that solve? Besides a few cases where people can't play Dink or any D-Mods thanks to speed issues (and are therefore unlikely to play TNH), Dink's speed is automatically adjusted depending on a variety of factors. While sp_speed() seems to be more questionable, Dink's actual speed fluctuates quite a bit, so Dink speed 3 for me is most likely the same for you too, even if sp_speed(&x,2); may not.
