Deprecated Darkstar fourms

Commit 7d749f63272592c7c6b4bc01bca6f07a24cb90c2 changed how keyitems are stored. Attached is an .exe that will read your map_darkstar.conf and convert every characters keyitems blob into the new format. Place it in your darkstar folder (where libmariadb.dll is) and then run it from the command line. It won't print anything out if it ran successfully. There is no way to guard against running it on an already converted blob, so make sure that you don't run it twice.

And the source, of course.

Any love for us on linux?

Oh oops, I took the time to make it portable and everything... I'll see what I can do

For Linux, build this in darkstar/keyitemconverter and then mv the tool to darkstar and run it

maybe stick this in https://github.com/DarkstarProject/dark ... migrations ?

I believe there's been a couple database changes since the project's beginning and I was just curious if there was a good place to view the history of changes or do I just have to do a compare my server's SQL files compared to the latest master's SQL files?

If not, it is what it is and I don't know if it would be beneficial enough for the team to manage going forward.

right-click the file / tortisegit / show log

I also have this "general purpose" database migrator written in bash here https://gist.github.com/Cloudef/7dd5cbd589235e5d2e85 It only handles table/field additions and removals, it won't understand field/table renames, or magically convert contents of field to new format, so it won't handle keyitems conversion nor the magic table refactor. It's mainly useful for keeping your schemas up-to-date.