Home

Rivet

Rivet is a general-purpose plugin for Paper servers. It combines player conveniences, survival mechanics, automation, staff tools, world management, and server administration in one JAR.

Rivet is built for:

• Paper 1.21.11
• Java 21
• servers that want one configurable plugin instead of many small utility plugins

It has no required runtime dependencies.

What is included

Area	Main features
Travel	Homes, public warps, server spawn, teleport requests, /back, random teleport, nearby-player search, and biome search
Player tools	Chat, private messages, nicknames, AFK, statistics, backpacks, kits, daily rewards, filters, trash, poses, and portable workstations
Gameplay	Graves, tree felling, vein mining, faster hoppers, crop protection, mob heads, egg capture, villager rerolls, and creeper restoration
Automation	Species-specific Auto Breeders with stored food, eggs, experience, and live holograms
Administration	Staff movement, vanish, flight, inventory tools, notes, command spy, ground-item cleanup, test worlds, time, weather, holograms, and optional local permissions

Start here

• Getting started explains installation, updating, and first setup.
• Feature guide explains how Rivet behaves in ordinary play.
• Command reference lists all 97 commands.
• Configuration explains every configuration file and the module system.
• Permissions explains access control and important extra nodes.
• Data and upgrades explains saved data, backups, and migrations.
• Troubleshooting covers common problems.

Important ideas

Rivet separates three kinds of settings:

1. modules.yml enables or disables substantial features. Module changes need a restart.
2. settings/ contains behavior, messages, limits, and shared policies. Most changes can be applied with /rivet reload.
3. data/ contains generated player and server state. Do not edit these files while the server is running.

Small mechanics do not each become a module. They live together in settings/gameplay.yml. Rules shared by several features, such as teleport warmups and cooldowns, live in their own policy file.

Links

• Source code
• Issue tracker