Steal a Brainrot

Installation

Requirements, install steps, first run, and the files the plugin creates.

This page gets the plugin onto your server. Building the arena comes after, on Arena Setup.

Requirements

RequirementDetail
ServerSpigot or Paper, Minecraft 1.18 and newer (Paper recommended)
JavaJava 17 and newer
Hard dependenciesNone
OptionalModelEngine for custom models, DecentHolograms for hologram rendering, Vault plus an economy plugin for real server money
DatabaseNothing to install. SQLite works out of the box, MySQL is optional (see Storage)

Install steps

Get the jar

Download the latest build from the store you bought it on. See Download.

Drop it in plugins

Stop the server, put the jar in your plugins/ folder, and start it again. Use a full restart, not a reload plugin.

Check the console

A clean start prints lines like these:

Using bundled language: en.
Storage: SQLite (data.db)
Steal a Brainrot is ready. Set up an arena with /brainrot admin.

If the plugin is missing from /plugins, look for an error above those lines and bring it to the Discord.

Optional: add ModelEngine

If you want custom 3D mob models, install ModelEngine too and follow Custom Models. Without it, every tier uses a normal Minecraft mob.

From zero to playing

Once the jar is in, these four steps take you to a live arena. Each one has its own page.

  1. Drop in the jar. Done above.
  2. Build one base. Stand on each spot and run its setup command. /brainrot admin show draws everything you have marked. See Arena Setup.
  3. Copy it and lay the runway. Stamp base 1 onto the other houses with /brainrot admin copy, then place path plates along the runway. See Arena Tools.
  4. Open the arena. Run /brainrot admin enable. Players can now /brainrot join and claim a base.

What gets created

On first start the plugin makes its folder:

config.yml
en.yml
fr.yml
es.yml
models.yml
arenas.yml
leaderboards.yml
data.db
FileWhat it holds
config.ymlEvery setting, with a comment above each one. See Configuration.
language/All player-facing text. See Messages & Language.
models.ymlRegistered ModelEngine model ids. Managed by the importer.
arenas.ymlYour arena layout. Written by the admin setup commands the moment you run them.
leaderboards.ymlWhere your floating leaderboards stand. See Leaderboards.
data.dbPlayer stats and unlocks when using SQLite. See Storage.
model-imports/Drop model packs here to import them. See Custom Models.

Updating

Replace the jar and restart. New config options and new messages merge into your existing files on their own, with your edits and comments kept. One thing to know: if an update changes the default of an option you already have, your file keeps its old value. Change it by hand, or delete config.yml and restart to get a fresh one with every new default.

Next step

Build your first arena: Arena Setup.

On this page