Repository navigation
Permissions
Permission identifiers use the defixus namespace. Fabric/Quilt use Fabric's newer permission API when that module is installed (26.1.2+); 1.21.11 and earlier 26.1 patches use the optional legacy provider with vanilla fallbacks. NeoForge registers equivalent nodes through its native permission API. Some commands and automatic bypasses additionally check Minecraft's permission sets directly.
The table uses Fabric's newer identifiers. NeoForge and the legacy Fabric permission provider replace the namespace colon with a dot: defixus:verification.scan.mod becomes defixus.verification.scan.mod, and defixus:panel.editor becomes defixus.panel.editor. Ordinary explicit-node checks default to false; the panel retains its Gamemaster fallback.
| Node | Effect |
|---|---|
defixus:verification.bypass.mod.on_join |
Skips ordinary mod checks, including Defixus presence/integrity and mod-list decisions. The matching release check and Mustlist still apply. |
defixus:verification.bypass.pack.on_join |
Skips ordinary pack checks at join. Does not skip later pack-change checks or Mustlist. |
defixus:verification.bypass.pack.on_change |
Skips ordinary pack-change checks and exempts the player from the normal pack-screen block. Mustlist still applies first. |
defixus:verification.scan.mod |
Allows /defixus scan <player> mods. |
defixus:verification.scan.packs |
Allows /defixus scan <player> packs. |
defixus:verification.mod.download |
Allows mod downloads and mod scan-result download buttons. |
defixus:verification.pack.download |
Allows pack downloads and pack scan-result download buttons. |
defixus:stats.global |
Allows /defixus stats global. |
defixus:stats.player |
Allows /defixus stats player <player>. |
defixus:panel.editor |
Allows /defixus panel and /dp, with a Minecraft Gamemaster-level fallback. |
Grant both join nodes to skip both ordinary sections after the reported release check. Granting one skips that section only. These permissions do not grant OP status or exempt anyone from required resources.
| Operation | Automatic access or exemption |
|---|---|
| Ordinary join verification | Exact LevelBasedPermissionSet.OWNER or exact MODERATOR skips both ordinary sections after the release check. |
| Ordinary pack-change verification | Exact OWNER skips it; Moderator alone does not. |
| Client pack-screen block | Exact OWNER, exact MODERATOR or the explicit pack-change node is exempt. |
| Scan, download and statistics commands | A level-based permission set at Moderator or higher grants the corresponding command access. |
| Panel | Uses the panel node with Gamemaster-level fallback. |
| List, reload, cleanup and hash commands | Require exact LevelBasedPermissionSet.OWNER on the command source. |
The ordinary join and pack-screen exemptions use exact permission-set comparisons, not a generic “all operators at or above this level” rule. An Admin/Gamemaster set must not be assumed to receive the exact Owner/Moderator bypass. Permission-provider behavior can differ from Minecraft's level-based sets; test with the actual accounts and provider.
Scan, download, statistics, panel and report-navigation commands require an in-game player entity. A full-permission local or Discord console source does not satisfy that requirement.
List, reload, cleanup and hash commands can run from an Owner console source. Other mods' commands have their own requirements.
Scans and downloads need an online target with compatible payload support. Download permission is separate from scan permission: a permitted scan viewer only sees download actions when also authorized to download that resource type. Download access is rechecked while transfers run.
Cached chat pages belong to the requesting UUID, expire after five minutes and recheck access when navigated. Navigation does not grant the underlying permission.
Mustlist is checked before ordinary staff/permission bypasses for Java players. Online required-resource rechecks and reported required-pack removals also apply to staff.
Geyser-recognized Bedrock players are exempt from the Java verification flows. Merely installing Floodgate or granting an ordinary bypass does not make a Java connection a recognized Bedrock connection.
The panel controls four verification switches and event-webhook switches. The webhook master switch controls event notifications, not the separately configured personal console bot or console forwarding.
Discord console authorization uses configured Discord user/role IDs; it does not use these Minecraft permission nodes. Authorized Discord commands run as a console source with Owner permissions. See Discord Integration.