Guidebook

Category: Gameplay & Systems

Quests & Events


On This Page

Basics

What Quests Are

Quests are goal-oriented roleplay threads that give characters a specific objective, challenge, or conflict to overcome. They can range from small-scale adventures like finding a missing animal, investigating a dangerous area, or repairing a damaged structure to combat encounters, personal trials, faction objectives, and major confrontations that directly affect the wider story of Embrathis.

Unlike an ordinary roleplay thread, a Quest has a defined goal and some form of resolution. Characters may need to investigate, negotiate, solve problems, survive hazards, fight enemies, complete assigned tasks, or respond to changing circumstances as the Quest unfolds. Depending on the Quest type, outcomes may be determined through player narration, puzzles and challenges, dice rolls against character stats, staff decisions, or a combination of these methods.

Quests may be player-led or staff-led and vary widely in scale, danger, mechanics, and importance. Some are designed primarily for character development and smaller adventures, while others can involve serious combat, lasting consequences, major rewards, or changes to the overarching site plot. Each Quest type has its own requirements and expectations, explained below.

Quest Expectations

For any turn-based or timed Quest, players are expected to consider their real-life availability before joining. These threads often move on a 24 to 48 hour posting schedule, depending on the number of participants and the Quest itself, so please only join if you reasonably expect to keep up with the required pace.

During timed Quest rounds, replies should remain short, clear, and primarily action-focused. Keep extended internal monologue, lengthy reflection, and other nonessential material to a minimum until your character has exited the Quest or the final round has concluded. This helps staff resolve actions quickly and keeps the thread moving for everyone involved.

If a player does not post within the stated time limit for their turn, their turn may be skipped so the Quest can continue. Being skipped does not protect the character from what is happening around them, and missed actions may result in injury, failed objectives, lost opportunities, or other negative consequences depending on the situation.

At the bottom of every Quest post, include a brief TL;DR action summary listing what your character attempted during that turn, along with any weapons, armor, magic items, consumables, companions, or other mechanically relevant items used.

Players are also responsible for tracking and following all cooldowns, usage limits, and other restrictions attached to their magic, abilities, and items. A new Quest round does not automatically reset an ability or item unless its mechanics specifically say that it does.

Rewards & Consequences

Quests can reward characters in a wide variety of ways depending on their type, difficulty, and role in the larger story. Completing Quests rewards Chips, and some Quests may also grant additional IC rewards such as magic, magic items, companions, positions of power or influence, rare knowledge, resources, reputation, or other unique opportunities. Participation in larger Quests may also place a character directly in the path of ongoing site plots, giving them opportunities to influence how those stories develop.

Quests can carry serious consequences as well as rewards. Some higher-risk Quests operate under blanket consent, meaning that by choosing to participate, players accept the stated level of risk associated with that Quest. Depending on the Quest, consequences may include character death, lingering or permanent injuries, loss or destruction of items, failed objectives, changes in status or reputation, or other lasting IC effects.

Some Quests may also have consequences if players take too long to complete objectives or fail to act within a stated window. These consequences depend on the individual Quest and the situation unfolding around the characters. The world does not necessarily remain frozen while a Quest is unfinished.

Failed Core Quests always have in-character consequences. Because Core Quests directly affect major conflicts and the wider state of Embrathis, failure may change circumstances beyond the participating characters themselves. Locations, factions, resources, relationships, future opportunities, or the direction of the site plot may all be affected by the outcome.

Quest Types

Quest Type Key

MQMiniquest

Key Features

  • Clear Goals: e.g., secure a mine, repair a shelter, map risky tunnels, rebuild a home, find a lost pet.
  • Fair Resolution: dice/stats, puzzles, riddles, or factual Q&A (right/wrong), or narrative judgement calls.
  • Unlimited Participation: no cap on how many MQs you host or join.

Hosting Guidance

  • Direct Play: present IC obstacles and react to player choices.
  • Tailor Prompts: give each participant a unique challenge aligned to their role.
  • Consent Envelope: minor injuries/setbacks are implied by joining; lasting harm requires explicit consent.
Example
Old iron mines in the Marrows were abandoned after a cave-in. The Doe family returns to stabilize the tunnels and recover what they can.

- John Doe (Host): Oversees the main chamber and assigns tasks, and takes whatever tasks remain.
- Jane Doe: Reinforce compromised beams in the primary shaft.
- David Doe: Explore deeper tunnels for salvage (tools, medical kits).
- Mary Doe: Chart side passages and note hazards for future crews.

