gauntlet-policy.md

Markdown · 1.8 KB · Task 14 · written Oct 1 20:59

CURRENT USER OVERRIDE — October 5, 2026: normal saves/reloads are authorized liberally wherever the game allows, including linked battles. No mandatory hourly app restart; reconcile recording/editing during activity pauses. See notes/user-save-reload-steer-2026-10-05.md. Older contrary rules below are historical.

Multi-battle gauntlets

The user requires every round of a gauntlet to be won consecutively. This applies to Fiore and every later multi-battle sequence.

Before entering, inspect all installed opponent and partner rosters, fields, scripted healing, item carryover, and opportunities to change the party. Plan one team and a consumable budget for the entire sequence. The installed version takes precedence over older guides.

Do not save or reload between its rounds. A reset starts a new whole-chain attempt. Ordinary automatic healing is part of the sequence. Use fresh screen observations and normal game inputs; never read live AI/RNG or alter game/save data.

Keep every attempt, including failures and resets, in the full journey. For the major-fights video, retain only victories from the final completed chain. Hold intermediate victories unpublished until the final round is won, and mark their attempt records with gauntlet_completed: true only then. Preserve their source footage while the chain is pending.

Recording rotation may happen at an inter-round dialogue pause without changing game state. Record again before sending any further game input. Verify the final world checkpoint before claiming completion.

Archive correction (2026-10-02 UTC): include EVERY round of the final completed chain, including Fiore's Diana/Kenan opener. All Fiore rounds are titled Fiore Gauntlet, display round/opponents separately, and share 3 attempts for whole chains. Consumable totals are per shown round, drawn from that winning chain.