Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
We could think about a way that the user could keep a copy of the file which contains all the changes... although it's probably tricky to define which changes the user acutally wants to keep...
Another thing I could think of is to enable custom SQL commands to be supported by the game (which would be applied to the database when starting the game). So instead of editing the definitions file, you would just add SQL commands to achieve the same thing (for instance, if you want to change the stack size of all items to 999, the SQL command for that would be "UPDATE items SET stacksize=999"). However, this isn't very user friendly... and it gets quite verbose if you want to update individual items differently, for example.
Having said that, being able to edit the definitions through the Plugin API is also on our to-do list. Once that's implemented, we could release an example plugin to change settings in the definitions (although we would still have to think about a user friendly way to perform the changes then).
would it be possible for a player to create a batch file with the SQL commands he wants and have this batch file executed if it is there?
something like "player_DB_conf.sqlbat" (don't know the ending for an SQL batch)
that way the player could collect all the SQL changes they want and keep the batch file over the updates...
Maybe a simple option before update that tolds you :
"do you want to save some DB/properties files?"
Then when updated if you had ticked that option to keep some old files backuped, then the game proposes you to add old data files with the new files... let's say on the new files the game will copy old file and merge it with the new file, like that you will have a "recompiled" file with old datas and new implemented datas in one
don't know if I’m explaining clearly :D
It's still not very user friendly though... the user would have to set up SQL commands instead of being able to edit the DB with a UI-based tool =/
Basically that would require some kind of UI where you can select which columns and rows you actually want to copy from another db file... if we just let the user store the entire items table, for example, this might get problematic if some values for existing items changed with an update (e.g. the model path). The game would need some kind of editor or dialog where you could select the columns you want to overwrite (e.g. if you just want to update the stack sizes, for example). There is unfortunately quite some work involved to implement something like that (and I also guess that the majority of users doesn't edit the database file at all)...
Well yeah... maybe with some Plugin API... dunno