November 17, 2026 — In-game code list check
On a level 1 account we observed four codes in the in-game Ready list, including THANKYOUFOR30KMAJORFIXES, and saved a screenshot and notes. We updated the walkthrough for the current button-based interface. Redemption success remains unconfirmed; the two level-gated codes remain external reports.
November 17, 2026 — Wiki and verification workflow
- Expanded the code redemption guide with troubleshooting, resource planning and a documented test procedure. The five reported codes retain their reported status; no redemption result was invented.
- Published the Anime Crusaders wiki and 20 T1 form guides. Acquisition references, skill uncertainty and proposed team tests are separated.
- Linked detailed forms from the roster, added related-unit links, and corrected heading structure on the three core pages.
- Opened community evidence submissions with private screenshot storage, manual review and withdrawal receipts. Accepted evidence appears on relevant code and unit pages.
- Added a direct official Roblox metadata check to the source ledger. This verifies experience identity, not gameplay.
November 17, 2026 — Initial field guide
Launched the code tracker, role-based roster, saved team board, beginner checklist and summon probability calculator. Connected the production domain, optional analytics and search verification. Advertising remains optional through consent, with adult advertisements disabled in the publisher configuration.
How future corrections will be recorded
A material correction should identify the affected page, previous statement, replacement statement, evidence and review date. A new source-check date will not be used to imply a fresh gameplay test. Community observations remain in the live evidence ledger with their build and observation time; a later contradictory result can prompt review without erasing the historical context.
There are no accepted gameplay observations at this workflow’s launch. Use the submission form to provide a result we can review. An editor will decide whether it supports a code-status change, a skill correction, or only a narrower note about the tested conditions.