如何生成一个玩家无法破坏的世界
有一直保护插件 可以做到 自己找吧 金子拿来
把该世界的build权限关掉
在：plugins里面的Groupmanager里面的worlds里面的world里面的group.yml,用notepad++打开然后找到你已经创建的世界下面的build选项改为build:false
jiuerd 发表于 2014-7-18 13:54
把该世界的build权限关掉
使用权限组还是多世界配置关
小孩不乖 发表于 2014-7-18 15:23
在：plugins里面的Groupmanager里面的worlds里面的world里面的group.yml,用notepad++打开然后找到你已经创 ...
这会禁止所有世界权限
jiuerd 发表于 2014-7-18 19:20
多世界会在gm文件夹下生成对应世界的权限文件；
没有取消子世界，所以pvp为主世界的子世界，没有独立的权限文件，但是生成了配置文件，pvp代码如下
pvp:
==: MVWorld
hidden: 'false'
alias: 竞技
color: DARKGREEN
style: NORMAL
pvp: 'true'
scale: '1.0'
respawnWorld: ''
allowWeather: 'true'
difficulty: HARD
spawning:
==: MVSpawnSettings
animals:
==: MVSpawnSubSettings
spawn: 'true'
spawnrate: '-1'
exceptions: []
monsters:
==: MVSpawnSubSettings
spawn: 'true'
spawnrate: '-1'
exceptions: []
entryfee:
==: MVEntryFee
amount: '0.0'
currency: '-1'
hunger: 'true'
autoHeal: 'true'
adjustSpawn: 'true'
portalForm: ALL
gameMode: SURVIVAL
keepSpawnInMemory: 'true'
spawnLocation:
==: MVSpawnLocation
yaw: 90.29507
pitch: -0.7500657
z: 1656.4944101155877
y: 67.0
x: -346.4104309298696
autoLoad: 'true'
bedRespawn: 'true'
worldBlacklist: []
environment: NORMAL
seed: '3300882769809938254'
generator: 'null'
playerLimit: 'build'
allowFlight: 'true'
playerLimit: 'build'为我更改的，默认为-1
rxffr 发表于 2014-7-18 19:21
这会禁止所有世界权限
版主谢谢，这个问题我就是将playlimit改为了build 备份文件刚刚测试了一下 成功了 。谢谢版主指导
rxffr 发表于 2014-7-18 19:26
没有取消子世界，所以pvp为主世界的子世界，没有独立的权限文件，但是生成了配置文件，pvp代码如下
pvp:
...
把世界名加入gm的config里面呢？
mirrors:
# Worlds listed here have their settings mirrored in their children.
# The first element 'world' is the main worlds name, and is the parent world.
# subsequent elements 'world_nether' and 'world_the_end' are worlds which will use
# the same user/groups files as the parent.
# the element 'all_unnamed_worlds' specifies all worlds that aren't listed, and automatically mirrors them to it's parent.
# Each child world can be configured to mirror the 'groups', 'users' or both files from its parent.
world:
world_nether:
- users
- groups
world_the_end:
- users
- groups
all_unnamed_worlds:
- users
- groups
# world2: (World2 would have it's own set of user and groups files)
# world3:
# - users (World3 would use the users.yml from world2, but it's own groups.yml)
# world4:
# - groups (World4 would use the groups.yml from world2, but it's own users.yml)
# world5:
# - world6 (this would cause world6 to mirror both files from world5)