Hello
I have been sitting on this script for over a year and finally think it might be ready for the masses to use.

I call it AlienHunt and all it does is triggers on Alien Space. It has been successfully tested in subzero games and I think that any game that has aliens with up 2 names should work. It will write to a file named GAMENAME.aliens, sends a SubSpace message and also if you have the ding.wav sound file in your TWX Directory will also make a sound.

I am releasing this in source format because I believe that the source should be examined by anyone who runs the script.

The only guarantee I am willing to put on the table is that it works for me, if it don't work for you; the source is there fix it.

Uploaded to NavHaz's script forum February 18,2007
Enjoy and please don't forget to make improvements.

I used it in another game with aliens, it didnt list the whole name but it still showed sector. ill post it for ya dont think its a big deal, still gets the info you want. Btw thanks posting it.

The in :3326

I think its because of the way they are named.

heres the # screen

Lieutenant Kane [2]

The The Fedz are on the move!
The The Terrorists are on the move!    

and in a subz its this

The Ascian Wanderers are on the move!
The Ferrengi are on the move!
The SubterFuge are on the move!     

I released one on grimys over a year ago and Sing has one on his web site..but thanks

Thank you for the script. It will be most useful for our Corp. Appreciate the work.

Thank you Thrawn

It's nice to have a running detector tho...

I looked over it, here's a quick draft I came up with that's a little simpler.

# -----------------------------------------------
# Quick script to detect aliens as they come in.
# Based on the script by Maniac.
# -----------------------------------------------
systemScript
# -----------------------------------------------

# Set the filename
setvar $file GAMENAME & "-aliens.txt"
fileexists $sound "ding.wav"

# Set the triggers
:set_the_triggers
killtrigger parse_sector
setTextLineTrigger parse_sector :tparse_sector "Sector :"
pause

# Parse it and check for aliens...
:tparse_sector
killtrigger parse_sector
# Check for spoofs - _[1;32mSector
getWord CURRENTLINE $spoof_test 1
getWord CURRENTANSILINE $ansi_spoof_test 1
getWordPos $ansi_spoof_test $ansi_spoof_pos #27 & "[1;32m"
if ($spoof_test <> "Sector") OR ($ansi_spoof_pos < 1)
     # It's a spoof, blah!
     goto :set_the_triggers
end

# Get the sector number
getWord CURRENTLINE $alien_sector 3

# Get the constellation name from the trigger
getText CURRENTLINE $constellation "in " "."
stripText $constellation " (unexplored)"
stripText $constellation "uncharted space"
stripText $constellation "."

# With all of this, is it a particular alien "space" ?
getWordPos $constellation $pos "Space"
if ($pos > 0)
     # It is!

     # Here we make a padding variable. Makes it easier to read
     # the file output by spacing things out better.
     getLength $alien_sector $sector_size
     if ($sector_size = 1)
             setVar $pad "       "
     elseif ($sector_size = 2)
             setVar $pad "      "
     elseif ($sector_size = 3)
             setVar $pad "     "
     elseif ($sector_size = 4)
             setVar $pad "    "
     elseif ($sector_size = 5)
             setVar $pad "   "
     else
             setVar $pad "   "
     end

     # Write it all to the file defined above as $file.
     write $file $alien_sector & $pad & $constellation

     # Echo to screen
     echo ANSI_14 & "**" & $constellation & " found at " & $alien_sector & "*"

     # Play the sound
     if ($sound)
             sound "ding.wav"
     end

# end if...
end

# Set the triggers again.
goto :set_the_triggers

Not sure you need to scan the # (who's online) at all.

Edit: fixed a copy/paste bug.

Sing only reason I used the '#' key was to get the alien names
And I like your changes
Just have 1 question does it trigger on a probe script?

And please excuse this rant ... If I had released this script in a CTS version there would be no chance that Sing can improve it.
I understand that people might want to keep some scripts private and I whole heartily accept that, but to publicly release a script in CTS format is not allowing the general community a chance to fix problems, make improvements and in general goes against the license that TWXProxy 2.04 is now released under.

