So with SQLite, would you only allow x number of total commands and make that many columns, make 1 commands column and store them like {command one}REALLYGOODSEPARATORHERE{command two}..., or when a new one is defined, would you read the number of columns currently in the table, subtract by the number of non-command columns, and then if that # < number of commands in new command, ALTER the table and add a new column? The last 2 offer the most flexibility, and the last one is probably the best, but I don't know anything about the SQLite implementation in Cuberite.
Also yes Ini's are slow but you could still only interact with them during initialization and disable (or if you have reload commands). The reload commands could get really long, but they are an optional thing so the owner will learn when they can and cannot do that. LOL IGNORE THIS
I just tried a 250 key ini file with 7 values per key. Using the LIP library (I gave up trying to get the Cuberite cIniFile stuff to work about 12 hours ago), it loaded the file into a table in < 1 second. Literally. I had it then write out to a different file. It wrote out in < 1 second. That's far from slow. I couldn't even see the difference between the LOG's "Begin parse of sample.ini" and "Parse Complete". They popped onto my screen at the same time as
[02:40:16] Begin parse of sample.ini
[02:40:16] Parse Complete
[02:40:16] Initialised BungeecordTeleButton v.1
[02:40:16] Plugin loaded
So yeah. Consider using INIs.
https://github.com/Dynodzzo/Lua_INI_Parser <- LIP library btw.
Also yes Ini's are slow but you could still only interact with them during initialization and disable (or if you have reload commands). The reload commands could get really long, but they are an optional thing so the owner will learn when they can and cannot do that. LOL IGNORE THIS
I just tried a 250 key ini file with 7 values per key. Using the LIP library (I gave up trying to get the Cuberite cIniFile stuff to work about 12 hours ago), it loaded the file into a table in < 1 second. Literally. I had it then write out to a different file. It wrote out in < 1 second. That's far from slow. I couldn't even see the difference between the LOG's "Begin parse of sample.ini" and "Parse Complete". They popped onto my screen at the same time as
[02:40:16] Begin parse of sample.ini
[02:40:16] Parse Complete
[02:40:16] Initialised BungeecordTeleButton v.1
[02:40:16] Plugin loaded
So yeah. Consider using INIs.
https://github.com/Dynodzzo/Lua_INI_Parser <- LIP library btw.