In an attempt to wrench things back to subject:

Thank You for offering to put out an updated version!
Is it possible to have a less aggressive relog? I seem to
get my box locked up trying to relog to a dead server.

I have been meaning to do it myself, but if I can get it
included in a new version of the bot, and get this topic
back in the Christmas spirit...

Nice gift idea TBH!


ps Stone, start your challenges in Open Discussions if you
absolutely must.

I am taking a look at that. There is a major problem when the server disconnects you. The fix of the goto/gosub is going to take a little while to hammer out but I will get it all fixed.

What would be nice is the ability to turn off the prompt banners for [Busted] and [MSL] on the command prompt. Now I just rem out the lines in M()mbot

H

Why would you want them turned off? Just asking cuz I think that is pretty important info. I can put that in as an enhancement later on though.

I agree you TBH, I see no reason for that to be changed.

Since I play a lot of unlims, I find the banners annoying sometimes, but purely from a cosmetic point of view. Occasionally, I do find them useful (especially MSL), so I wouldn't want to just comment them out.

I think adding an option to turn them off isn't completely pointless, but I'm sure there are a lot of other enhancements that would take priority.

qset sometimes causes mombot to crash. Is that a bug you're already aware of?

It totally makes SWATH go nuts

H

Oh, that's right, that's what makes swath think there's data corruption?

No, had not seen or heard any issues with qset. If you have more infor on error/situation and/or screen shots or logs that would be great.

I don't use swath for anything more than the visual mapper so never run into this. When you say go nuts, can you elaborate a little?

I dont use swath either other than for mapping.. but.. many times I do see [BUSTED] & [MSL] splattered across the screen in Zoc.

As an example, running wsst or any gridding script, the banner causes swath not to update the sector info in swath.

H

Oh, it's not as bad as I thought. I could have sworn it was crashing when I used it properly, but I can only reproduce a bug now when I use the command incorrectly. So for example ">qset a 33000" brings the bot down because 'a' is not a number. This would be a low priority bugfix. Actually, if you want I can help out by submitting the fix... I didn't look yet but I'm sure I just need to look at :qset and add a isNumber check and an error message and whatnot.

Btw 3_1036 is the latest version, right?

What about the clearscreen effect that adds pages of blank space to my local history when using the local commands... is there any way to get rid of that?