Players · Chronicle staff · Homebrew authors · Bot & webapp staff
Chargen v5 1.0(a)
The alpha release, supported workflows, current limits, and a practical testing checklist.
Checked against the live application · 2026-10-02
What this alpha includes
Chargen v5 1.0(a) is the first alpha of the web application and Chronicler Discord bot. Use your Discord account to work with your Chronicles, reusable character bases, and each Chronicle’s playable copies.
- Guided and Unguided creation for the supported Vampire and Werewolf character types, plus the adopted Sorcerer v5 homebrew integration.
- Creation allowances and XP purchases, refunds before approval, banked unspent XP, applications, staff review, and separate Chronicle progression.
- Chronicle settings, staff permissions, dice and rerolls, damage and resource trackers, projects, and supported play procedures.
- NPC profiles and optional dedicated sheets, linked sharing or independent copies, and permitted PC/NPC posting to Discord channels and threads.
- The Codex with source references, and Brewery collections with authors, forks, contributions, review, publication, and Chronicle adoption.
Test a character from creation to play
- Sign in with Discord. Choose a ready Chronicle or start an independent character, then select its game and type.
- Build the initial sheet in Guided mode. Switch to Unguided and back to confirm your saved choices remain. Check derived trackers and any Predator Type or creation-package grants.
- Open XP. Make an eligible purchase if the character has a budget, inspect its cost, undo it if needed, and leave some XP banked.
- Submit to a Chronicle. Staff should request a change, review the revised submission, then approve it. Confirm that the accepted sheet is a separate Chronicle copy and its bank matches the approved build.
- Award and spend XP on the accepted copy. Check that its reusable base and other Chronicle copies remain unchanged unless the owners have explicitly enabled progression sharing.
- Test a dice roll and eligible reroll, then check the saved result, delivery state, and Willpower changes. Test tracker changes and the Chronicle’s configured permissions.
Test staff and homebrew workflows
- Use a normal player account and a delegated staff account as well as a server owner. Each should see only the records and actions their permissions allow.
- Create and review a project; confirm that the roll period, duration, and required approval are enforced.
- Create an NPC with and without a sheet. Check member visibility, a sharing invitation, and an independent copy in another Chronicle.
- Test character posting only in an intended play or testing channel. Confirm that channel restrictions and NPC posting roles apply.
- As a Brewer, create a fork, submit a contribution, and have an eligible author review it. Chronicle adoption should retain the approved revision.
Current limits
A Codex entry is not a promise that every effect in that entry is executable. Supported costs, tests, trackers, and eligibility checks are automated where implemented; scene judgments and unsupported prerequisites remain explicit review conditions. An arbitrary new game definition does not provide a complete new sheet or rules engine.
Red’s Flaming Hot Sauce retains a book-confirmation hold. Its entry distinguishes the wiki’s activation-cost notation from the standard Alchemy distillation cost. Missing source details are never treated as verified rules.
The AI assistant is disabled. Discord delivery requires a connected bot with the relevant server and channel permissions. An uncertain delivery must be inspected before trying again.
Back to top ↑Report an alpha issue
Send the issue to the project owner or your designated testing staff. Include 1.0(a), the page URL or command, steps taken, expected result, actual result, and the approximate time. Add the character, application, or roll identifier when relevant. For display problems, include the theme, device, and a screenshot. Avoid sharing account credentials or unrelated private sheet information.
Back to top ↑