SkStorage

why does this exist The closest compatible plugin to this is PatPeter's SQLibrary for SQLite. The last release was 2013. It uses rollback journal mode (no WAL), one giant variables.db for everyone, stores pd::<UUID>::eco.credits as a 60 byte text key on every single row, and runs your user supplied regex on every write. I needed a server that could handle more than a combined total of one variable. So this exists. what it does Variables get sorted into one of three SQLite databases by name. If the name matches a glob you put in config.yml under persistent.patterns (think leaderboards, credits, balances) it goes in persistent.db. That file uses dict encoded UUIDs and keys, so a million leaderboard rows ends up roughly a third the size it would otherwise. If the name contains a UUID anywhere in it, it goes to player//.db. The file is opened when the player joins and closed when they quit. Open file handles roughly equal online players, not total players ever. If the name starts with sf:: it goes to server.db for global state. Anything else is not persisted. It sits in Skript's RAM for the session and dies on restart. This catches typos that the old setup would happily save forever to nowhere useful. WAL is on. Six other PRAGMAs are set. There's a flush task that commits every 200ms, so writes batch into transactions instead of fsyncing on every single set. Worst case data loss on a hard crash is 200 milliseconds.