Subfolder System

[QuerGamer]

The private worlds feature is a nice tool, so everyone can have their own build world. But what happens when you have a large builder team, and over 50 private worlds of 20-30 people?

My solution suggestion would be a system with which you could categorize multiple worlds in sub folders. Or also the possibility to have a parent folder per person. Maybe also a parent folder per project.

[thomasmny]

I definitely like the idea and would plan on adding it some day. However, currently I am very preoccupied so it will take a while unless you or somebody else wants to give it a shot.

How do envision it being implemented?

[TWME-TW]

Some possible ideas: people can't create existing folders (to prevent breaking existing world/plugin folders), and the person creating the folder will have a buildsystem.subfolder.<subfolder_name>.ownerpermission, and he can do this by using /addsubfolderuser <subfolder_name> to add a user, or use the buildsystem.subfolder.<subfolder_name>.access permission. When the world owner has this permission(buildsystem.subfolder.<subfolder_name>.access), he can move his world to this folder in /worlds edit.

Maybe add an option to default world folders (default is off) so that all created worlds don't fill the MC Server's home directory.

[TWME-TW]

But obviously we want to limit the number of subfolders to prevent filling the whole home directory again, or subfolders can only be created in the default directory? It may be divided into several options, namely whether to enable the default directory, whether to enable subfolders, whether subfolders are only created in the default directory, and permissions to limit the number of subfolders.