Complications for the Host to deploy: hairline cracks spreading under weight; buried crates beneath unstable scree; a forked route with “safe but slow” vs “fast but narrow.”

MQ+Main Quest

Features & Mechanics

  • High Stakes: success/failure can shift resources, borders, or faction influence.
  • Structure: Uses dice rolls against stats.
  • Consequences: abandoning or failing a MQ+ can create IC fallout.
  • Rewards: regional influence, access, reputation, assets (varies by quest).
Examples
- Fortify a border hamlet before monsters test the defenses.
- Broker terms between rival work crews competing for the same seam.
- Reopen a strategic pass clogged by a controlled rockfall.

LQLoom Quest

Features & Mechanics

  • Unique Rewards: Loom-blessed abilities, items, or knowledge.
  • Transformative Risk: failure may cause loss, corruption, or lasting alteration.
  • Tailored Trials: challenges reflect the seeker’s nature, flaws, and prior choices.
Example Outcomes
- A magic item.
- A new skill.
- Secret plot information.

CQCharacter Quest

Features & Mechanics

  • Triggers: By request. In #tag-staff on Discord, @staff that you're requesting a CQ, which character it's for, and what their goal is. Staff will respond with your quest.
  • Progression: can evolve into an LQ if conditions align.
  • Rewards: magic items, a change in station, a new companion, etc.
Examples of IC Quest Tasks
- A foreman entrusts David Doe to recover a lost ledger from a condemned shaft and reopen a mine.
- A councilor tasks Jane Doe with negotiating a truce between rival work crews.
- The Loom responds to Mary Doe’s vigil with a trial only she can complete.

CQ+Core Quest

Core Mechanics

  • Turn-Based Play: strict initiative order unless stated otherwise; no out-of-turn posting.
  • Round Timing: approx. 6 seconds IC per round.
  • Action Economy (TL;DR): generally one major action (attack/throw/etc.) plus movement. Faster extras may be allowed at admin discretion. Include a brief action summary at the end of each post, along with all weapons, armor, magic items, and companions brought into the quest.
  • Fleeing: allowed to attempt; not guaranteed to succeed.

Consequences & Expectations

  • Failure: can cause character death, regional losses, or plot delays.
  • Post Style: keep action-forward; minimize inner monologue.
  • Word Count: under 400 words target for pace.
  • No Post Edits: you may edit only before the person after you replies; once they reply, no more edits.
  • OOC Pace: 3 or fewer chars → 24h per round; 4–5 chars → 48h per round.
Example Expectations
“Jane Doe darts to the fallen beam, wedges a piton, and yanks the rope to lever it clear (Action: Brace structure). She retreats 10 ft toward cover.”

Posting Rules

Initiative & Rounds

Turn-based Quests use an established initiative order to determine when each character may act. Once initiative has been set, players should post only when it is their character’s turn unless staff specifically states otherwise. Do not post out of turn.

A full round is completed once every character in the initiative order has either taken their turn or been skipped due to the Quest’s posting deadline. The next round then begins from the top of the initiative order.

Unless a Quest states otherwise, each round represents approximately six seconds in-character. Actions taken during a turn should reasonably fit within that amount of time. Characters cannot perform a long sequence of separate actions simply because they can all be described within one post.

Timed Quests will state how long players have to complete each turn, typically 24 to 48 hours depending on the number of participants and the needs of the Quest. If a player misses their posting window, initiative continues without them and any consequences caused by their missed action may still occur.

Player Vs Player (PvP)

PvP applies when two or more player characters are genuinely competing against one another and the outcome has not already been decided OOC. This can include direct combat, skirmishes, faction-versus-faction conflicts, attempts to stop another character from accomplishing a goal, theft, or other situations where one character’s success directly depends on overcoming another.

If everyone involved has already agreed OOC on who succeeds and what happens, the scene may be written narratively and does not require PvP rolls. This includes pre-plotted fights, thefts, or other conflicts where the outcome is already established between players.

If the outcome is genuinely undecided, clearly state at the bottom of the initiating post that PvP has been initiated and tag staff. Staff will handle the necessary rolls to determine success, failure, and any contested actions between characters.

