nullquery wrote:
Either condensing type paths and/or run-time definition of items (specifically clothes and blunt instruments). I'd like to do this in order to reduce the amount of time it takes to compile the game.
You have gonna have to give examples, many examples, as to what you mean.
nullquery wrote:
A single database engine for persistent data storage. Either via SQLite and/or MySQL. To avoid the creation of dozens of savefiles and allow external tools to query game data.
I had this idea, if you did it right, and ensured you only used queries that both supported, it would be easy to do sqlite with mysql as an option (we need it since sybil and basil have no way of talking to eachother)
The biggest question, is how you handle importing the old data when we have multiple servers. players only get 3 char slots, but basil and sybil could each have 3 different characters.
Same for notes.
nullquery wrote:
A single method of configuration. To avoid all the various ways configuration files are being read.
Yes please!
nullquery wrote:
Reworking the administrator system. Verbs are helpful additions, but introduces a lot of clutter. Reduce verbs where acceptable, merge everything into browser windows and provide a dashboard/an overview of the game.
Before things can be moved to browser windows, the mess that is admin/topic() needs to be handled, badly.
nullquery wrote:
In general: Making things modular if I don't need them on my own server.
The only push back you might get is if that modularity comes with a cost of complexity
nullquery wrote:
In general: Making things configurable if need be.
Yes and no, There is a sizeable amount of people who think the config options have gotten out of control. I'm thinking maybe remove some of the config options that really don't need to exist, like health and crit numbers, (the game isn't balanced to anything else) and the like, that are almost never changed.
nullquery wrote:
In general: Making things extendable so I don't have to touch a single line of /tg/ code for custom modifications.
Good luck. =P
citrus wrote:
That's a fair chunk of work though, also bear in mind we have had performance trouble with the mysql DB (slow reads and writes), I can't remember exact details, MrStonedOne can probably talk more on this specifically.
This issue was fixed (for us at least). Mysql has a fuck ton of caching now, and its not even using it all. Its also on the same box as the other servers in its own vm.
One thing is that indexes need to be checked, I had to create some for our database, and I don't think they made it into the schema.