All VoxelBench commands start with `/bench`. Aliases: `/benchmark`, `/b`. ## General Commands | Command | Description | Permission | |---|---|---| | `/bench` | Opens the main GUI. | `voxelbench.use` | | `/bench start` | Runs the standard benchmark. | `voxelbench.start` | | `/bench start force` | Bypasses the player-online safety check. | `voxelbench.start.force` | | `/bench stop` | Aborts the current benchmark / auto-bench run. | `voxelbench.stop` | | `/bench test [k=v…]` | Runs a single test. | `voxelbench.test.` | | `/bench tests` | Alias of `/bench test`. | — | | `/bench tests list` | Lists every registered test, grouped by category. | `voxelbench.test` | | `/bench gui` | Opens the GUI directly. | `voxelbench.gui` | | `/bench info` | Server identity + plugin info. | `voxelbench.info` | | `/bench reports` | Local reports browser GUI. | `voxelbench.reports` | | `/bench reload` | Reloads config + lang. | `voxelbench.reload` | | `/bench lang ` | Switches the in-game locale for the sender. | `voxelbench.lang` | | `/bench monitor` | Opens the monitor GUI. | `voxelbench.monitor` | | `/bench stresslimit` | Runs the breaking-point mode. | `voxelbench.stresslimit` | | `/bench verify

