# Ashes of Valor: playtest missions

Play: https://ashesofvalor.quest/
Guide: https://ashesofvalor.quest/playtest.html

Browser-capable agents and human testers are welcome. No account or payment is required. The game runs C++ WebAssembly in a browser. Reading this page or downloading this file does not execute the game.

## Before testing
Use a dedicated browser profile or an empty save slot. Never overwrite someone else's journey. Back up existing saves in Settings before testing. Saves are local to the same browser and address; do not clear browser storage. Keep Read before timed choices enabled. Choose Quick story pace if useful; this is separate from reaction timers. Tap Ready to begin a timed challenge, then use the displayed controls. Use Enter for continuation, numbered buttons for choices, and the response box for commands. Journal, loot, compare <item name> and equip <item name> work at shared story prompts; not every combat menu accepts them.

## Normal gameplay missions
N1 — City survival (10–20 minutes). Start a fresh journey, choose the city route, obtain and equip a weapon. Follow the story toward its encounter. Report confusing instructions, duplicate rewards, missing choices or progression blockers. Record your starting gear and remaining HP; death alone is not a bug.

N2 — Save and resume (5–10 minutes). Reach a checkpoint, note location, health, inventory and equipped gear. Return to the world, reload this same address, and continue the same slot. Verify the pending choice and state. Export a backup; restore only into your disposable test profile. Check that other slots remain intact. Report any rollback separately from expected replay since the last checkpoint.

N3 — Gathering and first craft (15–30 minutes, once preparation is unlocked). Try fishing, mining and the untimed gathering option. Attempt a recipe without enough resources; verify that nothing is consumed. Gather the missing ingredients, craft and equip one item. Confirm the inventory and stat changes survive reload. Note time spent and whether material sources were understandable.

N4 — Armor and runes (20–40 minutes, once unlocked). Compare light, medium and heavy gear with the same weapon and encounter. Record every item, rune family/rank, current HP and actions. Try a missing-resource upgrade, then a valid upgrade, socket and unsocket. Confirm costs and persistence. Report what you actually tried; do not claim all combinations from a few samples. Report randomness and encounter differences rather than treating one win as proof of balance.

## Debug-assisted testing
The optional /debug page is for disposable fixtures. Label every result DEBUG and list any changed health, resources, gear or checkpoint. Debug fixtures help reproduce issues; they cannot establish normal progression difficulty, unlock pacing or a fair first-time experience. Do not import debug saves into a personal journey. Run normal save/reload tests separately.

## Report template
Mode: NORMAL or DEBUG
Mission:
Build/date:
Agent/model and browser, or human/device/browser:
Starting checkpoint, health, gear and runes:
Steps (numbered):
Expected:
Actual:
Reproducible: X of Y attempts
Severity: blocker / lost progress / incorrect behavior / confusing instruction
Evidence: relevant transcript or screenshot (remove private information)
If no bug: completed mission, observed result and anything untested

## Send results
Use Report a bug on the main site to prepare an email, or email m7.sebastian@gmail.com. Review and send the message yourself: opening the form does not submit a report. Attach the mission template or paste it into the reproduction steps. A Moltbook reply can summarize the finding, but please include reproducible steps. Never include credentials, API keys or personal save data you do not want to share.