Permissions

How Permissions Are Checked

• voxelbench.use is required for every /bench command. Without it, nothing else works, not even /bench lang.
• Most commands also require their own permission, listed below. Each test has its own node too (see Test Permissions).
• Tab completion only suggests the commands, sub-commands and tests you are allowed to run.
• GUI buttons run the corresponding commands, so they are checked the same way. Some screens also check a permission when they open (see GUI Screens).
• Operators, and players granted *, have every permission.
• The auto-bench agent sends /vbautobot, which checks no permission: the one-time code validated by voxelbench.com is its authorization. Its other form, /bench autobot, still requires voxelbench.use like every /bench command, and nothing more.

Permission Nodes

Command Permissions

Every command requires voxelbench.use, plus:

Without voxelbench.world, /bench zones still lists the zones, but hides the teleport links and the tp/clean usage lines. The clean line only appears when the zones are in a voxelbench_* world, the only worlds where clean removes anything.

Without voxelbench.stresslimit, stress limit profiles are not offered: the tab completion of /bench custom run, the custom profiles screen and the list of available profiles printed after an unknown name leave them out. /bench custom list and info still show every profile.

Monitor Permissions

Holding any one of voxelbench.monitor, voxelbench.monitor.bars or voxelbench.monitor.web opens the monitoring area; each part then requires its own node:

• /bench monitor without argument opens the boss bar screen for players with voxelbench.monitor.bars; for everyone else it shows the status.
• voxelbench.monitor.web covers everything that exposes metrics outside the game: the HTTP server, push mode, API keys, the IP whitelist and certificates.
• voxelbench.monitor grants both child nodes, and it is the only node that allows /bench monitor reload, because that command reloads the whole plugin configuration.

GUI Screens

These screens check a permission when they open, whichever way you reach them:

Buttons that start a benchmark, a test or another action run the matching command, so the command permissions above also apply.

Test Permissions

Each test is guarded by its own node. The node belongs to the test itself, so the canonical ID and the short alias of a test need the same permission (for example /bench test lightingUpdate and /bench test lighting both check voxelbench.test.lighting). /bench test alone and /bench test list need no extra node, and an unknown ID only prints an error.

The category nodes group the tests the same way as the test catalog:

Hardware Tests

Single-Core CPU Tests

Gameplay Tests

Extension Tests

A test added by another plugin requires the permission its author declared, if any. A test declared without a permission only needs voxelbench.use.

These nodes guard /bench test and the test buttons of the GUI. A whole suite is authorised by one node, not test by test: /bench start runs the standard benchmark under voxelbench.start, and the tests of a custom profile run under voxelbench.custom (or voxelbench.start), plus voxelbench.stresslimit for a stress limit profile. A player who can run a profile runs every test it contains.

Dynmap Permissions

These permissions control who can view VoxelBench layers on Dynmap's web interface.

Note: Dynmap permissions require additional configuration in plugins/dynmap/markers.yml. See Integrations - Dynmap for details.

Upgrading from 1.8.1 or Earlier

Up to VoxelBench 1.8.1, most of these permissions were declared but not checked. They are now enforced. Operators and players with * are not affected; for everyone else:

• Command nodes. voxelbench.use alone used to be enough for /bench start, stop, gui, info, reports, stresslimit, reload and monitor. A group that was only given voxelbench.use loses access to them: grant the nodes it needs, for example voxelbench.start and voxelbench.stop.
• New nodes. /bench link now needs voxelbench.link, /bench zones tp and zones clean need voxelbench.world, and the settings screen needs voxelbench.settings.
• Tests. Every test now checks its node, including the ones that used to run with voxelbench.use alone (lightingUpdate, entityCollision, tickingTileEntity, villagerTrading under their canonical IDs, and projectileStorm, entityCramming, playerWorldLoad, singleCoreBenchmark, singleCoreMax).
• Moved tests. mobPathfinding, redstone and blockPhysics moved from voxelbench.test.singlecore to voxelbench.test.gameplay, their category. A group that was given voxelbench.test.singlecore to run them now needs voxelbench.test.gameplay or the individual nodes; voxelbench.test.singlecore now covers singleCoreBenchmark and singleCoreMax.

LuckPerms Examples

Grant full access to an admin group

/lp group admin permission set voxelbench.* true

Allow a group to run tests but not full benchmarks

/lp group moderator permission set voxelbench.use true
/lp group moderator permission set voxelbench.test true
/lp group moderator permission set voxelbench.stop true
/lp group moderator permission set voxelbench.gui true
/lp group moderator permission set voxelbench.info true

Let a staff group manage the web dashboard

/lp group staff permission set voxelbench.use true
/lp group staff permission set voxelbench.monitor.web true

Allow all players to check TPS

/lp group default permission set voxelbench.use true

This gives access to the commands that need nothing beyond voxelbench.use: /bench tps, mspt, status, version, help, ping, the zone list and the test list.