How It Works
An admin marks a pedestal (a Reinforced Deepslate block). Players gather a recipe of rare items and drop them on it — when all of them are present, a 25×25 vortex of particles erupts and the Rebirth Ritual begins.
Players standing inside the vortex are slowly granted lives — up to 2 each.
The first life is granted at 8 minutes, the second at 15 minutes (the ritual's end).
A ritual heals at most 4 players — the first 4 to step into the vortex claim the slots.
Only a single ritual can be active server-wide. Each lasts 15 minutes.
Step outside and you're out. Leaving the vortex permanently forfeits any lives you haven't yet earned from that ritual — returning doesn't restore your eligibility.
Starting a Ritual
1. Place a pedestal (admin)
Look at a block and run /pedestal set. It becomes a numbered Reinforced Deepslate pedestal, saved to pedestals.yml. You can have several; they're identified by number in commands.
2. Offer the recipe
Drop all of these onto the pedestal (any players can contribute). Once the full set is resting on it, exactly the recipe is consumed and the ritual begins — extra items are left untouched.
Ritual Rules
| Rule | Behaviour |
|---|---|
| Duration | 15 minutes. |
| Concurrency | Only one ritual active at a time, server-wide. |
| Area | 25×25 centred on the pedestal (≈12-block radius), with a vertical tolerance. |
| Who's healed | The first 4 players to enter the vortex claim the heal slots. |
| Lives per player | Maximum of 2 — one at 8 minutes, one at 15 minutes. |
| Eligibility | Continuous presence required; leaving the radius forfeits remaining grants permanently. |
| Lives cap | Grants clamp to the SMP's configured maximum — a player already at the cap gains nothing. |
Commands
shardsrebirth.admin· default: OPAll Rebirth commands are admin-only. /pedestal set must be run in-game (it reads the block you're looking at).
| Command | Description | Permission |
|---|---|---|
/pedestal set | Turn the block you're looking at into a Reinforced Deepslate pedestal (numbered). | shardsrebirth.admin |
/pedestal delete <id> | Remove a pedestal by number (refused if it's hosting an active ritual). | shardsrebirth.admin |
/pedestal list | List all pedestals by number. | shardsrebirth.admin |
/rebirth speed <multiplier> | Scale ritual timings — applies to the live ritual immediately. Testing lever. | shardsrebirth.admin |
/rebirth stop | Stop the active ritual. | shardsrebirth.admin |
/rebirth status | Show the active ritual's pedestal, elapsed/total, participants and speed. | shardsrebirth.admin |
Configuration
config.yml holds ritual behaviour; pedestals live in pedestals.yml (managed by commands). Reload by restarting the plugin.
ritual:
| Key | Default | Meaning |
|---|---|---|
duration-seconds | 900 | Total ritual length (15 min). |
life-grant-seconds | [480, 900] | When each life is granted, from start (8 & 15 min). Count = per-player cap. |
radius | 12 | Half-width of the square area (25×25 ⇒ 12 blocks each way). |
vertical-radius | 6 | Vertical tolerance above/below the pedestal that still counts as inside. |
max-players | 4 | Max players a ritual heals (first N to enter claim the slots). |
tick-interval | 10 | Ticks between scans / particle renders / milestone checks. |
default-speed | 1.0 | Time multiplier (1.0 = real time). Override live with /rebirth speed. |
recipe:
| Key | Default | Meaning |
|---|---|---|
items | (map) | Material → amount required on the pedestal to start. |
settle-delay-ticks | 15 | Wait after a drop before tallying what's resting on the pedestal. |
detect-radius | 1.6 | Horizontal distance from the pedestal that counts as 'on' it. |
particles:
| Key | Default | Meaning |
|---|---|---|
enabled | true | Toggle the vortex particles. |
colors | (5 colors) | Colours cycled around the vortex (named or #RRGGBB). |
points-per-ring | 60 | Particles drawn per ring each pass. |
rings | 4 | Concentric rings from the centre out to the radius. |
size | 1.4 | Particle scale. |
column-height | 8 | Height of the rising central column. |
Integration
Rebirth hard-depends on ShardsSMPv2 and grants lives through its public ShardsLivesService SPI — it never writes the lives table directly.
Every grant funnels through the core's single lives choke point — clamped to the cap, persisted, and audited in lives_log under the EVENT reason. Rebirth keeps no database of its own.
If the core is mid-reload and the SPI is briefly unavailable, the ritual still runs — it just skips the life reward rather than failing.
Testing (temporary)
Internal — delete this section after validation. Goal: prove a ritual starts from a drop, grants lives at the milestones, and that leaving forfeits eligibility.
Quick run
- Speed it up first:
/rebirth speed 60(15 min ⇒ ~15 s; milestones at ~8 s and ~15 s). - Look at a block and run
/pedestal set. - Drop the recipe on it: 4× enchanted golden apple, 2× heavy core, 3× player head, 5× diamond block.
- Confirm the vortex appears and you get the start broadcast.
- Stand inside — watch for the join message, then the two life-grant messages.
- Step out before a milestone and confirm the forfeit message + no further grants.
- Check
/rebirth statusmid-ritual;/rebirth stopto cancel.
Verify the grant landed
Lives are audited in the core DB (creds in ShardsSMPv2/config.yml):
SELECT uuid, delta, new_value, reason, created_at FROM lives_log WHERE reason = 'EVENT' ORDER BY id DESC LIMIT 10;
Expect one EVENT row per life granted (clamped at the cap).