` | Server-pairing verification flow. | `voxelbench.verify` |
| `/bench world …` | Benchmark world lifecycle. | `voxelbench.world` |
| `/bench custom …` | Custom benchmark profiles. | `voxelbench.custom` |
| `/bench help` | Explicit help. | — |

## Benchmark Commands

| Command | Permission | Description |
|---------|------------|-------------|
| `/bench start` | `voxelbench.start` | Run a full benchmark suite |
| `/bench start  [delay]` | `voxelbench.start` | Run multiple benchmarks (e.g., `/bench start 5 60`) |
| `/bench stop` | `voxelbench.stop` | Stop the current benchmark or test |

### Full Benchmark

```
/bench start
```

Runs all tests in sequence: Hardware → Gameplay → Single-Core CPU. Results are submitted to voxelbench.com.

A confirmation is required before the benchmark begins (configurable via `confirmation.require-confirmation` in config).

### Multi-Run Mode

```
/bench start 5 60
```

Runs the benchmark 5 times with a 60-second delay between each run. Useful for averaging results and reducing variance. Requires confirmation before starting.

### With Warmup run

```
/bench start 5 60 warmup
```

Run one or more benchmarks, starting with a warm-up benchmark to prepare the server, the garbage collector, and other factors that may affect the score calculation.


## Individual Test Commands

| Command | Permission | Description |
|---------|------------|-------------|
| `/bench test` | `voxelbench.test` | List all available tests |
| `/bench test ` | `voxelbench.test.` | Run a specific test |

### Hardware Tests

| Command | Permission |
|---------|------------|
| `/bench test multiCore` | `voxelbench.test.multicore` |
| `/bench test memory` | `voxelbench.test.memory` |
| `/bench test disk` | `voxelbench.test.disk` |
| `/bench test network` | `voxelbench.test.network` |

### Single-Core Tests

| Command | Permission |
|---------|------------|
| `/bench test mobPathfinding` | `voxelbench.test.mobpathfinding` |
| `/bench test redstone` | `voxelbench.test.redstone` |
| `/bench test blockPhysics` | `voxelbench.test.blockphysics` |

### Gameplay Tests

| Command | Permission |
|---------|------------|
| `/bench test chunkLoading` | `voxelbench.test.chunkloading` |
| `/bench test mobSpawn` | `voxelbench.test.mobspawn` |
| `/bench test hopper` | `voxelbench.test.hopper` |
| `/bench test explosion` | `voxelbench.test.explosion` |
| `/bench test worldSave` | `voxelbench.test.worldsave` |
| `/bench test lightingUpdate` | `voxelbench.test.lighting` |
| `/bench test entityCollision` | `voxelbench.test.collision` |
| `/bench test tickingTileEntity` | `voxelbench.test.tileentity` |
| `/bench test villagerTrading` | `voxelbench.test.villager` |
| `/bench test chunkTicking` | `voxelbench.test.chunkticking` |
| `/bench test boneMealGrowth` | `voxelbench.test.bonemealgrowth` |
| `/bench test liquidPhysics` | `voxelbench.test.liquidphysics` |
| `/bench test combatSimulation` | `voxelbench.test.combatsimulation` |
| `/bench test mobAI` | `voxelbench.test.mobai` |

### Custom Test Parameters

In **custom mode** (`benchmark-mode: custom` in config), some tests accept parameters:

```
/bench test multiCore 100 100000    # threads, iterations
/bench test disk 512                # file size in MB
/bench test memory 512 3            # size in MB, passes
/bench test chunkLoading 200        # chunk count
/bench test mobSpawn 300            # mob count
/bench test hopper 3                # parallel lines
/bench test explosion 30            # TNT count
/bench test mobPathfinding 100      # mob count
/bench test redstone 50             # circuit count
/bench test blockPhysics 200        # block count
```

In **standard mode** (default), fixed values are used for comparability across servers.

## Monitoring Commands

| Command | Permission | Description |
|---------|------------|-------------|
| `/bench monitor web start` | `voxelbench.monitor.web` | Start the web dashboard |
| `/bench monitor web stop` | `voxelbench.monitor.web` | Stop the web dashboard |
| `/bench monitor bars` | `voxelbench.monitor.bars` | Toggle boss bar monitoring |
| `/bench monitor push start` | `voxelbench.monitor.web` | Start push mode |
| `/bench monitor push stop` | `voxelbench.monitor.web` | Stop push mode |
| `/bench monitor hash ` | `voxelbench.monitor.web` | Set dashboard password |
| `/bench monitor apikey` | `voxelbench.monitor.web` | Generate API key |
| `/bench monitor whitelist add ` | `voxelbench.monitor.web` | Add IP to whitelist |
| `/bench monitor whitelist remove ` | `voxelbench.monitor.web` | Remove IP from whitelist |
| `/bench monitor https generate` | `voxelbench.monitor.web` | Generate SSL certificate |

## Benchmark world management

Voxelbench benchmarks need a controlled environment. By default the plugin
creates a disposable flat world per run, but you can pin a specific world so
every run uses the same map.

| Command | Description |
|---|---|
| `/bench world list` | Lists all `voxelbench_*` worlds known to the server. |
| `/bench world show` | Shows the currently pinned world (or `` if auto-temp is in use). |
| `/bench world set ` | Pins `` as the target world for every subsequent benchmark. |
| `/bench world unset` | Clears the pinned world. Future runs fall back to auto-temp. |
| `/bench world create ` | Creates a brand-new flat world `voxelbench_`. |
| `/bench world delete ` | Unloads and deletes a `voxelbench_` world from disk. |

The `voxelbench_*` prefix is enforced — these commands cannot touch your survival
or production maps. See [World Management](../benchmarks/world-management.md) for
the full lifecycle, persistence, and Multiverse-Core interaction.

**Permission:** `voxelbench.world` (default: op).

## Custom benchmark profiles

Custom profiles are YAML files that describe a reproducible test sequence with
your own parameters. They live in `plugins/VoxelBench/custom_benchmarks/`.

| Command | Description |
|---|---|
| `/bench custom run ` | Runs the profile `.yml`. |
| `/bench custom list` | Lists every profile found in the directory. |
| `/bench custom info ` | Shows the profile's metadata + test list. |
| `/bench custom reload` | Re-reads the directory without restarting the server. |

Three preset profiles ship with the plugin: `standard.yml` (mirror of
`/bench start`), `showcase.yml` (longer, more thorough), and `example.yml`
(annotated reference). See [Custom Profiles](../benchmarks/custom-profiles.md)
for the YAML schema.

**Permission:** `voxelbench.custom` (default: op).

## Report Commands

| Command | Permission | Description |
|---------|------------|-------------|
| `/bench reports` | `voxelbench.reports` | Open reports GUI |
| `/bench reports list` | `voxelbench.reports` | List saved reports |

## Server Verification Commands

| Command | Permission | Description |
|---------|------------|-------------|
| `/bench verify ` | `voxelbench.verify` | Start server verification |
| `/bench verify status` | `voxelbench.verify` | Check verification status |
| `/bench verify cancel` | `voxelbench.verify` | Cancel ongoing verification |

## Account Linking Commands

| Command | Permission | Description |
|---------|------------|-------------|
| `/bench link` | `voxelbench.use` | Start the account linking process |
| `/bench link force` | `voxelbench.use` | Re-link (replace existing token) |

## Stress Limit Commands

| Command | Permission | Description |
|---------|------------|-------------|
| `/bench stresslimit` | `voxelbench.stresslimit` | Open stress limit GUI |

## Extension tests

Tests registered by third-party plugins through the extension API show up
under their own `.` namespace and accept parameters as
`key=value` pairs on the command line:

```
/bench test myplugin.cacheBench iterations=200 warmup=20
```

`/bench test  ` autocompletes from the live registry so any
extension test appears the moment its plugin enables. The parameter list
in the tab-completion popup is derived from the test's declared
`ParamSpec`s — no hand-maintained hint lists.