Troubleshooting & current limits

My server or character is missing

• Use the same Discord account on the website and in the server.
• Confirm that Chronicler is present and online, and that you remain a member.
• The creation server selector excludes incomplete setups. Ask authorized staff to use the dedicated Complete setup page.
• Dice character selectors need your accepted, active sheet for that server and the selected game. An independent draft is not a linked playable sheet.
• Deleted records are hidden, and private sheets require the appropriate access.

A page or command says I lack permission

Check account and server roles separately. A Storyteller needs account approval and local authority. Delegated settings editors need Server Staff plus the permitted settings scope. Brewery authors need Brewer approval plus collection edit access.

After Discord role changes, let the bot refresh membership. Use /chronicle-settings to see permitted links. An unavailable control should be addressed through role configuration, not by changing a URL or another user's identifier.

My character will not save

• Read the field errors and the top-of-form message. Some errors automatically open a collapsed section.
• In Initial mode, check the distribution slots, package and separate grants rather than only total dots.
• Use a permitted Codex choice and an eligible rating. Resolve duplicate powers or specialties.
• A stale revision means the sheet changed after the page opened. Reload and compare the latest state before re-entering changes.
• In XP mode, unsupported fields are not saved as free purchases. Use the specific supported purchase or a reviewed change request.

An application will not approve

Confirm setup is complete, applications are open, and the player is a current Discord member. Check character limits, required approvals, self-approval rules, validation messages, and the submitted settings revision.

If Chronicle settings changed, obtain a fresh submission. The base may have been edited without resubmitting its fixed snapshot. Automated acceptance can also retain an application for staff when rule coverage is incomplete.

A result is missing from Discord

1. Check the web Dice Logs for a saved result before rolling again.
2. If there is a pending play request, it still needs staff confirmation; no dice or resources have been resolved yet.
3. Staff should check the Dice Channel and Chronicler's View Channel, Send Messages, Embed Links and Read Message History permissions.
4. Inspect delivery status. A saved result is retried as the same result; an uncertain delivery needs operator reconciliation rather than blind reposting.

The bot must be online to deliver web rolls. Site availability alone does not prove Discord delivery is connected.

Reroll buttons are missing or disabled

• Rouse/Rage checks and other procedures without Willpower rerolls do not have these controls.
• The roll may have no eligible dice, already have a later result, reach its reroll limit, or be outside its recorded window.
• Only the original player may act on the result. Linked character permissions and available Willpower are checked again.
• For a characterless roll, the manual Willpower confirmation is required.
• A menu opened before expiry does not extend the window. Check the closing time displayed on the result.

A procedure asks for a scene, session or night

Ask authorized staff to record the correct boundary through /scene or Manage scene & turn. For nightly Vampire procedures, record Rise for the night with the correct in-game date through Play actions. Do not invent a new boundary merely to reset a limited action.

Homebrew is published but not selectable

Check publication visibility, access to the collection, Chronicle approval of the exact revision, and activation in Sources & homebrew. The required game, parent categories and sources must also be allowed. A new revision does not replace the server's pinned selection automatically.

A custom definition can describe fields and mechanics without having a playable sheet adapter. Only supported integrations, such as the bounded dice profiles, become runtime actions after proper activation.

The site shows Be back soon!

The independent maintenance page is serving while the web application is unavailable or deliberately closed for deployment. Try again later. It does not require you to create another account or resubmit a transaction.

If a form was open during a deployment, reload it and inspect current state before submitting again. The server rejects stale records where supported, but refreshing avoids acting on outdated information.

Report a useful issue

• Include the page or command, the Chronicle and character involved, and the action you expected.
• Include a roll or application number when available, the approximate time, and the exact visible error.
• Describe the steps that reproduce it. A screenshot can help explain a layout problem.
• Do not share passwords, bot tokens, client secrets, or private content unrelated to the problem.

Current capability boundaries

Guided creation, review, per-Chronicle copies, supported XP purchases, dice, trackers, play procedures, shared assets, and reviewed homebrew are implemented. Not every published rule has an executable adapter; generic homebrew definitions do not install arbitrary new character-sheet systems. Source detail and automation coverage are separate.

The AI assistant is disabled, the old theme gallery is retired, and a separate internal messaging app is not available. Use the current navigation and the command reference rather than historical project notes.