Repository navigation
Troubleshooting
Start with read-only checks:
/dragon system version
/dragon system status
/dragon system validate
/dragon system health
/dragon altar validate
/dragon event status
Do not start with a reset. Preserve evidence and take a stopped-server backup before any confirmed repair.
DragonAltar disables itself when editable configuration fails validation.
- Read every DragonAltar validation line in console.
- Fix only the named path.
- Check YAML indentation and quoting.
- Restart Paper.
- Run
/dragon system validate.
Common causes:
- Invalid material, sound, or particle name
- Bad server mode or transfer policy
- Negative duration
- Radius above a hard ceiling
- Fractured teleport maximum below its minimum
- Energy maximum changed from 100
- Invalid Rev Heat threshold order
- Inferno mobility cap above Hunt duration
- Bulwark maximum below minimum
- Invalid ritual mode or Elytra priority
- Animation action misspelling
If /dragon system reload encounters invalid configuration, it can disable the plugin. Use a restart after correcting it.
Confirm the setup session:
/dragon setup status
Staged points are not saved until:
/dragon setup save
/dragon confirm <token>
If the session expired after 15 minutes of inactivity, begin again and restage the missing values.
Check:
- Saved world is an End environment
-
event.end-worldmatches the intended world - Bedrock exists within 6 horizontal blocks and the allowed vertical search
- Crystal points are in the same world
- Each crystal is 2 to 6 horizontal blocks from the fountain
- Vertical difference is no more than 4 blocks
- North is actually north, and likewise for south, east, and west
Use explicit coordinates when standing on a block would save an imprecise player location.
The saved egg display point cannot be inside a solid block. Move it to clear space, save setup, and run:
/dragon dev altar repair-displays
/dragon altar egg inspect
Inspect:
/dragon altar egg inspect
/dragon altar recipe inspect
/dragon dev altar displays
Reconcile:
/dragon dev altar repair-displays
If the altar is dormant or has no unclaimed souls, missing claim displays are expected. Use /dragon altar status before forcing a preview count.
Run /dragon protection enable, then set both corners with /dragon protection setpos1 and /dragon protection setpos2. Both corners must resolve to the same world. This is a start blocker when internal-protection.required-for-event is true.
Then run:
/dragon protection status
Also confirm both corners are in the same world.
Run:
/dragon event preview
The preview reports preflight failures. Typical blockers:
- Existing soul records
- Invalid setup
- Invalid fountain or crystal ring
- Existing dragon
- Active End battle or respawn
- Occupied crystal site
- Event already started
Do not use a developer test dragon as a substitute for a failed official preflight.
Preserve loaded entities. Collect:
/dragon event status
/dragon event dragon-info
/dragon event locate
/dragon system entities
/dragon system health
Then take a backup and preview:
/dragon event rescan
or:
/dragon event recover
One matching dragon can restore Active. Four matching event crystals can resume summoning. Multiple matching dragons or a partial crystal set requires manual review. Existing souls take priority and restore the altar path.
Check whether it was the stored canonical dragon:
/dragon event dragon-info
/dragon event status
Test dragons and unrelated dragons do not progress the official event. The normal death path also waits the configured reward and awakening delays.
If ScaledEnderDragon is installed, confirm it did not replace the vanilla respawn path and that the official dragon was still accepted by DragonAltar.
The player must:
- Right-click the exact configured interaction block
- Wait until the official event is defeated
- Use an active altar with an unclaimed soul
- Not already be Dragonborn
- Pass every eligibility check
- Wait until no other initial ritual is active
Staff can inspect eligibility with:
/dragon dev eligibility explain <player>
For Elytra, review:
- Enchantment acceptance
- Renamed-item acceptance
- Custom-lore acceptance
- Equipped chest-slot setting
- Blocked PDC keys
- Offering mode
Use:
/dragon dev ritual test-elytra <player>
/dragon dev ritual recipe-plan <player>
The target must be online.
For pedestal modes, confirm dropped item entities are within 1.5 blocks of a configured pedestal. Items inside containers do not count as pedestal deposits.
Free inventory space and run:
/dragon refunds
Staff can check and retry:
/dragon admin refunds inspect <player>
/dragon admin refunds give <player>
The exact-item refund includes metadata. Overflow remains pending rather than being dropped.
The trigger runs when a player closes a qualifying single chest.
Confirm:
- It is not half of a double chest
- All four offering counts are present
- Weakness potions are drinkable regular or long variants
- The foundation blocks are exact
- All four White Candles are lit
- All four Soul Sand pads exist
- One player stands on each pad
- The closing player is one of the four callers
- At least one soul currently has a holder
The leader has 60 seconds by default. No offerings are consumed on expiry. Close the chest again after all callers are ready.
The tracked chunk may be unloaded. DragonAltar waits for a known unloaded tracked entity rather than immediately spawning a duplicate.
Check the public boss bar and allow the tracked chunk to load. On chunk load, DragonAltar reconciles duplicates and keeps one canonical creature.
Do not summon a replacement manually.
It returns when:
- There was no player killer
- A current Dragonborn would have landed the killing blow
- Normal soul assignment rejected the claimant
A non-Dragonborn player must land the accepted final blow and must not already hold a soul.
Pending is recoverable. Check that at least one online player passes:
/dragon dev eligibility list
/dragon dev eligibility explain <player>
Natural deaths use the countdown. Combat-log failures and the PENDING_TRANSFER collision policy can wait for join or startup recovery instead.
- Ask the player to free an inventory slot.
- Have them run
/dragon focus. - If needed, run
/dragon admin repair <player>.
The Focus is not restored into a full inventory and is never dropped on the ground.
Check:
- Player is online, alive, and not Spectator
-
dragonaltar.useis granted - The selected ability belongs to the player's soul
- Current energy is sufficient
- Own and shared cooldowns are ready
- Lamari's Fault is cast while flying
- Lamari's Reckoning is cast on solid ground
- Resonance participants are still online, in the same world, in range, and off shared resonance cooldown
- Another plugin did not cancel selection or casting
Use:
/dragon admin energy view <player>
/dragon admin cooldown view <player>
/dragon dev input status <player>
Match the error to these checks:
- Owner plugin is enabled
- Registration is on the primary server thread
- One add-on registration per owner
- Unique 2 to 32 character lowercase add-on id
- Namespace is not
dragonaltar - Metadata fields are nonblank
- Add-on is registered before its abilities
- Ability id starts with the exact add-on namespace and colon
- Local ability id is 2 to 48 lowercase characters
- Display name and category are present
- Energy is 0 to 100
- Cooldown is 0 through 24 hours
- At least one valid soul is listed
- Ability id does not collide with a built-in, resonance, or another add-on
Do not cast to DragonAltarApiImpl. Load DragonAltarApi from ServicesManager and declare depend: [DragonAltar].
Provide:
- DragonAltar 1.4.23
- Paper build
- Java version
- Reproduction steps
- Relevant configuration validation message
- Whether optional integrations are installed
- Whether the issue reproduces with shipped defaults on a test server
Remove names, UUIDs, paths, audit detail, network information, and unrelated secrets.
- Home
- Installation
- Altar Setup
- Ancient Dragon Event
- Dragon Souls
- Rituals
- Abilities
- Resonances
- Player Guide
- Administrator Guide
- Configuration
- Ability Configuration
- Commands
- Permissions
- Add-on Development
- API Reference
- Integrations
- Data and Privacy
- Troubleshooting
- FAQ
DragonAltar is owned by Silverfox0338.