|
Pyron Beginner
Joined: 11 Mar 2003 Posts: 19 Location: USA
|
Posted: Sat Mar 06, 2004 6:47 pm
Zmud Closes on a Whim |
Running Zmud 7.03 and I'm having a problem. Zmud just up and closes on me all the time. Most of the time it's when I'm doing something in another window. I'll be surfing the web or something, and go to click on zmud in the taskbar and the entire program is gone, it just up and closes. Any suggestions on why this would be happening and how to fix it would be nice. It really is rather annoying.
Thanks |
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Sat Mar 06, 2004 11:55 pm |
This happens in Windows when an application "blows up" it's memory stack. In zMUD, you can blow up the stack with a trigger loop. For example, if you have a trigger that does a #wait, then another line triggers another #wait while the first one is still active, and so on. That can lead to a huge set of triggers waiting for something to finish and might exceed the memory stack in Windows.
Or, a 2-way trigger loop where trigger A causes trigger B to fire and trigger B then does something to cause trigger-A to fire again can lead to an infinite loop and crash like this.
Since it's almost always a trigger issue, try turning off your triggers and then turn them back on one-by-one to determine which one is causing the problem. |
|
|
|
Pyron Beginner
Joined: 11 Mar 2003 Posts: 19 Location: USA
|
Posted: Sun Mar 07, 2004 10:04 pm |
Well, I have a lot of triggers that use #wait, because we have a 2 second delay between rounds. I've never had a problem with it before, and I'm using the same trigger set as I had been using with 6.x. I guess it's time for a trigger overhaul. Also, thanks for your help. I'm thinking one of my newer triggers was just poorly coded and your reply made me think about the exact one.
|
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Thu Mar 11, 2004 4:36 am |
Read the article in the Support Library called Timers, Alarms, and the #WAIT command for a description of better ways to perform delays instead of using #WAIT. On an event-driven operating system like Windows, doing a lot of #WAIT commands can really mess things up. You definitely want to re-do your triggers.
Also search the forums for "Roundtime" to get ideas on how other users have handled this on MUDs like Dragonrealms. |
|
|
|
|
|