Troubleshooting

Troubleshooting

Rivet does not start

Check the following:

1. The server is Paper 1.21.11.
2. Java is version 21.
3. Only one Rivet JAR is present in plugins/.
4. Every value in modules.yml is true or false.
5. YAML files use spaces, not tabs.

The enable error normally includes the exact file and validation problem.

A command says its feature is disabled

Find the feature in modules.yml, set it to true, and restart. /rivet reload reports module changes but does not start or stop listeners, recipes, or scheduled tasks during a live session.

/rivet reload fails

The old configuration remains active. Read the console for the failing path, correct the YAML, and try again.

Common causes are tabs, incorrect indentation, missing quotes, an unquoted colon inside text, or a non-Boolean module value.

A player lacks access

Check all relevant layers:

1. The module is enabled.
2. The player has the base command permission.
3. The player has any additional target, formatting, bypass, row, kit, or hologram-visibility permission.

See Permissions for the extra nodes.

Teleports cancel or report a cooldown

The normal player teleport policy is in settings/teleports.yml. Walking, falling, knockback, or another teleport can cancel a warmup when cancel-on-move is enabled. Looking around does not count as movement.

/back, TPA requests, and RTP also have feature-specific cooldowns. rivet.tp.nocooldown bypasses cooldowns but not the warmup.

A destination is unavailable

A home, warp, spawn, or /back history location cannot be used when its world is missing or unloaded. /back skips unavailable history entries and tries the next valid location. Rivet can load its own tracked test worlds, but it cannot recreate an unrelated missing world.

Restore the world or replace the saved destination.

RTP cannot find a location

Check settings/rtp.yml:

• the world is allowed;
• minimum radius is not greater than maximum radius;
• the world border contains the search area;
• biome rules are not too restrictive;
• maximum attempts are sufficient;
• the Nether maximum height leaves usable ground.

RTP rejects dangerous ground, liquids, and spaces without two clear standing blocks.

An Auto Breeder is idle

Confirm that it has at least two correct food items and two eligible adult animals of the configured species within eight blocks. The animals must be able to breed and not already be in love mode.

Breeding checks run every five seconds. The breeder chunk must be loaded.

If the hologram is missing, leave and reload the chunk. /clearhologram can repair stale loaded breeder displays without changing /holo displays.

Tree felling or vein mining does not start

Tree felling requires Survival mode, a suitable axe, the bottom log of a valid natural tree, enough natural leaves, and a structure within configured limits.

Vein mining requires Survival mode and a pickaxe that can produce a drop from the first block. Connected groups above the safety cap are left alone. Protection plugins are consulted for the connected blocks.

A grave did not appear

No grave is created when keepInventory is active or the death has no drops. The death location is still added to /back history.

If the grave save fails, Rivet leaves normal death drops in place and reports the error.

Sound warnings appear

Use a canonical key such as entity.enderman.teleport. Rivet also accepts minecraft: prefixes and legacy names such as ENTITY_ENDERMAN_TELEPORT or entity_enderman_teleport.

An invalid sound falls back to a safe default and reports its settings path.

Ground-item cleanup removed nothing

The cleanup scans only loaded worlds and only dropped item entities. Named items and items with persistent plugin data are protected by default. Check settings/lagg.yml and run /lagg clear to test the current rules.

Report a problem

Open an issue and include the Paper version, Java version, Rivet version, console error, triggering command or action, and the relevant settings with private details removed.