Control ownership and expired panels
Refuse another character’s action and stale review without damaging current progress.
Prerequisites: two dedicated, consenting test accounts and an operator-assisted staging environment for cross-account request checks. Player-visible observations are safe to share only after removing account/session credentials. Do not use another real player’s controls or private inventory.
Step by step
Tick a step after observing the expected result. Saved on this device only.
01Check private receipts
A and B each open /play independently in the same test channel and compare what each client can actually view.
Gameplay menus and receipts are private responses; no automatic public inventory dump or mention broadcast appears.
02Create an owner-bound review
A opens a low-impact Visit review or an owned work-action control. Keep it uncommitted.
The review has one authenticated owner; opening it does not mutate the character.
03Exercise an account mismatch in staging
An operator uses the existing transport test harness or a controlled staging request to submit A’s review through B’s authenticated test identity.
The handler rejects the ownership mismatch before any mutation. Do not expose the review token or session credential in a public screenshot.
04Let a menu expire naturally
Leave a dedicated /play panel unused for more than one hour, then select its old control.
The expired panel directs the tester to reopen /play. Expiry does not erase the character.
05Check a stale work turn
During an active test batch, open the same turn in two client views. Commit one current-turn intervention, then try the old review in the other view.
The stale work turn is refused; it cannot apply a second intervention to the new state.
06Recover with a fresh panel
Reopen /play or refresh the browser, then make a valid current action.
The owner can continue normal play with preserved inventory and activity state.