For Those that see my other post on vulcan I applogise but I wanted to hit as many scripters as possible.

*Original Message*
Safety: What are some of other scripters approach's to preventing blind twarps, etc without useing a settextlinetrigger?

Security: I know EP uses some form of security to prevent people useing his script past a time he determines. My question is as follows what do others use? And is it as simple as setting a date/time variable and haveing the script referance it on load?

Anti-Spoof: I have seen it mentioned people useing CURRENTANSILINE is a good anti spoof technique? Is that due to in ability without a script to broadcast ansi lines? What other techniques work well outside of that? Ive considered setting textlinetriggers for F and P but I assume thats to universal.

As I'm about halfway through my alpha these concerns are starting to arise as my final objective is to realease a fairly stable version of the script I'm working on while keeping a advanced version to give to corpies that will "Self destruct" i.e. not work

-Kaus
-=-It is also my objective to learn as much as possible for when i move onto more advanced scripts allowing myself the ability to not spend hours on one command lol



Yes that took me over a hour to figure out how to make a multi toggle.. lol

Preventing blind warps WITHOUT a settexttrigger?

Only way I know of, which is something I do... a little, is to update figs at the start of the app and keep a running figlist. This is dangerous however as there are numerous times where the fig can get taken out before you get the hit message, sending you on a trip to fuseland. This is one of the biggest advantages to pwarp-based scripts, you can macro everything.

EP does the expiration to keep people using the most current version. Lots of reasons for that. When I do it it's usually to make sure the script doesn't get passed around outside my control. If I find that new updates are getting passed out just track down from whom.

As for doing all that, yea, it's as simple as getting the system time, stardock value, whatever else and checking it. I got a little include routine, change it and recompile the script. Pretty easy.

Anti-spoof... TWGS filters any non-printable character from the input. So you can't send escape sequences via comms, atleast... to the best of my knowledge. I've never found a way. Easiest anti-spoof is just to check the first word against what it should be. Since 99% of the spoof attempts are w/ comms, beacons, planets, etc. Only problem there would be player name(s) and stuff that is sent thru the first line. There are a few other areas where this can fail, but they're pretty obvious as you write them.

If you want to lock down the rest of the spoof attempts:
http://tw-cabal.com/strategy/twxansitricks.html