Skip to main content
Everything runs through /relics. The alias is /relic. <relic> is a relic id: storm, inferno, void, gravity, blood, orbital, or a custom relic id. Tab completion lists the relics your server runs. Claiming a relic, casting its power and picking one up need no command and no permission.

Players

Admins

The console can run every command except opening the board, setaltar and spawn <relic> here. PRO-only commands on Lite reply with That's a Relics SMP PRO feature. See /relics pro.

Command notes

  • spawn only works on a relic that is at home. Otherwise you see That relic is already out. Reset it first.
  • give needs a free inventory slot. It doesn’t announce anything
  • reset <relic> announces the return in chat. reset all sends everything home quietly and confirms to you
  • reload tells you how many values were invalid and fell back to defaults. From 1.1.0 it refuses a config.yml with a YAML error and changes nothing. Adding or removing custom relics still needs a restart. See Configuration

The relic board

/relics opens a read-only board with every relic on the server. Nothing can be taken out of it.
The Relics board showing six relic icons and the How relics work book
Each relic icon shows:
  • Status: waiting at its altar, no altar set, held by a player, dropped on the ground, or its offline holder and the time left
  • Last seen: the holder’s last known spot and world
  • Active with its cooldown, and Passive
A relic at its altar shows as gray dye. A relic that is out shows as its own item, with an enchant glint. The book explains the rules to new players. On PRO, custom relics fill extra rows below the six built-ins, seven to a row. On Lite, admins see the four PRO relics as locked barrier icons. Set hints.pro: false to hide them. Admin actions. Players with relics.admin can also act from the board: Change the slots and icon materials under menu: in config.yml. Change the title and lore in messages.yml. See Configuration.