← All documentation

Chronicle staff · Players

Chronicle NPCs

Create NPC profiles, create optional NPC sheets, share between Chronicles, and post character actions to Discord.

Checked against the live application · 2026-10-02

Create and find NPCs

  1. Open your Chronicle and choose NPCs. Search by name, type, role, or location; filter NPCs created here or shared with this Chronicle.
  2. Choose Create NPC. Only a name is required. Add a portrait, aliases, and story details. Select Create a dedicated sheet for this NPC if you also want its mechanical details.
  3. Keep secrets in Home Chronicle staff notes. Ordinary profile details may be shown to members or shared with another Chronicle.
  4. Save the NPC. Creators with the Create NPCs permission can edit their own profiles; NPC managers can manage the full roster.

NPCs belong to a Chronicle. They do not use a player character slot or require a full sheet. Choose Create NPC sheet on its profile whenever a sheet is needed, then choose its game and character type. This creates a new sheet for that NPC. Edit its Identity, Attributes, Skills and Specialties, Advantages, Supernatural Abilities, Possessions, and Trackers in the home Chronicle. Only authorized home NPC staff and its permitted creator can access the sheet; revealing or sharing a profile does not reveal the sheet.

Back to top ↑

Choose roles and visibility

  1. Open Chronicle settings → Running the game → NPCs.
  2. Assign Create NPCs, Read staff-only NPCs, Manage all NPCs, and Post as NPCs to the appropriate Discord roles. Manage all NPCs also requires the Server Staff flag. The server owner and Discord administrators retain NPC management access.
  3. Leave member visibility off by default to keep new NPCs hidden. An NPC manager can use Visibility & local notes on an individual profile to reveal it.
  4. Use local notes for details specific to this Chronicle. These notes are never displayed in another Chronicle.

The Read staff-only NPCs permission grants access to hidden profiles and local staff notes. Creating one NPC does not grant access to every hidden NPC. Posting additionally requires membership in the server and access to the destination on Discord.

Back to top ↑

Share an NPC

  1. An NPC manager opens a home NPC and chooses Share with a Chronicle.
  2. Enter the receiving Discord server’s ID. Both servers need Chronicler, completed setup at the destination, and NPC sharing enabled.
  3. A receiving NPC manager opens NPCs → Sharing invitations, reviews the profile, and accepts or declines.
  4. Accepted shared NPCs start hidden from ordinary members. Receiving managers choose local visibility and maintain their own private notes.
  5. Either Chronicle’s NPC managers can end sharing. The home Chronicle keeps control of the shared profile; accepted Chronicles see updates to its ordinary details.

Home staff notes and the private NPC sheet do not travel with a share. Turning off new sharing prevents new invitations and acceptance; use End sharing to revoke an existing share. Archiving an NPC hides it from active rosters and prevents further posting in every Chronicle.

Back to top ↑

Post as an NPC

  1. In NPC settings, enable posting, assign posting roles, and select Allowed posting channels and thread parents. An empty destination list prevents posting.
  2. Open an accessible NPC and choose Post as the NPC. Choose a channel or active thread from the list.
  3. Write the action, choose Preview, then Publish to Discord. Discord formatting such as italics can be used in the action.
  4. The bot posts with the NPC’s name and portrait through a channel webhook. Discord continues to identify it as an automated message.
  5. Return to the NPC’s Discord posting log. Refresh to see delivery status and a link to the posted message. A queued post can be cancelled before the bot claims it.

Chronicler needs channel access, Manage Webhooks, and the relevant sending permission. Thread posting uses the parent channel’s webhook. Private threads require bot membership; archived or locked threads must be reopened first. Only active threads known to the bot appear, and synchronization can take several minutes. No webhook URL needs to be copied into Chargen.

The bot rechecks current server membership, role access, destination settings, and Discord permissions before posting. Mentions are sent without notifications. The author’s account remains in the posting log. If delivery is uncertain after a connection failure, check Discord before submitting again; Chargen does not automatically repeat an uncertain post.

Back to top ↑

Archive and restore

Home Chronicle NPC managers can archive a profile from its page. Archived NPCs stay in the database and are available through Include archived on the roster. Restore returns the profile to active rosters. Archiving, ending sharing, or changing permissions does not remove messages already published to Discord.

Back to top ↑

Post from Discord

  1. Open Edit NPC and set an optional Posting trigger, such as Jace. The NPC’s full name also works.
  2. In an allowed Discord channel or thread, send !npc Jace: Your action here.
  3. The action is posted directly with the NPC’s name and portrait. After confirmed delivery, the bot removes the unchanged command message when it has permission.
  4. Check the NPC’s posting log for delivery status. Failed or uncertain delivery leaves the original command in place.

NPC posting roles, visibility, sharing status, and Discord channel permissions apply. Matching is case-insensitive, and ambiguous triggers are rejected. Text only; attachments are kept in the original message and the action is not queued.

Back to top ↑

Make an independent copy of a shared NPC

  1. Open a shared NPC or its invitation in the receiving Chronicle. NPC managers can select Make independent copy.
  2. Choose a name and confirm. The copy starts staff-only, with its own editable profile and portrait and a source credit.
  3. Create a new dedicated NPC sheet if needed. Source sheets, private notes, posting triggers and message history are not copied.
  4. The original linked share remains available. End sharing separately if you no longer need it. Later source edits, archiving or ended sharing do not change the independent copy.

Both Chronicles must allow NPC sharing when the copy is made. Only one independent copy is created from each shared placement; retrying returns that copy. An archived copy can be restored by its receiving Chronicle rather than duplicated.

Back to top ↑