Skip to main content

ResurrectionChest Setup

First Boot​

Until setup is complete, ResurrectionChest posts a first-boot reminder ten seconds after each login by an admin with resurrectionchest.*. The message confirms the plugin is ready to use, points to /resurrectionchest setup, and reminds you how to register a chest (place a chest and put a sign that says [DeathChest] on it — or whatever you set Input name for death chest to).

ResurrectionChest works out of the box with vanilla chests, so there is nothing you must do here. The reminder stops appearing once setupDone is true in config.yml. Opening /resurrectionchest setup flips setupDone to true automatically, which permanently dismisses the message.

/resurrectionchest initialize opens guided setup. Recommended Setup, Manual Setup and Use Current Content each mark setup complete. Vanilla death chests work without downloading a pack.

Setup Menu​

/resurrectionchest setup

Opens the Nightbreak setup menu. From there, admins can:

  • view all ResurrectionChest content packs (Wooden Chest, Angelic Chest)
  • install or uninstall packs (which moves model files between FreeMinecraftModels' models and models_disabled folders)
  • filter packs by Free or Premium
  • check for and download a plugin update via the Plugin Update entry
  • download or update every pack at once with the download-all entry, which runs /resurrectionchest downloadall for you
  • open the Recommended Plugins list (the same view as /resurrectionchest recommendedplugins)
  • turn Automatic Updates on or off (the nightbreak.autoDownloadPluginUpdates setting — see Config and Permissions)
  • read installation instructions and open relevant Nightbreak links via the info button

When a pack is installed or uninstalled, ResurrectionChest reloads FreeMinecraftModels automatically so the chest props refresh.

/resurrectionchest downloadall downloads the plugin update (if any) and every available ResurrectionChest content pack from Nightbreak in one go (requires a linked Nightbreak account). /resurrectionchest downloadallcontent downloads only the content packs, and /resurrectionchest updatecontent (alias updateallcontent) re-downloads only the content packs that are outdated.

If a pack's files got damaged or deleted while the version number still reads as current, /resurrectionchest forcereinstallcontent <package|all> re-downloads it anyway. The package argument tab-completes to all, wooden-chest, and angelic-chest; use all to redo every pack that is already downloaded, or name the slug directly if a pack's files went missing entirely.

Manual Imports​

Downloads land in, and hand-placed packages can be dropped into:

plugins/ResurrectionChest/imports

Leave package archives intact. ResurrectionChest unpacks the folder on startup, routes model files into FreeMinecraftModels, and refreshes FreeMinecraftModels automatically when models were installed. See the shared guide: Manual imports vs in-game management.

Registering A Chest​

  1. Place a chest.
  2. Place a wall sign attached to that chest.
  3. Write the configured trigger text on line 1 or line 2 of the sign. Capitalization does not matter.

The default trigger text is:

[DeathChest]

When the sign is accepted, ResurrectionChest:

  • rewrites the sign (line 1 is cleared, line 2 shows the trigger text in purple, line 3 shows the player's display name, line 4 is cleared)
  • stores that chest for the player
  • removes the player's previous registered chest entry if they already had one, including deleting that old chest's setup sign (the old chest block and its contents are left alone)
  • tags the chest and sign blocks with an ownership marker on the following tick, so the plugin can tell its own blocks apart from look-alikes later

If another plugin cancels sign placement, no registration is committed and the previous chest remains registered. Breaking a chest or sign only removes its registration once the break actually takes effect. A cancelled break does not unregister it.

There is no command-based chest-registration flow.

Setup Rules​

  • The player needs resurrectionchest.use.
  • Setup is blocked in blacklisted worlds.
  • The accepted sign must be a wall sign attached to a chest.
  • Any wall-sign material works because the code checks for wall-sign block types, not one specific sign material.
  • The block behind the sign must be a plain chest. Trapped chests, barrels, and other containers are rejected.
  • The chest must not already be registered to another player. If it is (either half of a double chest counts), the sign is left as ordinary text and the player is told the chest belongs to someone else.
  • The player must be allowed to build at the chest block. ResurrectionChest uses MagmaCore's shared WorldGuard / GriefPrevention lookup and location-ownership protection reports. A denial refuses registration with the Chest protected region message text. With no protection or ownership provider there is no extra restriction — see Config and Permissions.

Single And Double Chests​

  • A normal single chest works immediately.
  • If a registered chest later becomes part of a double chest, ResurrectionChest detects the change one tick after the block is placed, tags the newly joined half (and any signs on it), and swaps the prop to the double-chest model.
  • If that newly joined half already belongs to a different player's registration, the whole registration is discarded rather than absorbing the other player's chest.
  • Death drops can fill both sides of a double chest inventory, all 54 slots.
  • A double chest can cross a chunk border. The server only pairs the two halves while both chunks are loaded, so when the owner dies far away ResurrectionChest loads the chunk holding the other half before it checks ownership and moves the items. It loads that chunk normally and does not keep it force-loaded. If the halves still do not pair, the console logs a warning naming the player and the chest location, and only the registered half receives items.
  • With the default security settings, every half of the chest must still carry this player's ownership tag on death. If one half was replaced out from under the plugin, the chest counts as missing.

Removal Behavior​

Breaking either of these removes the registration:

  • the registered chest
  • an attached sign belonging to that registered chest

When a registration is removed (by any trigger — breaking the chest, breaking the sign, or destroying it through the FreeMinecraftModels prop), the plugin also removes attached wall signs that pass its ownership check. Those signs are deleted, not dropped as items.

A registration is also dropped automatically when the plugin can no longer prove the blocks are its own: if any chest half at a stored location has lost its ownership tag, or now carries someone else's, the registration is discarded on the next startup, chunk load, or model refresh and a warning naming the owner's UUID and the chest coordinates is written to the console. The chest block itself is left in place. Sign tags are only re-checked when the plugin re-tags its blocks — when a double chest half is joined, and when an older registration is migrated onto the current ownership tags. Set Enable high compatibility / low security mode for plugin conflicts to true if another plugin on your server strips that block data — see Config and Permissions.

The plugin also cancels attempts to edit the registered setup sign in place.

If a custom chest prop is active, left-click on the prop also removes the registration (only the chest's owner can do this — see Config and Permissions).

Admins can wipe every registered chest at once with /resurrectionchest clear. For each tracked chest it drops the chest's inventory on the ground, then removes the chest and any attached setup signs and clears the stored registration.

This cleanup follows the configured ownership checks. Blocks that fail those checks are left alone. If a chest's world is unloaded, only its registration is cleared; the blocks in that world remain.

Protection Warning​

ResurrectionChest is not a protection plugin.

  • It does not stop other players from opening the physical chest.
  • It does not stop other players from breaking the physical chest or sign if your server protection setup allows that.

Use region protection or another chest-protection solution if you need access control.

Troubleshooting​

  • Items do not go to the chest. Check that the player has resurrectionchest.use, that the sign used the configured trigger text, and that the chest still exists and is registered to that player (breaking it removes the registration). Deaths in a world listed in blacklistedWorlds, or with keepInventory on, are left alone.
  • The custom chest model does not show. The model is picked when the chest is registered. If FreeMinecraftModels or the model pack was installed later, or the player's model permission changed, break the chest and register it again. See FreeMinecraftModels Integration.
  • Before running /resurrectionchest clear, back up playerData.yml and any chest contents you want to keep. The command empties every registered chest onto the ground and removes the chests and their signs.

When asking for help, include the ResurrectionChest and server versions, your config.yml, the steps that reproduce the problem and the full server log. /logify uploads the log and returns a link.