Repository navigation
World Access
Command permissions and world entry are separate. A player allowed to use go can still be denied entry to its destination.
World nodes use the canonical world name:
dimension.survival.allow
dimension.creative.deny
An explicitly granted .deny node blocks entry. It takes priority over an allow node, default entry, and dimensify.admin. An operator's fallback result for an undefined permission does not count as an explicit deny.
Without an explicit deny:
| Configuration | Entry |
|---|---|
permission_restrict_dimensions: false |
Allowed, subject to the player limit |
Restrictions true; default_dimension_restriction: true
|
Allowed by default, subject to the player limit |
Restrictions true; default_dimension_restriction: false
|
Requires the world's .allow permission, then checks the limit |
Giving .deny the value false does not deny entry. To remove a denial, remove the rule or set it false in your permission plugin.
Restrictions apply to go, spawn, send, portals and cross-world teleports from other plugins. The travelling player's permissions are checked when an administrator uses send. Existing players are not evicted when a player limit is lowered.
In the console:
permissify player setpermission Innectic dimensify.command.base true
permissify player setpermission Innectic dimensify.go true
permissify player setpermission Innectic dimension.survival.allow true
permissify player setpermission Innectic dimension.creative.deny true
permissify player check Innectic dimension.creative.deny
permissify player unsetpermission Innectic dimension.creative.deny
Replace the player and world names. The same rules can be assigned through groups. See Permissify's permission management for priorities and inheritance.
Permissify's RCON setting controls its own management commands; it does not control Dimensify's RCON commands.
See Configuration for the two entry settings and Command Permissions for management access.