[Feature Request] Exposing a singular database object.

[OoLunar]

What's your suggestion?

On the server class, a database object should be exposed to everything, plugin API included. The database object should be able to dynamically create tables based off of an object.

Why do you feel this should be added?

Having a single database available will prevent having 20 sqlite files laying around. It could also be used to prevent plugins from having filesystem access.

Do you have a rough idea of how this should be implemented? If so, how?

The table name should be prefixed with the plugin's name, along with whatever table name the plugin provides. A proof of concept:

public class EssentialsPlugin : Plugin {
    public async Task Main(IConfiguration serverConfig, Database serverDatabase) {
        ITable<Warp> warps = serverDatabase.CreateTable<Warp>("warps"); // Creates table essentials_warps
        Warp spawnWarp = warps.FirstOrDefault(databaseWarp => databaseWarp.Name == "spawn");
        spawnWarp.Coordinates = new Vector(0, 64, 0);
        warps.SaveChanges();
    }
}

I expect the final example to look very different, however the concept is here.

What gave you this idea? Was it related to a certain problem or inconvenience?

Multiple inconveniences when managing plugins.

Have any alternatives been considered?

N/A

Personal notes

N/A