I'm uploading what I have so far. This works but hasn't been debugged yet. It's actually 2 scripts and 1 script help file.
These are scripts that allow a CEO to change the subspace channel of his corpies that are running mombot without sending it over the current ss channel.

1) ss.cts (receiver script that is a bot command and goes in the mombot/commands/general directory of each mombot user on the corp)
2) ss.txt (help text for ss.cts and goes in the mombot help directory)
3) sschange.cts (sender script, ran by 1 person on the corp that wants to change the ss channel. Script goes in the twx/script directory)

Note: These scripts do require the mombot "all" command for subspace change excecution otherwise the data will have to be sent by hand for anyone
using a version of mombot where the "all" command is N/A.

Download below:

http://mysite.ncnetwork.net/resvekox/SSChanger.zip

These scripts are dedicated to HHT 2010.

that's a positive note.
good work, Big D

The all command is the problem.

How do u change when someone is offline?

Sounds like the easiest solution is to make the "all" and other multiple player commands not respond to players who aren't logged in to the bot. That way the other team trying this tactic would at least have to know one of the bot names for it to work. Not much point in letting a person who isn't logged in yet have access to the all command anyways.

Probably a better solution out there, but that would be a very quick and useful change.

MD

That's what we did. Changed the all command and fixed the private hail bug.

That becomes a problem if you know their botname, but it's rather easy
to change your botname to something the other corp wouldn't know.

That'a a problem that needs to be addressed in mombot. I just make a script that will change SS channels if it is comprimised.

I understand the need of changing your SS when you find out its been compromised.

I dont understand the point in a script that will automatically change the SS, say, every hour or so.. ??

IF a corp wants to scan for your SS.. I guess they can do it quick by putting out (for example) the "all" command and listening for a quick response. When the bots are corrected from this even happening.. I guess the SS trollers will have to find something new or go back to the old change SS scan & wait for response when they might think a corp has some chatter.

In which case... the other corp will not even know their SS has been compromised.

Now.. even though the corp might have a bot that changes their SS automatically every so often... the other corp may have picked up your SS soon after the auto-change and has been listening for almost an hour (example).

So.. now your bases have been exposed just the same way they had been previously.

So it seems like the best answer would be to make/change scripts to where they dont spit out "useful" information like where you are or where you are running a script from etc etc. Usually there is no need for a sector to be sent out over SS. Saveme sure.. but who usually needs to 'call' for saveme from their base??

Changing the SS on the regular will probably help.. but it seems to me that it wont solve the problem.

What about corp encryption on ss?

Yes Legion. I just made that script because without a plan and everyone at the keys you can't effectively change the SS channel. You can't bot them to change because you'd give them the new ss channel.
The problem is with mombot allowing someone NOT on the corp to recieve any message at all by using the "all" command. I do like the "all" because it can bot the entire corp, but it shouldn't respond to off corp players at all.

Also, it would lessen the chance of somone gaining access to your SS if you changed the SS before you ran scripts like Rammars SDT that spit out continuous SS messages and then change back again when that script is done.

You are correct though, the issue won't be resolved until mombot is fixed and released. That's not my script to fix, so I was just trying to make the best of a bad situation.

Just fix the private hail thing in your bot. Then ppl
can send commands over privmsg if they're logged
in.

I've already fixed several things in mombot. I don't have a problem. It's not my script to fix and release to the general public, so I released a script that was mine until these problems are fixed by the appropriate person and released to the general public. I believe at this time it the rights to mombot were given to Lonestar.

Mombot is no longer supported D. We are like stbot now. Everyone has there own hacked up version.

Removing the "not logged in response" was the fix i found. Whether or not they are logged in there will be no response to bad commands.Therefore the Crawler becomes useless without mimicking the first six letters in a logged in corpies name.I have never used Mombot myself but it is fairly simple in its main code.I also fixed the login bug, exit enter bug , and several others in my copy to hand out to others who wanted it.

The problem with CN6 commands is that the next Helix-like step is flooding private hail with spam.
I mean there is no "rule" against it in the game right?So SS changing every hour in combination with no response bug destroys the ability of the crawler to find your SS except by blind chance. I also removed the "all" command because it is of no value and I never found a real use for it.