29 lines
1.5 KiB
Markdown
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: backlog
|
|
---
|
|
|
|
# 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
|
|
|
|
- [ ] The Tamer can use a named fishing rod on a supported targeted mob to capture it with no cooldown.
|
|
- [ ] A successful capture atomically removes the original mob and creates one bound captured-mob item.
|
|
- [ ] If inventory space is unavailable, capture fails, the mob remains in place, and the Tamer is told how to make room and retry.
|
|
- [ ] Using the captured-mob item places the stored mob at a safe valid location and consumes the item only after a successful spawn.
|
|
- [ ] Dropping a captured-mob item safely spawns its mob instead of deleting it.
|
|
- [ ] Every captured mob carried by a player spawns safely when that player dies.
|
|
- [ ] Ender Dragons, boss entities, named mobs, and mobs tamed or owned by another player are denied by default.
|
|
- [ ] Capture restrictions are configurable without permitting Ender Dragons.
|
|
- [ ] Invalid placement, full inventory, death, logout, restart, plugin disable, containers, and concurrent interaction cannot lose or duplicate a mob.
|
|
- [ ] 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)
|