Game Sessions

RUNNING SESSIONS

All Nocturne Symphony members can host their own RP sessions, also known as games. Casual, non-plot-related RP is free to run - think "characters hosting a party", for example.

This page is for plot-related or otherwise significant RP sessions, often referred to as "canon games" (though, of course, casual RP is still canon, too). These games require an official Storyteller. The most common game type are missions, generally involving multiple players and taking 2-4 days to complete some kind of storyline or goal. Smaller games are often called minigames and are typically done at whatever pace the Storyteller finds comfortable. These are generally downtime or "between" activities (e.g. gadget Installations, lore investigations, follow ups after a larger mission, etc), and can have as few as a single player.

All public RP in the main server must abide by group rules and should have content warnings when applicable.

SESSION RULES

• Only official Storytellers can host canon games.

• Canon missions must be approved by the mods.

  • • Minigames may or may not require explicit approval. For example, minigames that lead into missions are likely to require approval, while minigames that are tying up loose threads after a mission may not need approval.

    • As a rule of thumb, new content should get approved by mods before being introduced to players. This is to make sure NPCs and storylines make sense within Nocturne Symphony's lore.

• Only approved missions can be added to the group calendar.

  • • If timing is important to your mission, you can request a reservation ahead of time. You must send in a mission for approval within a week of making your reservation.

    • For both canon and non-canon games, please only claim a calendar slot if you are committed to it. Flaking on time slots inconveniences both players and other Storytellers.

• Storytellers are in charge of their own signups, posted to the #bulletin channel in Discord.

  • • Storytellers are allowed to use any system for determining signups. Some examples include:

      • • First come, first serve. Players are chosen based on signup order.

        • Priority. Players are chosen with some form of priority system, such as "did not play in the Storyteller's last game" or "character lives in the region".

        • In-character. Players are chosen through an in-character discussion where characters may volunteer for a task.

        • Handpicked. Players are chosen directly by the Storyteller. Generally applies to minigames more than missions.

• Canon games must be hosted in the main server. If it involves a Storyteller, the RP must be done in a public RP or mission channel. This is to ensure transparency for changes in equipment, Conditions, and other plot-relevant events.

  • • Mochi will create channels on request. Otherwise, the default RP channels are available for use.

• Canon missions can have art prompts, for completion by characters who did not play in the game. Submit up to 3 prompts to Mochi, who will assign Beat rewards.

• Storytellers are strongly encouraged to provide their table rules upfront, prior to signups. Basic standards of courtesy, respect, and communication are expected across all games, as well as adherence to group-wide rules.

SESSION BEATS

Players can earn rewards (i.e. Beats) through participating in canon games.

MISSIONS

• Storytellers hosting a canon mission will earn half the Beats of the highest earning Player.

• All participants, including the Storyteller, earn 100 AP.

• Players earn Beats through participation, utilizing mechanics, and roleplay. Storytellers can learn more on how to best award non-mechanical Beats on the Storytellers page.

MINIGAMES

• Not all minigames should reward Beats. The Storyteller should only award Beats if the game itself is intended to have both inherent risk and narrative significance. The Storyteller should exercise reasonable judgment and should explain why when submitting Beats to Mochi.

  • • This is very context dependent. For example, while Compromise is always technically a risk, rolling an Exceptional Success while checking for Compromise may not always earn Beats in a minigame. For a minigame where the character is simply talking to an ally NPC in a safe area, they are unlikely to earn Beats for risking Compromise. In a minigame where the character is tracking down a foe in enemy territory, they should earn Beats for Exceptionally Succeeding on Compromise.

    • The only exception to this are Beats from Conditions (Persistent or Condition resolution). These Beats are always awarded.

• Minigames reward purely mechanical Beats, i.e. through Conditions, Dramatic Failures, and any mechanics that explicitly reward a Beat for a trigger.

RECORD KEEPING

Storytellers are responsible for submitting logs of character changes after a canon game, both missions and minigames. This information must be submitted to Mochi. If the game was a mission, please see the backend report requirements on the Storyteller page.

• Aether: The net Aether change, such as +3 or -5

• Integrity: The net Integrity change, such as +1 or -1

• Willpower Dots: Whether Willpower Dots have been burned, such as for anchoring a gadget, gaining Integrity, or burning WP past their maximum. Please also include the canon date of the WP change, as WP dots have a 1 month cooldown to regain.

• Deaths: Whether or not the character has died

• Equipment: This information does not need to be submitted to Mochi, but the player (or Storyteller, with the player's permission) must add/remove equipment to their character inventory.