Thank you. I can't wait for it to be available for use!
To answer your question: yes. I decided to go down a more Essentials like route, for the simple reason it makes it much easier to obliterate data for a specific player. In fact, I've written a
reset command that will do that for you - and will probably make an event that other plugins can listen to that asks them to do the same thing (plugin devs, would that be useful?). All configs that are intended to be user editable are autogenerated at startup, data files are only created as needed.
The current structure is that I have split configs and data, config files go in
/config/nucleus, data files go in
/nucleus (location of the data files are subject to change, but I do not want to put data files in
/config). Opinions are welcome.
/config/nucleus/main.conf - main config options, including module config and other general options.
/config/nucleus/commands.conf - turning specific commands on and off, along with warmup, cooldown and charging information
/nucleus/userdata/ - one JSON file per player. My data file would be at
/nucleus/userdata/df/dfe5c2a0-28bb-4449-ac73-a95980850077.json, for example.
/nucleus/worlddata/ - one JSON file per world.
/nucleus/general.json - one file for per server settings, such as blacklist.
/nucleus/jails.json also exist, but I will likely move this data into the general data store.
Part of the reason I haven't published a build yet is because I'm still getting the structure down, and I think it would be irresponsible to publish a plugin that is subject to large change that will mean server owners will have to update their files over and over. However, I think we're just about there on this sort of thing, so I'll put a build out soon.