I'm targetting the July 4th weekend to release a new build of TWX. I'll be reviewing past feature requests, trying to decide what I can reasonably get done between now and then. I'm also looking for new feature requests (or reiterating past requests) so post them here. Just remember that they'll be weighed based on usefulness and difficulty to implement.

Also, I know that a few people have rolled their own builds of TWX, so if you have changes that you'd like me to incorporate, bring them to my attention via email please. I'm not promising anything, but let's see what we can work out.

+EP+

One thing I would still like is that TWX would recall the "listening for connections on port" from the game DB. When running multiple instances of TWX, you have to make sure the port is correct and not "left over" from a previous setting. This would be the same as what SWATH does and part of the game settings.

               / Promethius / Enigma / Wolfen /

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

Nod. Would it be difficult to, instead of popping up a msg box, auto-increment the port number (mebbe by a random number between 1 and 5) and checking again? Up to a max of say 5 attempts?

Hey EP. here's a few of my wish list items:

Would like to be able to limit variable dump to a specific script, or perform a dump to a Text File

Ability to Delete SectorPArams

Limit GetNEarestWarps to 'n' Hops from a T.A.

SetANSITrigger ..or.. SetTextLineANSItrigger

When viewing the History msgs: Fed/SS msgs, etc.. would like to be able to see Limpet hits and server msg's if possible.

would like to be able to addmenu to "TWX_MAIN", and not have the script terminate when '$' is pressed (see reference)

Having the listening port in the database is almost fully implemented for the next version, and will be included unless I run into some nasty snag.

LS, I think those are great suggestions, though I may hit you up for clarification on the history msg thing.

The suggestion of limiting getNearestWarps is a good idea, and has been mentioned before. A satisfactory change has to remain simple though. I would love to have a process that further simplifies searching, as many still don't grasp how to perform a BFS using getNearestWarps. I imagine this method as a criteria specification followed by a search for said criteria, like:
setCriteria $criteria1 ((SECTOR.FIGS.OWNER="yours") OR (SECTOR.FIGS.OWNER="belong to your Corp"))
getNearestWarps $warpArray CURRENTSECTOR $criteria1

That just doesn't seem much simpler to me. I could hardcode a few static criteria though, which might help, like PORT=xxB or OURFIG=true. That could get complicated quickly though.

I am planning on adding SECTOR.PARAMCOUNT[sector] and SECTOR.PARAMS[sector][index]. The ability to delete sector parameters makes sense also.

getNearestWarpsIn is really needed as well.

Right-Click on TWX icon in System Tray, select: View, and then History. Far as I know, there are no indications of Limpet/Armids Hits, as well as Server Msg's (i.e.: Shutdown, general announcements, etc)

Speaking of shutdown msgs.. could there be an EVENTTrigger that captures that?

[EDIT]
How about also Global Variables similar to STARDOCK/RYLOS/etc.. like: BSS, SSB, SBS, SSS, etc. cause I can never remeber the Class Numbers above zero

Well, I have kind of a cross between a bug fix request, and a feature request.

When importing warp data from a text file, can we have a check box to force TWX to overwrite the database with the imported file? This option would be useful for rebuilding partially damaged databases.

Right now, from my observations of version 2.04, non-date-stamped imported data is treated as "older" and ignored if an entry in the database has a date stamp. This may be a bug, or a "feature" I don't know.

The issues comes up, when my TWX database's sector warp data becomes damaged. I am yet unable to track the cause of the damage, as it happens too infrequently. Running a ZTM, or exploring/e-probing the effected sectors and pulling the warp data CIM will fix the database, but these can take a lot of time. I have in the past had to resort to reverting to a backup copy and even rebuilding the database from scratch.

This issue may be moot, as you may have already fixed many of the underlying problems, but I decided to bring it up anyway.

P.S. Thank you very much for all your work on the new version of our beloved TWX!

import portspec data.

Here is something that has been asked for or thought of in the past :
a way to Set/Check Auto Relog
so it can be toggled on / off and check status of the flag.

This can be accomplished as follows:

Note: This works because this value is toggled when the menu is opened. The 'FALSE' at the end of openMenu prevents the menu from pausing after opening, so the closeMenu occurs immediately. This technique will not work for a menu item that requires user input, like TWX_LISTENPORT

+EP+

Is there a good way to turn off the login script by another script? I've forgot a few times to uncheck it after logging into a game and it would be nice to be able to prevent its running after a drop. I don't like putting in delays. I guess I could just rewrite my relog script and replace the normal login script if there isn't a way to toggle this.

               / Promethius / Enigma / Wolfen /

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

There is no good way, though you might watch for the login script to load by using an event trigger, then kill it when it loads.

I decided just to set my relog script to save a var $relogActive to 1 and have the normal login script check the value and if it is 1 then halt.

               / Promethius / Enigma / Wolfen /

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

How about functions? Twx code is a big mess without them. Or am I missing something? Is there some way of passing variables around?

I suppose this is difficult to implement, but it would also be extremely useful, I think.

Also, coding with GOTO kind of sucks... very difficult to figure out what's going on. How about some flow control structures?

Hehe... functions.

If no functions, how about a stack?