hi i have a creative world in my server and i don't people to be able to tpa to them. the plugins i have that i think can stop it are mulitverse and essentials group managers plz solve this for me
Ok, first off, you need to set up your parent/child config in your Group Manager's config.yml. It is found in plugins/groupmanager/config.yml. Open it up and change it so that it copies the users.yml from your parent world but not the groups.yml. See spoiler below. Spoiler (Move your mouse to the spoiler area to reveal the content) Show Spoiler Hide Spoiler Code: mirrors: # Worlds listed here have their settings mirrored in their children. # The first element 'world' is the main worlds name # subsequent elements 'world_nether' and 'world_the_end' are worlds which will use # the same user/groups files as the parent. # Each child world can be configured to mirror the 'groups', 'users' or both files from it's parent. World: World_nether: - users - groups World_end: - users - groups Creative: - users Next you want to disable the /tpa ability of your users in the creative world. Simply open up the groups.yml file in the world folder /plugins/groupmanager/worlds/CREATIVE/groups.yml and add this permission to the yml: Spoiler (Move your mouse to the spoiler area to reveal the content) Show Spoiler Hide Spoiler Code: VIP: default: false permissions: - -essentials.tpaccept inheritance: - admin info: prefix: '&4[VIP] ' build: true suffix: ''
wait im still confused im sorry man i tested it bet they still tpa'ed and then when they entered the world they became default EDIT by Moderator: merged posts, please use the edit button instead of double posting.
oh, well you could try another route then. Under your MultiVerse-Core config.yml found here: /plugins/MultiVerse-Core/config.yml Open it up and change the line for enforceaccess: 'false' to 'true' and then give the permission node to your groups in your groups.yml in your parent groups.yml like so: Spoiler (Move your mouse to the spoiler area to reveal the content) Show Spoiler Hide Spoiler Code: Default: default: true permissions: - -multiverse.access.Creative - multiverse.access.World - multiverse.access.World_nether - multiverse.access.World_the_end inheritance: - admin info: prefix: '&4[VIP] ' build: true suffix: '' VIP: default: false permissions: - multiverse.access.Creative inheritance: - admin info: prefix: '&4[VIP] ' build: true suffix: '' This will use permissions to enforce access to certain worlds. Your VIP group will be able to access the creative world, but your default group will not. Make sure you type the name of your world EXACTLY as it is. This node IS case sensitive.
Make sure you /stop your server before you make any changes to the configs. This will prevent any reverting of the configs due to them being saved in the memory. Especially your groups.yml and users.yml.
Anytime...i have been running a server for two years, one hosted, one in my house. And multiverse/groupmanager the whole time. PM me if you need some help with those. And stop by some time and say hello.