Is there anything in mombot or any script or way of protecting myself from random CBY's?

I seem to do that a lot on accident.

Swath has a built in protection but , just like the blind warp protection ..
you can type fast and get by it too.

There are several other scripts for TWX that have Blindwarp and CBY built in.
coordinator.ts is one invisible_keepalive.ts is another I don't use either but I know they work unless you type extremely fast.

Mombot tries in it's macro protection, but it has workarounds.

Swath tries, but it can't prevent you from macroing thru it.

And yea, my old coordinator and keepalive both try, and it's faster than swath, but still no real macro protection.

So depends on what you need.

That would be a good player option to add to the next TW release in the CN settings:

(C) Online Auto Flee - On
(S) Self destruct mode - Off

That is "if" JP ever sells or decides to release the code. I'm sure the game will be completely dead before that happens tho.

why not go further?

(B) Blind Warp Protection - On
(F) Fake Bust Protection - On
(M) Mugging Protection - On
(P) Self Photon Protection - On

Personally, I think its better not to protect players from these mistakes. On one hand, I have seen games swing based on mistakes like these. On the other hand, I have often seen teams fail to capitalize on the opportunities that these mistakes create. In the end, without the opportunity to make these mistakes, great players become even more invincible. We should leave some chinks in their armor.

The difference between the things you listed above, is that players will very seldom self destruct by accident unless it's caused by a script error, or by spoofing of a script. Blind warps, dock muggings, and self photoning are no doubt usually a mistake made by the player and should be part of the game.

i disagree. personally, i can't recall how many times i have (or almost have) CBY'd trying to beam to terra from the citadel, not realizing that i was at the computer prompt in the citadel. maybe you're too elite to do that, in which case you wouldn't need the protection feature anyway. i see your point, but respectfully disagree.

Did you just call me elite? No since in starting with the dirty name calling! OK, that does it. Going to have to #SD# you now.

You can if you use ZOC have an auto macro that will send a N when the "ARE YOU SURE CAPTIN? (Y/N) [N] comes up, Or an enter for that matter, It has saved me a few times but I dont know how well it would hold up if you macro'd CBY. I bet Rev probably knows off the top of his head since he is the ZOC king.

Telix SALT is compiled, the following will beat a macro:


main()
{
int int2 = 0;
int int3 = 0;
int3 = track( "ARE YOU SURE CAPTAIN", 0 );
while ( )
{
terminal();
int2 = track_hit( 0 );
if ( int2 == int3 )
{
cputs( "n" );
break;
}
}
track_free( 0 );
track_free( 0 );
}

Pity nobody uses it anymore

LOL. No, it won't.

Oh, and use enter instead of "n" since it clears the prompt, but won't hang if someone hits N at the same time.

The only way to beat a macro (or really fast typer) is to catch the macro before it goes into the buffer, which means to catch it during processing.

As for casual typeage, any number of twx scripts will do the job.

never heard of SALT.

wheres it at?

On your table.

Nah, salt is telix's old scripting language. Kav likes it cuz he's too stubborn to learn twx.

no it won't stop a CBY macro. as Sing has already said, the only way to stop a CBY macro is to catch it before it hits the network.

proxies are well situated to validate macros at least in the simple case where a macro contains CBY verbatim. in order to catch all of the other cases, e.g. CB1123Y, then you have to do a lot more work; the proxy has to shadow the twgs state. then, on top of that, even if the proxy detects the CBY scenario, what does it do with it? take the CB1123Y example. does it send CB1123N or CBN or 1123 or just nothing at all? and how do you debug your scripts when the proxy is dynamically changing your output? nothing about it is simple.