RP Events

RP Events give characters a shared occasion to attend: a celebration, assembly, competition, private gathering, or situation demanding an immediate response. Those present can have different responsibilities, loyalties, and reasons for being there.

Start with the premise, place, timeframe, and participation information. Establish why your character would attend and how they would learn of the occasion. A professional duty, personal connection, invitation, or nearby responsibility may provide enough of an introduction.

• Open — Further characters may join through a plausible connection.

• Coordinated — Contact the organizer or relevant participants to work out whether and how a character could enter.

• Closed — The Event is not accepting additional characters.

These descriptions help players arrange participation. They do not give characters permission to enter a restricted location or knowledge of private matters. If the route into an Event is unclear, coordinate it before treating the character’s presence as established.

Characters can contribute as employees, visitors, representatives, neighbors, or others with a reason to be present. Their involvement can matter without making them the focus of the occasion.

An Event can contain several threads. At a ceremony, an attendant might manage practical arrangements while guests pursue introductions, settle an argument, or avoid an unwelcome conversation.

Missions provide a home for focused objectives. If an incident during the ceremony leads characters to search for missing equipment, that search could become a related Mission without replacing the wider Event.

RP Hooks provide openings for interaction, while Campaigns & Story Arcs connect developments across a longer narrative. An Event can contribute to either or remain independent. These connections follow the story as it develops; they do not require a fixed progression.

A useful record supports both joining and later reference. Include the details needed to understand the occasion, then preserve what play actually establishes.

• Status and participation — Record progress and availability separately.

• Fictional timeframe — Place the occasion within shared history, using an approximate date when necessary.

• Session arrangements — Give the real-world date, time zone, and agreed play format where relevant.

• Place and premise — Explain where the gathering happens, what brings people together, and how characters could enter.

• Hosting and coordination — Distinguish the in-universe host from whoever coordinates play. Publish only contact information intended for that purpose.

• Significant connections — Identify relevant people, organizations, locations, and earlier stories.

• Developments and outcomes — Preserve consequential choices, discoveries, setbacks, and changes.

• Continuing threads — Connect later roleplay that responds to what happened.

Use the detail appropriate to the occasion. A brief meeting may need only a short account. Distinguish intended attendance from actual involvement, and leave unplayed possibilities unresolved.

Dates and Character Knowledge

Session dates and fictional dates serve different purposes. One gathering may span several sessions, and a newly played scene may belong earlier in the characters’ lives.

Use Current Setting when an Event depends on StarForgeRP’s adopted present and SWTOR story boundary. That page contains major story spoilers. For historical scenes, establish the relevant circumstances of that period.

Separate confirmed developments from allegations, mistaken accounts, and proposed outcomes. Preserve the difference between information available to readers and information a character could obtain. Private conversations and concealed identities retain their established boundaries; discoveries reserved for later play should remain undisclosed.

What Continues Afterward

Keep the account of the occasion and its immediate results with the Event. Related character, location, and organization pages explain lasting changes to their own subjects and can link readers back to that account.

The Story Archive connects concluded roleplay with continuing significance. The Event Directory provides historical context for selected developments whose causes and consequences warrant broader attention. These destinations may reveal story outcomes.