Respawned Dragon

Registry name

etfuturum:ender_dragon

Audit correction: previously written as etfuturum.respawnedDragon. The registration deliberately reuses the vanilla name ender_dragon so that dragon-respawn logic can find the entity. Evidence: core/proxy/CommonProxy.java:251 registerEntity(EntityRespawnedDragon.class, "ender_dragon", 10, ...)

Basic info

• Health: Inherited from EntityDragon (standard Ender Dragon health)
• Armor: Inherited from EntityDragon
• Size: Inherited from EntityDragon (large)
• Spawn conditions: Only spawns through EntityPlacedEndCrystal logic (when 4 placed end crystals on the End portal are all valid)
• Drops: XP orbs (see below), but no equipment/ender dragon drops
• Behaviour: Variant of the Ender Dragon that spawns after the End is re-charged via end crystals. Has an extended death sequence.

Extended death sequence

The key difference from a normal dragon: onDeathUpdate() behaviour after death begins:

Ticks	Event
1–180	Normal death animation (particles, movement)
180–200	Huge explosion particles at random offset positions around the dragon
Every 5 ticks (after 150)	Spawns 1000 XP orb at dragon position
200	Spawns 2000 XP orbs total, then entity dies

This gives a dramatic XP burst on the second kill compared to a normal dragon’s single orb drop.

Notes

• Extends EntityDragon directly
• No override of attackEntityAsMob, AI, or any other behaviour
• Used exclusively for the End crystal respawn mechanic in EntityPlacedEndCrystal
• playBroadcastSound(1018) at tick 1 (same as vanilla dragon death broadcast)
• Does NOT reset the End — the original dragon’s death handles the End victory state

Configuration gate

• Entity registration (shared if with end_crystal, id 9): ConfigEntities.enableDragonRespawn, key enableDragonRespawn, default ON (configuration/configs/ConfigEntities.java:69). The option’s own description calls the implementation a “crude implementation of respawning the dragon using four End crystals”, which is more accurate than implying a full dragon rework.