Missions

Missions bring characters together around something they want to accomplish. An investigation, rescue, negotiation, repair, expedition, or personal obligation can provide the starting point. The objective gives the story direction while leaving participants free to decide how their characters respond.

A mission can concern a few people or contribute to a larger campaign. Combat, formal orders, and galactic importance are unnecessary: a local problem can have lasting consequences for the characters involved.

Mission Status

• Planned — The premise is established, but meaningful mission roleplay has not begun.

• Active — The mission is advancing through roleplay.

• Paused — Play began and remains unresolved, but is temporarily inactive.

• Concluded — The mission’s active roleplay has ended, regardless of its result.

Concluded records appear in Completed Missions. The directory name describes the end of play; it does not establish that the characters achieved their objective.

Cancelled proposals are handled separately. Cancellation does not mean an attempted mission failed, and it does not erase preparations or decisions already established in continuity. Once meaningful mission events have occurred, preserve them under the appropriate mission status.

Participation

• Open — Additional characters are welcome through believable connections.

• Limited — Involvement depends on circumstances such as access, timing, relationships, responsibilities, or available space.

• Closed — Additional participants are not currently being accepted.

Begin with the individual record’s objective, circumstances, participation information, and Ways Into the Mission section where provided. Look for a connection grounded in your character’s work, relationships, location, obligations, expertise, or experience of earlier events.

A character might possess relevant evidence, need assistance, maintain equipment, represent an affected party, or encounter consequences independently. Involvement need not mean joining the central team or sharing its priorities.

For Limited participation, establish how the proposed connection fits the mission’s access and coordination conditions. If an opening is unclear, coordinate with the relevant players before treating involvement as established.

Read Information Access for the distinction between what readers know and what characters can learn. A character who obtains one report may still lack the wider investigation, and an authentic document may contain mistaken or deliberately false information.

Start with circumstances that allow a meaningful first action. Explain what characters have reason to pursue, what makes it difficult, and what is already established. Leave their decisions and unplayed discoveries open.

Use Current Setting when the premise depends on StarForgeRP’s shared present. That page contains major SWTOR story spoilers. Historical missions should establish the circumstances of their own period.

What the Record Should Establish

• Opening summary — Introduce the mission, its central problem, and the circumstances needed to understand it.

• Mission at a Glance — Summarize status, participation, mission type, timeframe, setting, and objective. Add principal participants, sponsorship, authority, information access, connected stories, or outcome when useful.

• Mission Objective — Explain what characters seek or sought to accomplish without guaranteeing a result.

• Context and principal parties — Establish relevant background, responsibilities, interests, and limits on authority.

• Mission-specific material — Explain the evidence, hazards, resources, locations, technical concerns, or competing claims that matter.

• Information Access — Distinguish public circumstances from restricted details, disputed accounts, and knowledge available only through particular sources.

• Participation and unresolved questions — Identify believable openings when participation permits and uncertainties that remain available to play.

• Developments and consequences — Preserve what has happened and what it changes.

• Related Records — Connect the people, places, organizations, and stories needed to understand or continue from the mission.

Use the depth the mission requires. A straightforward assignment may need a short account; a complicated investigation may require separate explanations of evidence, custody, and authority. A suitable principal image can follow the introduction, with a Table of Contents for records that benefit from section navigation.

RP Hooks offer circumstances characters can respond to. A hook may develop into a mission when participants pursue a focused objective, or it may lead to a conversation, relationship, or another kind of story.

Campaigns & Story Arcs connect developments across a broader narrative. An individual mission can contribute to that narrative while keeping its own objective, circumstances, and consequences clear.

RP Events bring characters together around an occasion or shared situation. Participants may have different purposes; something that happens during the event can give rise to a related mission.

Preserve the developments another player would need to understand the mission and its continuing significance. Record consequential choices, discoveries, losses, changed objectives, and unresolved responsibilities without recounting every exchange.

Distinguish established events from allegations, testimony, interpretation, and proposed developments. Preserve the boundaries around concealed identities, restricted information, and discoveries reserved for future play.

As the Mission Develops

• Planned — Describe the starting situation, objective, available connections, genuine uncertainties, and stakes. Leave future participation and outcomes unestablished.

• Active — Separate the original premise from subsequent discoveries and decisions. Explain the current situation when developments have changed what participants face.

• Paused — Preserve a State at Pause: where play stopped, what had changed, and what remained unresolved. Resume the same record unless the later story is genuinely a separate mission.

• Concluded — Explain what actually happened, the result of the objective, and lasting consequences. Continuing leads can support later stories without automatically reopening the original mission.

• Cancelled — Separate Established Circumstances from Proposed Mission Material. Unplayed encounters, intended participants, and planned discoveries remain proposals.

Following the Consequences

Keep the mission’s detailed account with its record. Link affected character, location, and organization pages so readers can follow lasting changes to those subjects.

The  Story Archive connects concluded roleplay with continuing significance. Current Storylines follows narratives still developing across StarForgeRP. These destinations may reveal outcomes or information unavailable to characters.

Use the Timeline when a development’s date or sequence matters to wider history. Preserve meaningful dates and leave uncertain chronology approximate; a mission does not require a separate historical entry simply because it ended.