I am actually wanting to learn to correct scripts that i have... Please help

Trigger dump for script: C:\Users\Josh\Desktop\twx5\Scripts\Mombot\__mom_bot3_1034b.cts

Text Triggers:
SECTORDATA = [:CHECKSECTORDATA, "(?=Help)? :", ""]
ONLINE_WATCH = [:ONLINE_WATCH, "Your session will be terminated in ", ""]
Text-Line Triggers:
GETSHIPOFFENSIVE = [:SETSHIPOFFENSIVEODDS, "Offensive Odds: ", ""]
GETSHIPMAXFIGHTERS = [:SETSHIPMAXFIGATTACK, " TransWarp Drive: ", ""]
FEDERASE = [:FEDERASEFIG, "The Federation We destroyed your Corp's ", ""]
FIGHTERSERASE = [:ERASEFIG, " of your fighters in sector ", ""]
WARPFIGERASE = [:ERASEWARPFIG, "You do not have any fighters in Sector ", ""]
GETPLANETNUMBER = [:SETPLANETNUMBER, "Planet #", ""]
OWN_COMMAND = [:CHECK_ROUTING, "com", ""]
OWN_COMMAND_TEAM = [:CHECK_ROUTING_TEAM, "all", ""]
LOGINMEMO = [:LOGINMEMO, "You have a corporate memo from ", ""]
CLEARBUSTS = [:ERASEBUSTS, ">[Busted:", ""]
Text-Out Triggers:
USER = [:USER_ACCESS, ">", ""]
UPARROW = [:USER_ACCESS, "", ""]
DOWNARROW = [:USER_ACCESS, ", ""]"]
DOWNARROW2 = [:USER_ACCESS, "", ""]
TABKEY = [:HOTKEY_ACCESS, " ", ""]
RIGHTARROW = [:HOTKEY_ACCESS, ", ""]
RIGHTARROW2 = [:HOTKEY_ACCESS, "", ""]
LEFTARROW = [:HOTKEY_ACCESS, " ", ""]
LEFTARROW2 = [:HOTKEY_ACCESS, "", ""]
Delay Triggers:
KEEPALIVE = [:KEEPALIVE, 30000]
Event Triggers:
SHUTDOWNTHEMODULE = [:SHUTDOWN, "SCRIPT STOPPED", "scripts\MomBot\Modes\Resource\pimp.cts"]

Trigger dump for script: scripts\MomBot\Modes\Resource\pimp.cts

Text Triggers:
Text-Line Triggers:
Text-Out Triggers:
Delay Triggers:
Event Triggers:
DISCOD1 = [:DISCOD, "CONNECTION LOST", ""]
DISCOD2 = [:DISCOD, "CONNECTIONS HAVE BEEN TEMPORARILY DISABLED.", ""]
Waiting For: "Average Interval Lag:"

Am I missing something .. like where is the question , what is the question ?

Sorry, Sing, I accidentally edited your reply rather than quoting it to respond. I'll see if I can restore the post, but I may not be able to. - JP

ok , the new v202 has been returned to that original trigger.

What others have done is have 3 triggers to cover the servers they play on
or as a stop gap .. made a macro to send ave interval lag trigger on sub space.

I for one am glad that is resolved for those who have .cts only.

Works like a charm =-)

It might change, depending on what future OSs there are and whether or not TW ever gets compiled into 64 bit (not likely). As all current supported windows versions are derived from NT, the "Windows NT" identification will be consistent. However, if some new branch of Windows OS comes out that can't be properly identified as NT, I may change that to properly identity the OS on which it's running.

As a general rule, it's a bad idea to script on things that are meant to be reports of hardware or software system status. The best things to script on are gameplay-related. As long as the gameplay doesn't change, those triggers won't change. I've never guaranteed that things like copyright notices, system identification, processing metrics, etc, won't change. But I rarely, unless there's a very compelling reason, change game-related output. The addition of a digit to planet # comes to mind, but that's a bug, not a cosmetic change. The display needs to support the number of digits allowed for a planet.

Would it help to add a global that's intended specifically for this use? That won't help past scripts, but future scripts would be more stable in the face of changes to operating systems and underlying engine details.

Well, if it changes 5 years from now, I'll worry about it then.

And I'll get my butt chewed over it ;)

Haha, probably.

But yeh, if you want to add another command like #145, something that replies back a unique string, that would work too. Like if someone sends #178 and gets #179 #180 #181 back or something.

If we wanted to use a typeable character, _ is available.

Since it's mostly a script or macro feature, that probably doesn't matter. But either way is fine.

I could also put a title on the @ screen that isn't going to change. Something like Server Details. That'd be simple enough.

Well John , I'de say stop and save yourself some time to work on something else ..

Because you've already fixed the Average Interval lag trigger key in
3.15 , so those who have 1.03 or 3.15 up will be ok ..
I don't think that those who are running anything in between will be doing so for very long now that 3.15 and 3.16 are around the corner ..

By far these are the best yet ...

So as I see it .. that issue is done , and you might be kind to to all
by keeping a post-it ® to note never change that ...
Why make more work and separate this version from past versions.

my 2¢

Speaking of which, how is the new log viewer working? Any more crashes?

I love it , it keeps the ticked option for hide inactives , it will start in current selected .. it loads one at a time ..

no crashes and I really don't expect any either ...

Good job