WorldMaster is a plugin that allows you to be in full control of your server's worlds. You can use various commands documented below to create, delete or teleport to worlds.
Plugin features
Worlds
- Worlds created by this plugin are separated into two categories:
- Worlds named "worldmaster_<name>_overworld". These are accompanied by a world named "worldmaster_<name>_the_nether" and one named "worldmaster_<name>_the_end".
- These worlds are linked to their nether and end counterparts: entering a nether portal in that world teleports you into its nether, not the normal nether. End portals in that world teleport you into its own end dimension, instead of the normal end dimension.
- Dying in one of the three dimensions of a world will put you into the overworld of that world, not in the normal overworld (except if the player has a custom spawnpoint in the same or another world).
- The 1:8 ratio of the overworld and the nether is kept as normal.
- Worlds named "worldmaster_separate#_<name>".
- These worlds are on their own: nether portals and end portals don't teleport the player anywhere.
- The hashtag sign is replaced by 0, if it's an overworld dimension, -1, if it's a nether dimension or 1, if it's an end dimension.
Commands
The following commands can be used by operators:
- /tpworld <world> [<player>]
- This command teleports the specified player to the specified world's spawn point.
- The player parameter is optional; if it's not specified, the player that ran the command will be teleported to the specified world.
- Also works with worlds not created by this plugin.
- This command requires permission worldmaster.tpworld to be run.
- /deleteworld <world>
- This command deletes the specified world completely, including its folder in the server folder. This cannot be reverted.
- Also works with worlds not created by this plugin.
- This command requires permission worldmaster.deleteworld to be run.
- /createdim [<name>] [<type>] [<seed>]
- This command creates a world named "worldmaster_separate#_<name>".
- Every parameter is optional; just running the command without any parameters will create a normal overworld with a random seed, and its name will be completely randomized.
- The type parameter can only be one of normal, flat, largebiomes, amplified, nether or end. This is self-explanatory; it will change the world type of the world that will be created.
- This command requires permission worldmaster.createdim to be run.
- /createworld [<name>] [<type>] [<seed>]
- This command creates a world named "worldmaster_<name>_overworld", accompanied by a nether and end dimension, as explained above.
- Every parameter is optional; just running the command without any parameters will create a normal overworld, including a nether and an end dimension, with a random seed, and its name will be completely randomized.
- The type parameter can only be one of normal, flat, largebiomes or amplified. This is self-explanatory; it will change the world type of only the overworld that will be created.
- This command requires permission worldmaster.createworld to be run.
- /createworlds <number>
- This command runs the /createworld command with no parameters as many times as you specify.
- This is better than running the /createworld command a lot of times just to create some default worlds.
- This command requires permission worldmaster.createworlds to be run.
Configuration files
You will find there are some files in this plugin's folder. The only files you should care about are messages.yml and worldsToLoad.yml; the rest of the files should not be messed with if you don't want corruptions.
The messages.yml file contains all messages that can be sent to players' chat when using the plugin's commands. Every message is customizable on its own. You can also use color codes in all messages (apart from the warning when trying to delete the main world), using the '&' symbol and a letter for a specific color code. You can see the available color codes here:
https://minecraft.wiki/w/Formatting_codes#Color_codes
The worldsToLoad.yml file will usually be empty, apart from a few comments. If used correctly, all worlds specified in the file will be created on next server restart.
Here is an example of how to use worldsToLoad.yml:
Code (YAML):
worlds-to-load:
example:
world-type
: default
seed:
generator-settings:
dimensions-to-load:
example:
world-type
: amplified
environment
: end
seed
: amplified end
generator-settings:
It is kind of self-explanatory, but let me clarify some things:
- worlds-to-load will create worlds that include a nether and end dimension, while dimensions-to-load will create lone worlds.
- "default" is not an accepted string for world-type, but setting it to anything unaccepted will cause it to assume normal.
- world-type can be normal, flat, large_biomes or amplified.
- In dimensions-to-load, world-type doesn't matter if environment is set to nether or end.
- seed can be empty to use a random seed, or a string that is turned into a number in exactly the same way that Minecraft does it in singleplayer.
- generator-settings is used for flat worlds. It works exactly like the same tag in server.properties.
Fun fact: the icon for this plugin was taken in snapshot 22w13oneblockatatime.