If a character initiates combat against another player character, clearly state at the bottom of the post that PvP has been initiated, a TLDR of your actions, and tag staff. Once PvP begins, staff will handle any required dice rolls and resolutions between the characters.

Action Summaries

At the bottom of every Quest post or PvP, include a clear and concise action summary for staff to reference when resolving rolls and determining the outcome of the round.

The summary must plainly state what action your character took during the post. Avoid vague wording or relying on staff to infer the action from the prose above. If your character attacked, defended, healed, moved an object, attempted to flee, used magic, searched a body, or performed any other mechanically relevant action, state it directly.

Players must also list all magic items their character currently has with them from their inventory, even if those items were not used during that particular turn. If a magic item is used, clearly state which item was activated and what it was used to accomplish.

This summary allows staff to quickly review each character’s actions, available items, and relevant mechanics while calculating dice rolls and resolving the round.

Editing Posts

Quest posts may be edited only until the next player in initiative has posted. Once the following post has been made, the previous post is considered locked and may no longer be changed.

This rule exists to keep Quest play fair and ensure that actions are not altered after another player or staff member has already responded to them.

Fleeing Or Withdrawing

Characters may attempt to flee or withdraw from a Quest at any time, but escape is not automatically guaranteed. Staff will roll to determine whether the character successfully gets away based on the circumstances of the Quest.

If all participating characters flee or withdraw, the Quest is considered failed, and any appropriate consequences for that failure will still apply.

During PvP, a player may choose to yield before their character reaches death. Yielding always allows that character to escape the conflict with their life, though other consequences of the encounter may still apply.

When a character loses all of their health, they become unconscious. Any additional damage dealt to that character after they have reached zero health results in death. Because of this, a character must yield before reaching that point if the player wants to guarantee their survival.

Miniquest Example

How Miniquests Flow

Miniquests are player-led Quest threads built around a clear goal, challenge, or problem for the participating characters to solve. One player acts as the host, setting up the scenario, presenting obstacles or complications, and guiding the Quest forward as the other characters respond.

A Miniquest should begin with a clear objective and enough information for participants to understand what they are trying to accomplish. From there, the host introduces challenges as the thread progresses, gives individual characters opportunities to contribute, and reacts to the choices players make rather than deciding the entire outcome in advance.

Miniquests must include at least two additional participating characters besides the host and run for a minimum of four rounds. Dice, stats, puzzles, riddles, or other resolution methods may be used at the host’s discretion, as long as expectations are established clearly for everyone involved.

Minor setbacks and injuries may occur as part of participating in a Miniquest, but lasting harm, permanent injury, or death always requires explicit player consent.

Miniquest Walkthrough

host

Host Opening Post

IC

Rainwater pours through the lower streets of the district, spilling from drains already struggling to keep pace with the storm. Beneath them, part of an older waterway has collapsed, sending water through maintenance passages and dangerously close to the foundations of several nearby homes.

City workers have blocked the entrance with lanterns and rope, but the damage below needs to be assessed before anyone can begin proper repairs.

The passage is already ankle-deep in cold water. Farther inside, the sound of rushing water echoes through the stone.

Three problems are immediately apparent: a damaged water gate needs to be closed before the flooding worsens, one of the main support beams has cracked beneath the pressure, and a maintenance worker who entered the tunnels before the collapse has not returned.

player

Player Arrival Post

IC

Jane Doe ducks beneath the rope and descends into the flooded passage, boots disappearing beneath the murky water.
Her attention catches immediately on the cracked support.

“I’ll take that.”

She crosses to the beam, pulls a support post from the nearby repair supplies, and begins positioning it beneath the weakest point of the structure before reaching for the tools at her belt.

player

Player Arrival Post

IC

David Doe wades deeper into the tunnel until the damaged water gate comes into view through the spray.

“I’ve got the gate.”

He reaches the mechanism, plants his feet against the current, and grips the warped wheel with both hands. After testing it once, he puts his weight into trying to force the gate closed.

Player Arrival Post

IC

Mary Doe reaches the flooded fork and spots the maintenance passage disappearing into darkness.

“Missing worker went this way?”

She raises her lantern and starts down the passage at once, checking the walls, water, and debris for any sign of where the worker may have gone.

host

Host Task Post

IC

Before John can even make a move to check on progress, the tunnel answers all three of them at once.

