Skip to content

Gameplay and Automation

Alex Baldry edited this page Aug 13, 2026 · 3 revisions

Gameplay and automation

Auto Breeders

Auto Breeders are species-specific machines represented by an End Rod. They store the correct breeding food and automatically put a nearby eligible pair into love mode every five seconds.

Each breeder tracks:

  • animal type;
  • stored food;
  • number of animals bred;
  • stored breeding experience;
  • naturally laid chicken eggs.

The inventory's first row accepts food. Chicken eggs appear in the middle row. Click the experience bottle to collect stored experience.

The live hologram is reconstructed when the server starts or its chunk loads. The recurring breeder task only updates already-loaded displays; it does not repeatedly search for or reconstruct holograms.

Graves and /back

When a player dies, Rivet adds the death location to the player's private teleport history and can place a persistent grave containing the dropped inventory. A grave is not created when keepInventory is active or there are no drops.

Ownership, access delay, expiry, item dropping, and tracking compasses are controlled in settings/graves.yml. /back returns the player to the latest valid history location and also uses the shared teleport policy.

The history records deaths and the origins of meaningful homes, warps, spawn, TPA, RTP, portal, staff, and utility teleports. It keeps up to eight distinct locations across restarts. Tiny movement corrections and internal teleports are ignored. The history is never exposed as numbered commands, and a successful /back consumes its destination instead of recording a return trip.

Rivet saves the grave before clearing normal death drops. If saving fails, the normal drops remain.

Tree felling and vein mining

Breaking the bottom log of a valid natural tree with an axe can fell the connected tree. Rivet checks tree shape, natural leaves, size limits, tool suitability, and protection events before starting.

Vein mining handles connected ores, Ancient Debris, and Glowstone. It requires a suitable pickaxe and respects protection plugins. Drops and experience are collected at the initially mined block.

Egg capture

Players with rivet.eggcapture can capture supported mobs by throwing eggs. The captured mob is stored in a spawn egg while preserving supported entity data. Sounds, particles, and messages are configurable in settings/egg-capture.yml.

Villager rerolls

Eligible villagers receive a special non-consuming reroll offer in their normal trade screen. By default, a villager must have a workstation and must not have been traded with. The ingredient, result item, messages, and effects are configurable.

Rivet uses Paper's native trade generation for the villager's current profession and level.

Creeper restoration

Rivet records blocks destroyed by creepers for the lifetime of the current server process. A Restoration Core can be thrown near a saved crater to rebuild it with a visual reverse-flight animation.

Container blocks, container contents, other block-entity data, activation radius, timing, debris, sounds, and particles are configurable. Crater snapshots are not saved across restarts.

Mob heads

Mob-head drops are configurable and take Looting into account. Native head materials are used where Minecraft provides them; other supported mobs use bundled textures. Vanilla Wither Skeleton skull behavior is preserved unless custom Wither Skeleton drops are explicitly enabled.

/head <player> creates a head only for an online or server-cached player profile.

Small gameplay mechanics

settings/gameplay.yml groups mechanics that do not need full module lifecycle management:

  • crop-trample protection;
  • replanting of water-harvested crops;
  • optional Iron Golem poppy drops;
  • faster block hoppers.

Hoppers use a two-tick transfer cooldown by default. Vanilla uses eight ticks.

Ground-item cleanup

The lagg module periodically removes eligible dropped item entities from loaded worlds. It does not remove mobs, minecarts, armour stands, projectiles, or other entity types.

By default, custom-named items and items with persistent plugin data are protected. Scheduled warnings, cleanup interval, empty broadcasts, protected-item rules, and result messages are configured in settings/lagg.yml.

/lagg clear runs a cleanup immediately. /lagg reload validates only the cleanup settings and restarts its schedule.

Clone this wiki locally