At first I was going to say 'Fifa's '.....
Personally I'd used flat file instead of databases in this scenario. I don't think it's worth headaches in many area (version control, query management, database driver, etc etc.). I'd use databases in the system that would frequently updates and need to handle multiple transaction concurrently (like MMO game server for instance).
Anyway I think for embeded database, nothing beats Sqlite.
http://9tawan.net/en/
6 hours ago, mr_tawan said:Personally I'd used flat file instead of databases in this scenario. I don't think it's worth headaches in many area (version control, query management, database driver, etc etc.).
Quite.
Keep things as simple. Make it even more simple if you can.
I agree you may pick a wrong solution, but then again, maybe the solution used by some other game was wrong too, but they realized it too late and got stuck with it? Who knows.
A less complicated solution has the advantage that it's easier in every aspect. Simpler to understand, simpler to use, simpler to modify if you find your ideas are not optimal, etc.
This means you can build experience with it (and with your game design problem) faster. With that experience you can make better decisions what to use (and what not to use). If your solution doesn't work, it's easier to change it to something else if you used something simple. Making a complicated system simpler is much much much harder if not impossible.
