https://www.multimuse.app/dashboard/storyline
Settings
Open Settings from the Story Line toolbar.
Publishing
| Setting | What it does |
|---|---|
| Publish Story Line | Makes the viewer public and enables Story Line launch options |
| Public view | Feed (Story Line cards) or Graph (story map) |
| Public start page | All Events, arc chooser, or a specific arc |
The muse card must also be public. A private card disables public Story Line publishing.
Use Publish all Story Lines on the main Story Line page to publish every eligible muse at once.
Appearance
Under Story Line display:
-
Upload Story Line banner — shown at the top of the public viewer and Discord post
-
Accent color — timeline rail, glows, default event styling, and Discord accent
-
Muse avatar thumbnail — include the muse avatar in Discord output
-
Intro blurb — short introduction under the muse name
-
Save display — applies appearance changes
If unset, Story Line falls back to the muse’s profile banner, card color, and quote. Appearance is global for the muse, not per arc; individual arcs can still use their own accent colors.
Workspace
-
Default editor view — Timeline, Feed, or Graph
-
Story direction — Oldest first or Newest first
Your most recently selected editor view is also remembered in your browser and may take precedence over the per-muse default.
Event styles
Choose default colors for Scene, Backstory, Milestone, and Other. You can also manage saved custom event types.
Integrations
Integration settings include StageHand date syncing and Discord posting.
StageHand dates
If your server uses the StageHand calendar, MultiMuse can fill missing Story Line dates from tracked scenes.
Under Settings → Integrations:
-
Auto-fill dates from StageHand during archive sync for all muses
-
Sync this muse’s StageHand dates
Only empty date fields are filled. MultiMuse preserves dates you entered manually.
Date detection can use StageHand’s saved opener data, the Discord opener post, Story Line or thread title, archive title, and other events linked to the same thread.
Publish and share
A public Story Line requires:
-
A public muse card
-
Publish Story Line enabled
The public URL supports the full Story Line and direct arc links. Owners can preview an unpublished page; it will show Owner preview — not published yet.
Basic and Creative muse cards gain a Story Line button when the feature is published. The button launches the Story Line Activity inside Discord.
WARNING
Card action buttons use Discord components. If a Basic or Creative muse card is near Discord’s 40-component limit, simplify the card to leave room for Story Line and other actions.
Public viewer
Visitors can read a published Story Line in Feed or Graph view.
Viewer controls include:
| Option | What it does |
|---|---|
| Arc selector | Switch between Full Story Line and individual arcs |
| Oldest first / Newest first | Reverse event order |
| Feed / Graph | Change the presentation |
| Event types | Show or hide Scene, Backstory, Milestone, and Other |
| Co-muses | Show events involving any selected muse |
| Reduce motion | Reduce graph and card animation |
Preferences are saved in the viewer’s browser for that muse.
If the muse has a published Connections cloud, viewers can use See Muse’s connections to jump between the two features.
Post to Discord
Story Line can create a Components V2 post in a Discord text channel or thread. Large stories paginate automatically based on Discord’s component and text limits.
Each post can include:
-
Story Line or arc header
-
Banner, accent color, and optional muse avatar
-
Event titles, dates, locations, notes, and images
-
Open Story Line Activity button
-
Multiple page messages when needed
From the dashboard
Under Settings → Integrations → Discord activity:
-
Paste a Discord channel or thread link.
-
Choose Post to Discord.
-
After posting, use Refresh Discord post to update it or Open in Discord to jump to it.
Posting again to the same destination updates the existing post and removes surplus old pages.
NOTE
Auto-sync to Discord is marked as coming soon. Use manual posting or refresh for now.
From Discord — /storyline post
Options:
-
muse— muse whose Story Line to post -
destination— This channel (default) or Saved channel (dashboard) -
arc— optional arc to post instead of the Full Story Line
Posting to This channel also saves that channel for future dashboard posts.
To refresh a posted Story Line from Discord, use the message’s Apps menu Refresh action. Only the original poster can refresh it.
Open the Discord Activity
Use:
-
The Story Line button on a published Basic or Creative muse card
-
Open Story Line on a Discord Story Line post
-
/storyline timeline
With /storyline timeline, choose a muse or leave it blank to open the Activity picker.
The Activity must be launched from a server text or voice channel, not from a thread. Posting a Story Line to a thread is supported; launching the Activity from that thread is not.
Limits and troubleshooting
| Item | Limit |
|---|---|
| Event notes | 2,000 characters |
| Scene date | 64 characters |
| Custom type label | 40 characters |
| Arc title | 80 characters |
| Arc description | 500 characters |
| Arc slug | 48 characters |
| Image upload | Approximately 8 MB |
Discord posts automatically split into pages to stay under Discord’s 40-component and 4,000-character per-page budgets.
If an older tracked scene is missing, continue tracking it or add it manually in Story Line. Contact support if you expected an archive entry to be transferred and it did not appear.