The cracked support gives a sharp groan above Jane. The break is worse than it first appeared. Reinforcing the beam where it stands may not be enough. She will need to brace it from below before securing the damaged section.

At the gate, David manages to shift the wheel only a fraction before the mechanism jams completely. Debris has wedged itself into the lower gears beneath the rushing water. The obstruction will have to be cleared before the gate can close.

Mary finds what she is looking for farther down the maintenance passage: a dropped lantern caught against the wall and a streak of blood disappearing around the next bend.
Then the water rises another inch.

player

Player Response Post

IC

Jane looks up when the timber groans. “Right. Of course you’re worse than you looked.”

She abandons the damaged section itself and moves beneath the beam instead, dragging one of the loose support posts into position.

Jane wedges the post beneath the sagging timber, checks the angle once, then drives it firmly into place before putting her weight against it to test whether the brace will hold.
Only then does she reach for the tools needed to begin reinforcing the original break.

Events

What Are Events?

Events are open roleplay opportunities built around a shared occasion, activity, celebration, or site storyline. Unlike Quests, Events do not revolve around completing a single objective or following a strict turn order. They are designed to give characters room to mingle, participate in activities, play games, interact with the setting, and take part in whatever is happening around them.

Site-Wide Events and Mini Events function as open gathering threads. Depending on the event, they may be available to the entire site or restricted to a particular group, class, faction, or selection of characters. There is no posting order, and players may participate with as many eligible characters as they would like.

Each character who makes at least three posts in a Site-Wide Event or Mini Event earns Chips for participating.

Event Threads are ordinary roleplay threads connected to an Event. They often take place before or during a Site-Wide Event and may explore preparations, side stories, individual activities, or specific moments happening alongside the larger gathering. Participating in Event Threads may also earn Chips and may sometimes fulfill requirements for additional rewards offered during the associated Site-Wide Event.

Mini Events are smaller, lower-stakes gatherings intended primarily for fun, character interaction, and earning Chips, without necessarily being tied to a major site storyline.

Event Types

Site-Wide Events

Site-Wide Events are large-scale events open to all characters on the site. Participation is always optional, but these events offer higher Chip rewards, opportunities for plot progression, and sometimes additional surprise gifts or rewards tied to completing relevant Event Threads.

Site-Wide Events usually follow a central theme and may include games, challenges, performances, competitions, celebrations, or other activities. Some are casual gatherings, while others connect directly to ongoing site plots or major changes within Embrathis.

There is no posting order, and players may participate with as many characters as they would like. Each character must make at least three posts in the Site-Wide Event for their participation to count toward Chip rewards.

Some Site-Wide Events may also offer additional rewards for characters who complete related Event Threads before or during the event. Any special requirements will be explained when the event is announced. Site-Wide Events are always announced ahead of time.

While many Site-Wide Events begin as social or celebratory gatherings, they always have the potential to escalate. Unexpected plot developments, hazards, conflicts, or other surprises may occur as the event unfolds.

Event Threads

Event Threads are writing prompts for threads connected to an upcoming Site-Wide Event. They give characters opportunities to interact with the event’s theme, story, or preparations before the main gathering begins.

Typically, each Site-Wide Event will include two to three Event Thread prompts that players may complete before the event opens. Completing these prompts earns Chips and will often contribute toward additional gifts, bonuses, or other rewards available during the associated Site-Wide Event.

Event Threads are optional, but participating in them can give characters additional involvement in the event and unlock rewards beyond those earned through the Site-Wide Event itself.

Mini Events

Mini Events are player-hosted gatherings that may be created at any time without staff permission or a formal site announcement. Announcements are optional, and the host decides how long the event will remain open.

Mini Events are intended to give players a flexible space for characters to mingle, build plots, create drama, play games, celebrate, argue, flirt, scheme, or otherwise interact around a shared occasion or theme. If desired, a host can offer a prize, but it must be something from their own inventory.

A Mini Event may be limited to certain classes, factions, magic types, professions, social groups, or other IC categories when it makes sense for the event. However, hosts are expected to make a reasonable effort to keep Mini Events inclusive on an OOC level and avoid repeatedly excluding the same players from participation.

There is no posting order. Each participating character must make at least three posts in the Mini Event for their participation to count toward Chip rewards.

Mini Events may escalate naturally because of character choices and interactions. Staff will not intervene in or direct the event unless PvP is initiated or another situation arises that requires staff resolution.

Extra Notes