[/QUOTE]
How does the Bot know when a script is terminated. Abnormally or otherwise?[/QUOTE]

I use a trigger that waits for the last module run to die. This only applies to modes actually. I assume Commands will finish quickly and Daemons you will want to run forever.

Since the modes are generally scripts with long running triggers (citkill, pdrop, etc.) it does an event trigger on the death of the last mode run.

MD

This I will definately be hitting you up about. At least once I get your ICQ and I get home from work. hehe

I hope you have a solution, because it is annoying me to no end.

259922155 ICQ....
glenpacker1552@yahoo.com
TS at vulcansforge-online.net:8767 for voice

It would be nice to get that swath issue fixed.  That has limited a lot of players use of many of the features.
In the help file for the Bot there is also a list of variables that can be loaded into individual Modules.  If you have any suggestions for more let us know.

I would like to hear some feedback on it's use.  This is a beta so we are working out the bugs.  Also if anyone needs some instructional use on the Bot let me know.  I can set up a game on my test server and I can give some pointers on to use it.

The Colo module for the bot had an issue that is now fixed. You can get the new one on grimy in the MomBot package.

Thanks to Fork for the find.

Thanks to Parrothead's help, the advanced menu works great in SWATH.

If you want to use the history feature and edit the command line in SWATH you must:

Create 4 macro's in SWATH called uparrow, downarrow, rightarrow, leftarrow
-----------------------------------
uparrow ^(1c)
down arrow ^(1d)
right arrow ^(1e)
left arrow ^(1f)

Create 4 triggers in SWATH to call these macros and it will now treat the arrow keys the same as in ZOC or any other terminal for the bot.

The new SWATH friendly version is now available at http://www.grimytrader.com or http://www.mindovermattertw.com

I still don't recommend leaving the lightbulb on in SWATH though. heh

Mind Dagger;

Thanks for the info, and to all involved with this Bot. I find this has helped me to learn more about scripts, helpers, and how best to use things and when. I appreciate all the efforts put into this, and am grateful to you all for this.

Too bad this doesn't work to redefine tab (which appearantly can't be assigned?). You can use it in the main window, but triggers work from the comms window too... so if anyone knows a way to make TAB a trigger key that works (I tried editing the .cfg file to key="9", it assigned it to tab... but it still wouldn't load the macro) let me know.

Tab is out but Cnrl+I is also ascii code 9 is that helps any.So Tab then A will work with cntrl+I then A with comm window open. 
Macro(tab) ^(09) trigger cntrl+i = macro(tab) that maintains consistantcy with other telnet but you should be able to assign ^(09) to any key and the Bot will see tab(#9)
These issuses along with the fact that other well known scripts use certain keys is why Im not using Tab Backspace cntrl+c and other windows keys etc.

If anyone wants or needs to fool around with key codes...this miniscript will give you the codes on every keystroke.
http://www.navhaz.com/forums/viewtopic.php?t=52

Yah you can assign ^(09) to a macro and do it from there. I was just trying to assign a tab macro to the tab key, in an effort to override the usual "ignore tab because you're at the comms window and I'm lazy" bug.

Ok no luck with tab key.....keystroke never gets to swath as windows sees 2 windows open with comms window up and uses the key to switch between the two..so code page changing is the only option or a key stroke redirect program..neither solution is very handy or easy to implement.

Yah, I was just hoping for an easy work-around. Can simply do the macro approach I suppose.

Unfortunately that is the problem with using swath.  In Zoc there is never an issue with the tab key.  MD talked about making it configurable but in Swath finding something that is quickly accessable just wasnt feasable.  In earlier versions of the bot we were able to load up traitors comm watch but that got lost somewhere along the way.  Will have to re-add that in.