← All documentation

Players · Chronicle staff

Character projects

Propose an undertaking, approve its rules, and track time, attempts, Background stakes, and completion.

Checked against the live application · 2026-09-21

Propose or create a project

  1. Open your Chronicle, then Projects. Sign in with Discord and use an accepted character from that server.
  2. Choose Propose a project. Staff can use Create project to choose any eligible character in their Chronicle.
  3. Give it a title, explain the undertaking, and describe the intended outcome. Submit the proposal.
  4. Staff opens Rules & review, chooses the method and dice system, sets the stats and timing, and saves the approved terms.
  5. If changes are requested, edit the proposal and submit the clearer objective. Rejected proposals remain in the history.

Projects belong to the accepted Chronicle character. They are not attached to the reusable base. Only the character's player and authorized project staff can open its project records.

Back to top ↑

Configure the rules

  1. Choose Corebook Projects for Vampire or Accumulate successes for a Chronicle-defined undertaking. Werewolf and other supported dice profiles can use the accumulated method.
  2. Select the stats for the launch and progress pools. Backgrounds and Disciplines can be selected alongside Attributes and Skills. Add an approved pool adjustment if needed.
  3. For Corebook Projects, choose Scope. Launch Difficulty starts at Scope + 2 and increases after failed launches. For accumulated successes, set Difficulty from 0 to 10, the target, and whether a successful attempt adds successes or margin.
  4. Set the duration and its units. Separately choose weekly, every two weeks, monthly, or a custom number of days for the roll period, and the number of attempts allowed.
  5. Choose an existing Background and its dot increase if completion should automatically update that Chronicle sheet. Otherwise leave automatic dots at zero and describe the narrative outcome.
  6. Enter a staff note and save the rules to approve the project.

Approved terms remain editable until the first attempt. After rolling begins, pause or cancel the project instead of silently changing the terms of existing results. A replacement project can carry a newly agreed plan.

Back to top ↑

Choose real-world or story time

In Chronicle settings → Play & automation → Character projects, select whether new projects use Chronicle story time. With that setting off, new projects use real-world time. The choice governs both duration and roll periods, and is saved with each approved project. Changing the setting does not change existing projects.

The Story clock page lets authorized project staff set a starting story date, then move it forward. The first date may be earlier than today before any story-time project has been approved. Once approvals exist, the clock cannot move backward. Advancing it updates project progress and roll availability without rolling dice.

Weekly means seven days; every two weeks means fourteen days. Monthly periods use calendar months anchored to the approval date, with shorter months handled at their final day. Unused attempts do not accumulate. Pausing freezes duration and the roll schedule. Dates are displayed with their timezone.

The roll allowance starts when staff approves the terms. The duration starts when a Corebook launch succeeds and its required stake has been allocated, or on the first accumulated-success attempt. A failed launch uses an attempt but does not start the duration.

Back to top ↑

Make a project attempt

  1. Open the project and review its current pool, status, and remaining attempts.
  2. Check the named Dice Channel. Select Make launch roll or Make progress roll when available.
  3. From Discord, use /project-roll with the project number. Review the private confirmation, then press Roll in Dice Channel.
  4. Read the public embed or the linked website result. The attempt, dice, outcome, and progress change are saved together.

Every resolved attempt counts, including failed launches. Repeating the same submitted request does not generate another roll. Corebook project attempts do not allow Willpower rerolls or Blood Surge; the accumulated method also currently uses final project attempts without those modifiers. Hunger or Rage is taken from the linked character for the relevant V5 dice system.

Back to top ↑

Corebook progress and Background stakes

A successful launch starts a project with ten countdown steps. A regular success may require a Background stake; a critical launch avoids that commitment. The allocation screen shows the available Background dots. Confirm exactly the required total. Those dots leave the available sheet rating until the project ends; the project's own Goal pool may still use its committed dots.

The approved duration is divided into ten equal elapsed-time increments. Each increment advances the countdown automatically. A Goal roll contests the number of dice left on that countdown. The character counts each successful die once, including each 10, while the opposition keeps its critical-pair scoring. Winning advances progress by the margin. Losing damages Backgrounds, beginning with the committed dots.

If losses exceed the stake, the allocation page asks where the remaining available Background losses fall. Further rolls and cancellation are blocked until those losses are allocated. Exhausting a regular launch's stake ends the project; the critical-launch exception is retained. Narrative consequences of Hunger outcomes or a failed launch remain visible in the result for staff to resolve.

Back to top ↑

Completion, expiry and cancellation

A Corebook project completes when its countdown is exhausted. An accumulated-success project completes on reaching its target; if its duration ends first, it expires. Automatic time updates catch up after downtime. Story-time projects advance only when staff moves their clock.

Completion applies a configured Background reward once, without charging XP. Other outcomes stay ready for staff to record as fulfilled. A new trait, an XP charge, or a narrative consequence should follow its normal review or advancement process; the project record does not invent or grant it.

Cancellation releases remaining, unlost stake dots. It does not restore destroyed dots or erase history. Paused projects retain their commitments. Full sheet replacement is blocked while an approved project is open so its stat references cannot be erased; normal XP purchases and trackers remain usable. Character snapshots restore still-owned committed dots and do not copy the project or its schedule into another Chronicle.

Back to top ↑

Permissions and logs

Owners and Discord administrators can manage projects. Approved Storytellers with the Chronicle's Storyteller permission can do so too. Other server staff need both the Server Staff flag and the Manage character projects role permission. These checks apply on the website and bot.

The History tab records proposals, staff decisions, approved terms, rolls, clock progress, allocations, and outcomes. Dice results also appear in the existing Chronicle dice logs. Rule and pool snapshots remain on each saved roll. The project clock has a separate visible history.

Back to top ↑

Discord commands

Discord commands
CommandUse
/projectsList your projects, or show one project's status and workspace link.
/project-proposeSubmit a character, title, goal, and optional outcome.
/project-rollReview and confirm an available attempt.
/project-manageRequest changes, reject, pause, resume, cancel, or record fulfillment, as permitted.
/project-clockStaff: set an aware story date, for example 2026-10-01T20:00:00+00:00, with a reason.
Back to top ↑