DS Account Manager

Yes this is a replacement for IonCross; it also includes some features found in CheatersDeath, FLPlayerCleaner and FLStat.
It is also similar to Biocross but it is a lot easier to install and offers more features.

We’ve been using it for about a year and this is the latest version.

I expect that this version will have bugs but it is completely usable. I’m releasing it so that I can more quickly find the remaining bugs as the bug reports from the server operators I know are using it have more or less stopped.

EDIT: See the Readme.RTF in the download package from a more complete description of the features.

Yes this is a replacement for IonCross; it also includes some features found in CheatersDeath, FLPlayerCleaner and FLStat.
It is also similar to Biocross but it is a lot easier to install and offers more features.

We’ve been using it for about a year and this is the latest version.

I expect that this version will have bugs but it is completely usable. I’m releasing it so that I can more quickly find the remaining bugs as the bug reports from the server operators I know are using it have more or less stopped.

Yeah, we’ve been using this version for several weeks. It works okay and we haven’t managed to break the character database yet. We used the previous version for about a year.

I haven’t tested it with other mods. The program processes a lot of ini files and it is possible that other mods will cause errors due to the way they have been implemented. Check the log tab for any errors and report them. I’ll fix the errors.

It is extremely unlikely that you could corrupt your character database but it is worth making sure that you have a current backup.

I should add that this program works best with FLHook. It should work with most common versions although I’ve only tested it with FLHookPlugin 1.6.0 (and the 1.6.1 svn head version).

It will work without FLHook but some features, like character renaming are not available.

One more thing, I expect I will release a new version of this and the process manager in a couple of weeks. I’ve already found one annoying shut down bug in the process manager (ugh!) and a minor UI bug in this program.

As soon as this is done I can get back to FLHook programming…

Nah, the Character Created time is correct - it refers to this time that the character was first detected by the program.

As you have upgraded and an entirely new db has been made, all characters will have ‘new’ character creation times.

The UI issue is the slider widget in the faction window is not locked to the bottom of the tab and when you make the window bigger, the slider is in the middle of the table.

Use it as is - it is fine.

I forgot to mention that I released a new version of this software a few days ago. http://forge.the-starport.net/projects/dsam/files

What difference between:

• “Automatically clean character files”
  and
• “Automatically fix character files”
  ?

Files > Automatically clean character file: If selected then old FLHook plugin files are automatically removed. If all character files in the account are deleted then the account directory will be removed. Note that the account directory will not be removed if the account is banned.

Files > Automatically fix character files: If this option is selected then when a character file is checked and errors are found, the errors will be automatically fixed. The program will check for invalid hashcodes and lines with too many/few parameters.

See the Readme.rtf file in the bin directory for information about the other settings.

HeIIoween wrote:
What does mean ship 2704647112 does not exist in database?
In which database? SqlLite?

Click “Tools>Reload Game Data”. This will cause the account manager to recalculate the CRC hash codes for all game data.

If this still doesn’t work then the account manager cannot find the Freelancer directory. Check that the “Properties>Freelancer directory” is set correctly.

When i try to open dsam.db by SQLite Administrator it says “qAdmin: cannot perform this operation on a closed dataset”

This happens sometimes and is probably a bug in SQLite Administrator. Quit SQL Administrator and restart it.

The final possibility is that database is corrupt although this is unlikely.