Files
aevolution/docs/playtests/M11_9_REPEATED_LIFE_PLAYTEST.md
T
dingo 8b54e7447a
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 4s
Close M11.9 for now and review the overhauled cellular UI
2026-10-17 11:35:56 -04:00

75 lines
4.0 KiB
Markdown

# M11.9 repeated-life playtest plan
2026-10-17: the maintainer closes this gate for now and authorizes proceeding to
M12. The original sample plan and observations remain historical evidence;
uncompleted tests and reported issues stay on the follow-up backlog. See the
[closure decision](../engineering/M11_9_DELIVERY_PLAN.md).
Recorded feedback: [2026-10-16 solo report](2026-10-16_M11_9_SOLO_FEEDBACK.md).
It preserves the original questions below, records a living-cell reconnect blocker
and six local retest issues, and does not grant product acceptance.
This plan predeclares what the M11.9 playtests try to learn, who plays, how sessions
run and what is recorded. It is written before any session so that results are not
read into after the fact. It is not a balance sign-off; every value it touches is a
trial value (ADR-0098, ADR-0120, ADR-0124, ADR-0125, ADR-0128).
## Preconditions
- A DEV region provisioned with the `cellular-v4` opening (rules 5: engulfment,
detritus, budding wildlife, offline freeze) on a server image that passed CI.
- An engineering client with the v10 path: movement, feeding, engulf, bud, the
mutation offer and chooser, and the death and restart flow. These screens are now
implemented (see CLIENT.md), including amended v10 costs and engulf reasons.
Record the client build and steering/feeding assistance settings; older clients
test less, and the notes must say which screens were present.
- A fresh grant bundle per participant (`renew-dev-m10.sh` output) and a three-hour
session window.
## Questions (fixed before the first session)
1. **Movement and food.** Can a new player find and keep feeding within two
minutes without help? How long until their first mutation offer?
2. **Tradeoffs.** When an offer appears, can the player say what each candidate
costs and gives? Does the chosen candidate change how they play afterwards?
3. **Predation.** Do players notice engulfment, both as hunter and prey? Do they
understand why an engulf attempt failed (size, membrane)?
4. **Descendants.** Do players bud on purpose? Do they recognize their wildlife
descendants as competitors, and does that matter to them?
5. **Death and restart.** Is the cause of death clear? After dying, do players start
again, and does their second life go differently from the first?
6. **Offline.** Does the 10 s linger feel fair, both when leaving and when finding a
lingering cell?
7. **Variety.** Across lives and players, do different genomes and play styles
appear, or does everyone converge on one build?
8. **Fun.** Would the player come back to the cellular stage? What made them want to
stop?
## Sample and sessions
- At least three participants, including at least one who has not seen the probe,
and ideally sessions with two players in the region at once.
- Each participant plays at least three lives (or 45 minutes), across at least two
sessions on different days, so that repeated lives and returning are observed.
- Sessions are recorded only as the participant agrees: notes always, screen
recording only with explicit consent.
## What to record
- Per session: date, region, server image digest, client build, which client
screens existed, participants (by a pseudonym chosen for the notes), and the
`evo-world-clone summary` output at the start and the end (ADR-0130).
- Per life: how it ended (cause as the player understood it, compared with the
summary's counts), what the player tried, and quotes about confusion or delight.
- Issues: anything that broke, felt unfair or was unreadable, with the tick if
known. File each as an issue with a proposed change.
## After the sessions
- Answer each question above with the evidence for and against; do not tune to one
seed or one participant.
- Propose changes to trial values only with the observations that motivate them,
and retest the change in a later session before treating it as settled.
- Record results in `docs/playtests/` with the date, and summarize the decisions in
the roadmap. Engineering success is not evidence of fun.