Players · Chronicle staff
Post as your character
Send character actions to Discord from the website or with !pc Trigger: Your action.
Checked against the live application ·
Enable posting for a Chronicle
- Open Chronicle settings → Running the game → Character posting.
- Turn on Allow players to post as their characters. It starts off in each Chronicle.
- Use Add and Remove to move channels or thread parents between the available and allowed lists, then save.
- Chronicler needs View Channel, Manage Webhooks, and the appropriate sending permission in those destinations. Players must also be able to access and post there.
Player and NPC posting have separate switches and allowed-destination lists. Turning player posting off prevents new posts and stops queued posts when the bot checks them. Already delivered Discord messages remain.
For command replacement, give Chronicler Manage Messages and Read Message History as well as its webhook and sending permissions. These can be set on its server role; channel overrides must still permit them. Message Content Intent must be enabled for the bot in the Discord Developer Portal.
Back to top ↑Post from the website
- Open the Chronicle and choose Character posts, or open your accepted character’s sheet and choose Post as character.
- Choose a channel or active thread and write the action.
- Select Preview, review the character name and destination, then choose Publish to Discord.
- The posting log shows delivery progress, the submitted action, and a link to the delivered Discord message. You can cancel a post while it is still queued.
Post from Discord
- For a PC, open Character posts on the website and save an optional short posting trigger beside your character. For an NPC, use the Posting trigger field in Edit NPC. Full names also work.
- In an allowed Discord channel or thread, type !pc Trigger: Your action or !npc Trigger: Your action.
- Sending the command publishes directly in that same channel or thread with the character’s name and portrait. There is no Discord posting dialog.
- After confirmed delivery, the bot removes the original command if it is unchanged and it has permission to remove it. Failed or uncertain posts keep the original command. Check the website posting log if delivery needs attention.
Triggers ignore capitalization. If more than one available character matches, the bot asks for a distinct name or trigger. The full name and the custom trigger both go through the same ownership, NPC-role, and channel checks.
These commands accept text only. Attached files, stickers, polls, and forwarded messages are not proxied. An edited or deleted command waiting in the queue will not be published from its earlier text. Keep the action after the colon within 2,000 characters.
Back to top ↑Which characters can post?
You can post only as your own accepted, playable copy of a character in this Chronicle. An independent base, pending application, archived character, or another player’s sheet does not qualify. Temporary guest access must still be valid. Owning a copy in another Chronicle does not authorize posting here.
Discord displays the character’s name and portrait. A portrait is optional. Actions can contain up to 2,000 characters. Mentions do not send user, role, or everyone notifications. The bot checks ownership, Chronicle settings, current server membership, and destination permissions again before delivery.
Back to top ↑Delivery logs and staff controls
Players see their own posts; the server owner, Discord administrators, and Chronicle staff can review the Chronicle’s player posting log and cancel queued posts. System staff can pause player-post delivery separately from NPC delivery in Admin Workspace. Paused delivery leaves posts queued.
Check Discord means delivery could not be confirmed. Inspect the destination before submitting the same action again. The system does not automatically resend uncertain posts, which avoids accidental duplicates.
Back to top ↑