Files
spigot-tyrant/design/user-stories/us-007-capture-and-place-mobs.md
T
dmg 777cbc6b4b
Release / release (push) Successful in 2m24s
CI / build (push) Successful in 1m16s
feat(tamer): capture and relocate mobs
2026-08-14 23:18:26 -04:00

29 lines
1.5 KiB
Markdown

---
type: User Story
title: "US-007: Capture and place mobs as a Tamer"
description: Let the Tamer move supported mobs without losing or duplicating them.
status: done
---
# US-007: Capture and place mobs as a Tamer
As the **Tamer**, I want to capture a mob and release it elsewhere so that I can relocate creatures safely.
## Acceptance criteria
- [x] The Tamer can use a named fishing rod on a supported targeted mob to capture it with no cooldown.
- [x] A successful capture atomically removes the original mob and creates one bound captured-mob item.
- [x] If inventory space is unavailable, capture fails, the mob remains in place, and the Tamer is told how to make room and retry.
- [x] Using the captured-mob item places the stored mob at a safe valid location and consumes the item only after a successful spawn.
- [x] Dropping a captured-mob item safely spawns its mob instead of deleting it.
- [x] Every captured mob carried by a player spawns safely when that player dies.
- [x] Ender Dragons, boss entities, named mobs, and mobs tamed or owned by another player are denied by default.
- [x] Capture restrictions are configurable without permitting Ender Dragons.
- [x] Invalid placement, full inventory, death, logout, restart, plugin disable, containers, and concurrent interaction cannot lose or duplicate a mob.
- [x] Stored mob data is validated defensively before spawning and cannot execute untrusted serialized behavior.
## Related
- [Use class ability items](us-014-use-class-ability-items.md)
- [Persistence model](../concepts/persistence-model.md)