"Stock Ticker: Insider Knowledge" finally released!

I am using SQLite, because save games are stored in a single file. Easy to manage by me and the user who wants to move or hack his save games.

SQLite does have some limitations compared to other DB engine, put it is much more simple and faster. For example, there is less datatypes. All text is the same type, no need to manage length for fields.

My only complaint so far is that there was some missing features, like incapacity to load and run an SQL file. No way to do "SOURCE filename.sql" or n API function that loads and run a file. This is where I used Chat GPT to generate such function. I generated many utility functions to make programming easier, I might build a library of my own with it. Now its currently in Glymmer. For example, have a function that runs a query that returns a single value. I made a function that encapsulate the process for each data type. It avoid manually looping records and it handle errors. So more features are on the way, it will be mostly generated by AI, I don't care, I assumed those functionalities to be available some how.

Now I am considering using SQLite for prototyping my next game. Basically using scripts that implement the rules or basic functions, and manually manipulating the data in the database according to the player's actions. This would allow me to simulate the game without programming the user interface. And most of those rule scripts would be reusable in the final product. We will see, that would be the next design step.