Improving ChunkVault (Teller): Leveraging SQLite for Faster World Management and Automated Backups

[JakePIXL]

So, you might be wondering how ChunkVault (Teller) goes about finding worlds. It does this by scanning every file listed in local-directories.json. It checks if these files belong to a Minecraft world and whether Teller has already indexed them by looking for a .chunkvault file. What this means is that every time you load a world, Teller reads it from your disk, and it has to create a unique identifier the first time it's indexed by Teller.

Now, let's be honest, this isn't the most ideal way to handle things, but I went with it to get ChunkVault out there. But I've got a hunch that the key to solving our current indexing and restoration woes lies in something quite simple – an SQLite database. Here's how it can make a world of difference:

1. Immediate World Indexing: With SQLite, we can index worlds as soon as they're added to our tool. This means that world data is readily available right after the initial setup. No more waiting for worlds to load from scratch.

2. Background Updates: We're talking about performing background checks and updates for user worlds, making sure the data is always up to date. Imagine this: when you open ChunkVault, it seamlessly fetches data from our SQLite database, resulting in lightning-fast load times.

3. Automated Backups: Now, let's dive into an exciting feature I'm planning to introduce – automated backups. You can turn this feature on for each world you cherish. The system will keep an eye on two vital time points: the "most recent backup" and "last played." If your last visit to your world is more recent than the most recent backup, and you've enabled "auto backup," Teller will automatically craft a backup in the location of your choice. And, of course, this preference will be conveniently stored as a field in the SQLite file.

In a nutshell, incorporating SQLite as the backbone of our beloved tool, ChunkVault (Teller), promises to enhance user experiences, significantly reduce load times, and pave the way for exciting features like automated backups. This change isn't just about fixing the hiccups; it's about evolving ChunkVault into an even more indispensable tool for every Minecraft adventurer.

I'm eager to hear your thoughts and ideas. If anyone has alternative solutions or suggestions for world indexing that might outshine SQLite, I'm all ears. Keep in mind that this is a rough plan of what I'm envisioning, and it's not etched in stone. Let's discuss and explore the best path forward together.