Today I am not giving data on who did what. Today I am going to post something that I, and feedback, have both been saying for years.
If you have a script that will continue unabated, it needs to be changed. The following is my recommendation, and how to do it in either the Wizard or StormFront.
People have scripts that loop back on themselves. They check statuses then go back to some earlier point to continue until the skills are at whatever point people think they should be at. There is nothing abnormal about that, I see it every day.
What I also see every day is people who have placed no check whatsoever on that operation, such that if the phone rings, or something on the stove boils over, or the sewer backs up, the script continues on its merry way, lands the character in the scripting box, and then I am forced to deal with it.
The following will prevent the vast majority of those. At the start of the script section, add a line similar to this:
waitfor ygavsnyrnoadsru
Next, create a macro on a key, ygavsnyrnoadsru\r
What this does is, when the script returns to the beginning for the next cycle of whatever it will do, it requires a manual input from the user, the macro. By doing this, you will be able to look for unusual messaging, or if you are called away, the script will stop, and eventually you would be dropped for inactivity.
This is not a foolproof solution. If the script is very long, it could continue long enough that the pause would not come up quickly enough. Alternately, there is still enough time in the process that it is possible to be warned in the inactive period if you were clearly active. What it will do is make falling asleep at the keyboard much less likely to result in something truly unfortunate.
Sanguious
