
Overhaul permissions
TheE opened this issue ยท 1 comments
If existing permissions need to be adjusted this should be done before releasing a beta version.
Points that need consideration are:
- Unneeded
warp
prefix in command, sign and world access permissions. After all, everything is about warps. Instead, command permissions could receive acmd
prefix. - Adjustment of warp warmup disobey permissions to use the
timer
prefix. /warp point
permission should be namedpoint
, notcompass
.- Removal of usage scopes like
admin
,basic
andsoc
. Setups are differently and there is no way to determine if a command is regarded as basic or not - it should be entirely up to the end-user to decide. Access and modify override permissions could be moved to a global scope (mywarp.accessall
). - Sponge's implicit inheritance could cause problems with permissions for command flags (
mywarp.warp.soc.give.force
) or usage for other players (mywarp.warp.basic.assets.other
), see here.
Should be fixed by 4ee8ea5.