Guides / Nomad Cairn

Commands

Every player and admin command, the permission each one needs, and how restore, held and archive work.

/cairn, /graves and /grave are the same command, so use whichever your players will type. Run with no arguments, it opens the grave GUI for a player. For install and what Cairn does, see the Cairn page. The permission nodes are listed in Permissions.

Command list

Tab completion only offers subcommands the sender has permission to run. A regular player never sees restore or verify.

Teleporting to a grave that is not yours needs cairn.admin.tp on top of cairn.command.tp.

Two permission families

Two kinds of node are easy to confuse.

• cairn.admin.* gates the commands. Listing another player's graves needs cairn.admin.list. Nothing else is consulted on those paths.
• cairn.loot.other and cairn.loot.other.bypass gate the marker, not the commands. They decide whether a player right-clicking someone else's grave in the world can take from it, together with grave.protection-minutes.

An admin node lets staff act through commands. The loot nodes let ordinary players take from each other's graves in the world. Granting one never implies the other.

Choosing a marker style

/cairn style on its own lists the styles you hold and may pick. /cairn style <style> sets one and /cairn style default clears it. The command only works when marker.allow-player-choice is true, and it says so when the feature is off. A change applies to your next grave. An existing grave keeps the look it was made with.

Restoring a grave

Use /cairn restore when a player insists items are missing and you have checked their history. It rebuilds a grave from the audit log as a new grave where you are standing, not where the player died.

If the ledger's own record shows the items were already handed to the player, restore refuses by default and will not hand out a duplicate. If you are certain the record is wrong, for example a witnessed delivery that never reached the player's inventory before a crash, run the same command again with confirm-not-delivered appended. That overrides the refusal on your authority, and the override is written to the audit log under your name.

A restore also brings back an archived grave, with a fresh full grave.expiry-minutes. Retained experience is not part of it, because XP leaves the ledger when a grave expires. See Configuration.

Held and archived graves

/cairn held answers where a player's items went without reading a log. With no argument it shows everything the ledger is holding. With a player name it shows only theirs.

/cairn archive <player> <grave id> takes a grave out of the world and off the player's list while keeping the items in the ledger. Use it for a grave somebody keeps reopening a ticket about, or one sitting in a build you are about to change. Nothing is destroyed: the row stays held, /cairn held still lists it, and /cairn restore brings it back. Both commands sit behind cairn.admin.restore because they are the two directions of one reversible operation.

Checking a missing-items report

1. Run /cairn history <player>. Every state change is listed with a time and a reason.
2. If the history shows the items were never delivered, run /cairn restore <player> <grave id>.
3. If the ledger says they were delivered and you are certain they were not, add confirm-not-delivered.
4. For an expired grave under the default on-expiry: archive, run /cairn verify. It lists every archived row with its custody id and the exact restore command. The same line is written to the server log when the grave is archived.

/cairn verify flags marker-missing as informational. A grave can be listed with its marker gone after a chunk was unloaded, regenerated or edited by another plugin. The items live in the ledger, not in the marker, and the sweeper re-renders the marker once the world is available again.