How would you feel about a helper that continuously and automatically commits changes to its database? I.e., no "save" option in the menus, as the database is always saved.

The only real drawback I can think of would be accidentally logging into the wrong game, and I will have it recognize this and stop collecting data. It'll parse what game letter you went into and automatically check the start date on the * screen.

Thats the way twx works.

H

Yeah, logging into the game with the wrong dbase happens all the time.

Here's an idea, have the helper "read" the game letter & name as you enter the game. If it's does not match the one stored when you first enter the game, then abort logging in with a message back to the player to load the correct dbase.

Continually saving is great, but not getting them mixed up is even better.

Now I'll let the cat out of the bag on keeping your dbase from corruption due to entering the wrong game as my login script does.

First time in it checks for a .cfg , if it does not exist it checks the * at the t-menu .. then will log in and create a .cfg of what it seen or captured.

Now next time in game if it sees "do you want to start a character" or something like that .. it disconnects , this keeps dbase from getting hosed.

Now if you get dropped and a script trys to log you into wrong game , the login stops all running scripts .. this also helps.

The only way that it is possible to get into the wrong game is to play 2 games on the same server and by luck or lack of .. that a script could shoot you into that exact game.

But in my experiences , this has not happened to me yet.

My login script has taken all the possible accidents out of the equation ..

But a helper with this and auto mapping would be nice for the returning player base.

Keep up your work , it will be appreciated

The best solution is that if multiple helpers had all the game info on the same setup. Unlike TWX that does not have a listening port tied to the game and Swath tries to hit a listening port and you changed games. That's what causes most all DB corruption.... IMO

Auto updating is the best way since people play for days and tend to forget to save the data before exiting or an ungraceful disconnect

Here is a piece of code that will tie twx listening port to a game.
It is used when you have multiple twx's open and want to insure
not to mix them by accident.

Based on a conversation I had with Toyman and listening ports.
Add this to your login script and all is well.

But what does any of this TWX stuff have to do with his opening post?

I'm for continuous saving, Keep up the good work Mongoose.

I'm sorry for the thread hijacking ...

I could not find the original thread about the twx and UUID things about keeping from getting corrupt data.
I also could not find the post where I put up a 2 line code to show how to locate the twx listening port.

So I continued the thread here where it was talking about corrupt data in hopes to further helping others in the prevention of such things.

But if all we were to answer was for Auto Save feature ..
Swath & twx (which are the most used current helper programs)
Swath asks for user intervention and twx does auto save.
So having a new helper software auto save , once it can detect and prevent data corruption , would be nice ..

For now though , having the user decide if they want to save date (once they KNOW) they did not pick up false data though say the Swath Sync
or TWX Sync or KNOW for sure they have NEVER been in another game , has been our best option.

Vid