acdream/docs/research/2026-08-26-issues-444-445-447-test-script.md
Erik f6fe0f2a4f
All checks were successful
CI / linux-portable (push) Successful in 3m27s
CI / windows-gate (push) Successful in 6m42s
CI / release (push) Successful in 2m12s
fix(client): restore retail interaction parity
Harden keyboard and camera routing, inventory and vendor interactions, chat/emotes, relog portal flow, and paperdoll rendering. Add retail research, connected gate coverage, and release-gate validation.
2026-08-26 20:45:11 +02:00

2.2 KiB

Issues #444, #445, #447 — consolidated owner gate

Run these checks together on the next connected test build. They deliberately require no special probes; record the client log and one screenshot per section. If a split fails, also record the exact visible error text.

#444 — alternate-currency vendor balance

  1. Open a vendor that accepts an alternate currency and note the amount shown in both the Items cost sentence and the Buying-tab purse line.
  2. Buy one item.
  3. Confirm both visible amounts decrease immediately and remain correct after the server refresh. Close/reopen the tab and vendor and confirm the amount does not bounce back to the old snapshot.
  4. Buy All once with enough currency, then once without enough. Confirm the first uses the refreshed holding and the second shows retail's insufficient- money notice without sending a purchase.

#445 — inventory and vendor partial stack splits

  1. In the main pack, select a stack of 10, set the slider to 2, and drag it to an empty main-pack slot while at least one side bag is equipped.
  2. Confirm the source becomes 8 and a new stack of exactly 2 appears at the chosen loose-item position; no error should appear.
  3. Repeat into an open side bag and confirm the same 8+2 result.
  4. Reset to a stack of 10, select 2, and drag it onto the vendor Selling list. Confirm the client prints Splitting the <name> before selling them, then the staged row resolves to the new stack of 2 rather than the source stack.
  5. Press Sell All and confirm exactly 2 are sold and 8 remain.

#447 — @acecommands multiline response

  1. Run @acecommands on the test account.
  2. Confirm command text is visible, consecutive server lines are readable, and there is no screen of blank chat rows.
  3. Scroll through the retained result. A response beyond retail's 10,000- character transcript cap should retain the newest complete command lines instead of blanking the entire response.
  4. Run @acehelp acecommands and one ordinary chat command afterward; confirm their text and normal chat presentation remain intact.

Pass all three sections on one exact binary, then mark #444/#445/#447 owner-accepted together.