Visibility levels

Every entity in Skryrún has a visibility level. This is the primary mechanism for controlling what players see, managing secrets, and revealing information deliberately during play.

The three levels

New entities default to GM Only. There is no way for a player to see a GM Only entity — it does not appear in portal search results, the player graph, or any portal navigation. Wikilinks from Party-visible articles that point to GM Only entities render as plain unstyled text for players; they will not know an entity exists at that name.

GM Only

The default state for all new entities. Use GM Only for:

• Prep notes, tactics, and behind-the-scenes lore
• Secrets and reveals not yet discovered
• Entities you are still drafting or haven't decided to expose

When you flip a GM Only entity to Party, the change is immediate — players on the portal see the entity appear without refreshing.

Party

Party visibility makes an entity visible to all authenticated players in the campaign. It appears in the player portal, shows up in player search results, and wikilinks pointing to it become clickable for players.

Use Party for:

• Locations the players have visited
• NPCs they have met
• Lore and history they have learned
• Clues they have found and collected

Character-Tagged

Character-Tagged lets you target visibility to specific players based on their character's traits. Tags are defined on character profiles and can include:

Tags are entered when players fill in their character profiles. You apply a tag rule to the entity from the visibility panel.

OR logic (default)

Any player whose character matches at least one of the specified tags can see the entity.

Example: race:elf OR class:ranger — visible to elves and rangers, separately.

AND logic

👑 Runekeeper only. Every tag in the rule must match for a player to see the entity.

Example: class:cleric AND deity:Morreth — visible only to clerics of Morreth specifically.

Practical uses for Character-Tagged

• Race-specific lore — ancient elven histories visible only to elf characters
• Class-specific knowledge — arcane libraries visible only to wizards
• Cult secrets — a deity's inner doctrine visible only to characters who follow that deity
• Level-gated content — high-stakes revelations visible only when characters reach a certain level
• Background hooks — information that only a character with a specific background would recognize

Parent inheritance

Visibility is not automatically inherited from parent entities. If a location is set to Party, entities nested inside it — rooms, NPCs placed there, items found there — remain at their own individual visibility settings. You must update child entities separately.

If you want children to mirror the parent, enable Inherit from parent in the entity's visibility settings. When active, the child entity always shows whatever the parent's current visibility level is — changing the parent updates the child automatically.

Practical examples

Setting a location to Party so players can read its article Open the location entity, click the visibility badge next to the entity name, and select Party. Players see the location in their portal immediately.

Keeping an NPC's Secrets block GM Only while the NPC itself is Party Set the NPC to Party visibility. Open the Secrets block within that NPC and set it to GM Only. Players see the NPC's article, personality, and equipment — but not the secrets section.

Setting deity lore to Character-Tagged for clerics only Open the deity entity and set visibility to Character-Tagged. Add the tag rule class:cleric AND deity:[DeityName]. Only players with a cleric character who worships that deity will see the article in their portal.

Full comparison table

See also

• Key concepts — overview of visibility in the broader mental model
• Entity types — what entity types are available
• Pricing and tiers — what each tier includes