I apologize for my zealotry about open source but some programs/scripts might only need 1 little fix to make them better or used for an entirely different purpose. Xide used to charge for TWXProxy and therefore he had to "encrypt" scripts that he wanted a chance to make some cash to pay him for his hard work. Now that TWXProxy is free and open to anyone to modify/add enhancements it is in MHO that public scripts should be open sourced as well. Your opinions might differ and I hope that this doesn't develop into a flame war.

Laff... 'sok, it's natural for people to be possessive of their work. I tend to release my public stuff as .ts, and my private as .cts. But not always, and that's just a matter of taste. Sometimes it makes sense not to release everything as a cts so people don't "borrow" your code.

There's no licensing scheme for scripts, the GPL is for twx proxy itself and there's actually substantial precident that the compiler license does not translate to the compiled code it generates. Otherwise everything made using C++ would be open source. My only hope is that any changes to the base twx proxy are passed back up to EP so he can adapt them for public use.

I know you used the # to get the alien names. And that works, to be sure... in most cases. But it's not neccessary to use # to get the alien races since there's another pattern that's more native to the data (all alien races have "Space" in their constellation name). Sometimes the alien space name doesn't match the who's online data.

The revamp I did should work on ether probe, ya. I don't see why it wouldn't.

I agree any people using TWXProxy that have actually modified their code to make enhancements/ or even to make it worse must also upload their changes or make a reasonable facility for the changes to be downloaded for anyone and everyone that wants it. According to the GPL as I understand it is you are free to modify code as you see fit but you are also are required to make said changes available for anyone if you make it publicly available.

Once again thanks Sing for improving my code.

<rant>
Can we get onto IMHO one of the best set of scripts out there (CK's) to release either updates or to open source their scripts? Yea like that will happen
</rant>

Either way, thank you both. It is quite helpful.

Well, GPL is... unenforceable. I mean what are you going to do, get wind of a non-public update, track down the guy and sue them? Good luck... =)

CK has stopped playing. He will not be making updates to those scripts, or so he has said (altho who really knows... lol). There is source code out there, but it's not publically available. It was on the tavern right before it went down, and some people managed to get it. I've read over it... and to be honest, his style is not mine. It would be easier to start from scratch in most cases and that's probably what you'd want to do since the learning process is worth it by itself.

Barring that, ask around and I'm sure someone can send you the source to his public scripts. You'll run into the same problem tho...

Well I fixed Ck's Ztm syntax issue that popped up in 2.04 beta. Afterwards I contacted EP who in turn contacted CK. The response was that he didnt want anything posted that was a rehash of his scripts. I believe I am free to give it out but not post it was the jist of the conversation if memory serves.

Part of the reason for .cts releases is to prevent someone from messing a script up and passing it on. If they leave the author's header in the script then it reflects on the person who wrote it. I have ran into one instance of seeing the corp asset script I released in .ts form being claimed as written by the person I was corping with. It was a bit funny to me - amazing what you can see playing under a different alias.

               / Promethius / Enigma / Wolfen /

"A man who has no skills can be taught, a man who has no honor has nothing."

Agreed Prom New scripts might have bugs to be fixed how do you do that if peeps are messing with it?
 If I release something in TS then maybe ill repost after a bug fix maybe I wont. They are really just for other peeps to mess with so they can see a way of getting something done. (my way not the only way) or to promote conversation on a subject. If someone wants the TS of something Ive posted to see the code or whatever all they have to do is ask for it.

Sorry my work is my work I will do with it as I wish and someother persons statement on a piece of software holds no legal or other sway on me. My scripts are not for sale therfore no contract is in place. The GPL on twx itself deals with the source code EP released not scripts.
There is a reason EPhaggle is timelocked. To allow the author to deal with bug reports from one version at a time only and in the end give us something very nice to use.

Plagerism is not cool.
Adding a new bfs to oz ptrade is fine its still oz ptrade. If peeps want their name on a script all they have to do is write one. Oh BTW Prom love the asset check.

'setTextLineTrigger parse_sector :tparse_sector "Sector :" '
yes

[quote="Parrothead"] Plagerism is not cool.
Yes it is. Havent you noticed all my scripts look just like other peoples? None of it is original.