简体中文
EnglishCan Scabard Be Shared With Players or Collaborators?
Updated
Yes. Scabard supports two distinct kinds of sharing: you can invite trusted collaborators into your world without exposing secrets to players, and you can share a player-facing view of what they should know while keeping the rest hidden. Both are built on the same visibility controls that let you mark pages, notes, and connections as secret until you decide otherwise.
Two audiences, two sharing modes
Scabard's own feature list separates these use cases, and the distinction matters when you set up a campaign.
| Audience | What they see | What stays hidden |
|---|---|---|
| Trusted collaborators (co-GMs, co-writers) | Your world as you build it, so they can add and edit alongside you | Nothing from them by default — they are inside the world |
| Players | Only the pages and connections you choose to reveal | Hidden pages, secret notes, and spoiler-free connections you haven't published |
The site frames the collaborator case as "share your world with trusted collaborators without accidentally spoiling it for your players," and the player case as "share what players should know while keeping your secrets hidden." So the same world can serve both groups at once, as long as you keep the visibility settings straight.
How the secrecy actually works
Scabard treats a campaign as a connected web of characters, places, factions, events, secrets, maps, and history rather than a stack of separate pages. That structure is what makes selective sharing possible:
- Hidden pages stay invisible to anyone you haven't granted access to.
- Secret notes attach to entities without appearing in the shared view.
- Spoiler-free connections let you link two things together in your own view without revealing the relationship to players.
- Reveal timing is yours — the site describes keeping a page hidden "until the time is right," so you can open things up mid-campaign as events unfold.
Because relationships stay visible to you (characters belong to factions, places contain other places, events shape history), you don't lose track of what's connected just because part of it is hidden from players.
Why share with players at all
The stated goal is engagement: "Wish your players cared more about your world?" Scabard's answer is to bring the campaign to life through interconnected people, places, history, and lore, then let players see the parts that are theirs to know. A player-facing view gives them something to read between sessions and a reason to ask questions about your world — without you having to hand over your notes.
Practical setup
- Build your world first, marking anything sensitive as hidden or secret as you go.
- Decide who each person is: a collaborator who edits, or a player who only reads what you reveal.
- Share the appropriate view, then check it as that person would see it before sending the link.
- Reveal hidden pages and connections over time as the story reaches them.
The main risk is the obvious one: if you mark something as visible by mistake, it's visible. Reviewing the shared view before you send it is the simplest safeguard.
What to check before committing
Scabard offers a free sign-up and a separate pricing page, so you can test the sharing and visibility controls before paying for anything. The site also lists PayPal among its payment options. Feature availability and any limits tied to a paid tier aren't spelled out in the material here, so confirm the specifics on the pricing page if sharing at scale matters to you.