The permission is always worldmanager.[MainSubcommand].
For example, the command /wm generate [World] (Generator) {Seed} has the permission worldmanager.generate. worldmanager.gen wont work. It have to be the main subcommand.
You can see the command and all the aliases when you execute /wm help ingame or via console.
You also can prevent players from entering a world. Just give them the permission worldmanager.deny.[World]
If you want to give a player access to /worldmanager teleport but only to a specific world, just give him the permission worldmanager.teleport.[World]
To open the teleport ui, the player needs the permisson worldmanager.teleportui.
For the generation ui, they need the permission worldmanager.generationui.
You can change the max players per world in your world settings. If the limit is reached, you can't enter the world unless you have the permission worldmanager.enterfullworlds
/worldmanager teleport [World] (Player)* teleports you or the pointed player in this world. Instead of "teleport", you can use tp and to
/worldmanager generate [World] (Generator)* {Seed}* generate a new world. Instead of "generate" you can use gen or create
/worldmanager delete [World] deletes the world. Instead of "delete" you can use del, remove or purge
/worldmanager load [World] loads the world while /worldmanager unload [World] unloads a world
/worldmanager reload [World]* reloads a world.
/worldmanager rename [World] (New Worldname) renames a world
/worldmanager copy [World] (Name of the Copy)* will copy a world. Be careful. You can overwrite other worlds.
/worldmanager setspawn will set the worldspawn
/worldmanager settings [World]* opens a FormUI with world-specific settings
/worldmanager regenerate [World]* regenerates the world. You also can use reg or reset instead of "regenerate"
/worldmanager setseed [World] (Seed) Change the seed of your world. Also works with reseed
/worldmanager info [World]* shows you informations about this world
/worldmanager setbiome [Biome] changes the biome of every loaded chunk in the current world.
/worldmanager gamerule [World]* opens an UI to manage the gamerules
/worldmanager update Updates WorldManager.
/worldmanager addons opens an addon ui where you can extend your server very easy.
/worldmanager default [World]* shows you the default level. You can change it if you write the worldname too.
So for teleportation its worldmanager.teleport or worldmanager.teleport.InsertYourWorldnameHere
Generation is worldmanager.generate
Gamerules are worldmanager.gamerule
etc.
But you can always use worldmanager.admin to have access to everything.
Now you can sync gamerules and worldsettings easy
Just do /wm sync (templateworld) and a UI opens to select the worlds.
This is useful to save some time while changing the world gamerules on every level
Added a /locatebiome command because Nukkit does not have one.
Can be executed with /locatebiome or /wm locatebiome
The args are: /wm locatebiome (biome) [range] {true/false}
The {true/false} sets if you want to get teleported to the location.
Range and the teleport boolean are optional.
Also added an Auto-Updater.
Enabled by default. Can be disabled if you create a file in your plugins folder called worldmanager.yml with the content
autoupdate: false
The file isn't generated by default...
let the player execute /wm tp world and give them the permission worldmanager.teleport.insertworldnamehere or just worldmanager.teleport to let them teleport to every world
Im just getting started making a small server for friends im considering making a network like server and adding cool plugins. i have a question to ask does this plugin only require 1 server to make multiple worlds and could the lobbynk make only one of them worlds a lobby/hub.
Im just getting started making a small server for friends im considering making a network like server and adding cool plugins. i have a question to ask does this plugin only require 1 server to make multiple worlds and could the lobbynk make only one of them worlds a lobby/hub.
Uhh. I made some inprovements over time. But I dont remember which.
So I will list everything I found.
So added API 1.0.13 to the supported apis,
Added an image link in plugin.yml to to display this image in PluginManager
Added Addons: WorldWhitelist by Buddelbubi, MaxWorldPlayers by Buddelbubi
Added /worldmanager version command? or maybe just forgot to document it.
The plugin now uses its own World Class and used World Objects in the cache instead of configs.
It will probably use more ram, but it is more performant and elegant.
The World Class was added for a while now, but the plugin didn't use it.
Also renamed some classes and methods.
- Changed World Setting "respawndefaultworld" to "respawnworld". You can now select the respawn world.
- /worldmanager setdefault [world] now saves the setting in the server.properties. (no loss after reboot)
-...
i don't know if this is a bug, when a person places a bed and clicks on it to get respawn point, when they die they will respawn at world coordinates so not at bed coordinates! is there any way to fix this? this error does not occur at version 1.1.1
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
