RP Events

Gatherings, occasions, and shared situations that bring characters together at a particular place and time.

RP Events are shared situations that give characters a believable reason to be present together.

An event might be a diplomatic reception, military assembly, public celebration, private gathering, competition, ceremony, criminal meeting, political function, community activity, emergency, memorial, festival, professional conference, or almost any other occasion capable of bringing characters into the same situation.

Unlike a Mission, an Event does not necessarily give everyone present the same objective. Characters may attend for completely different reasons, arrive with competing interests, know only some of the other participants, or discover that the situation becomes more complicated than expected.

The event establishes the circumstances. What develops from them belongs to the players.

Conversations may become relationships. Disagreements may become rivalries. A celebration may reveal a problem. A routine meeting may create an unexpected alliance. Something intended as a single gathering may become the beginning of an investigation, mission, campaign, or entirely separate story.

Events may stand alone or connect to larger StarForgeRP storylines.

[Briefly explain what is happening, why characters are gathering, what kind of atmosphere or situation they should expect, and any information a prospective participant needs before becoming involved.]

A good reason for attending is more useful than a complicated one.

Before joining an event, consider how your character would realistically learn about it and why they would be there. A public festival may require almost no explanation. A military briefing, private diplomatic reception, criminal gathering, or restricted ceremony may require a professional, personal, organizational, or story connection.

An Event marked Open is available to characters who have a reasonable way to participate.

An Event marked Coordinated may accept additional participants, but players should speak with the organizer first so that introductions, access, timing, or other circumstances can be established appropriately.

An Event marked Closed has a fixed group of participants or is not currently accepting additional characters. Completed events may also appear as Closed once they are retained primarily as archive records.

These labels describe access to the roleplay, not the importance of a character within it. Joining an event should never imply control over its outcome or over the actions of other participants.

When in doubt, begin with the character's existing connections.

Who invited them? Who do they work for? Who might they know there? What service could they provide? What responsibility brings them into the situation? What do they want from attending—and what might make them regret doing so?

A simple, believable connection is enough.

Completed events remain useful after the roleplay itself ends.

Past Event records preserve who was involved, where the gathering took place, what developed through play, and which consequences remain relevant to the shared continuity. They can provide context for relationships, political developments, organizational changes, damaged reputations, new alliances, unresolved disputes, future investigations, and later stories involving the same people or locations.

An Event does not need a dramatic outcome to deserve a record. A conversation that changes a relationship, a ceremony that establishes an obligation, a meeting that introduces two future rivals, or a social gathering that exposes an unresolved problem may matter long after the scene itself is over.

Completed Events can remain discoverable through RP Events while also appearing in the wider Story Archive.

Events are especially useful places for new Roleplay Hooks to emerge.

A character might leave an Event with a new contact, professional opportunity, suspicion, debt, rival, obligation, secret, invitation, enemy, or unanswered question. These developments can become separate Hooks when they offer meaningful opportunities for later interaction.

Not every conversation needs to become a documented Hook. Record the ones that are likely to matter beyond the original scene or give players a useful reason to continue the story.

An Event page should make it possible to understand both the opportunity for roleplay and the continuity created afterward without requiring someone to reconstruct the entire scene from chat logs.

Where applicable, individual Event records should identify:

• Status — Planned, Scheduled, Active, Completed, Postponed, or Cancelled.

• Participation — Open, Coordinated, or Closed.

• In-Universe Date — When the Event occurs within StarForgeRP continuity.

• Play Date — The real-world session date when preserving it is useful for organization or archive purposes.

• Location — The planet, settlement, facility, vessel, stronghold, or other place where the Event occurs.

• Organizer or Host — The character, organization, player, or other party responsible for coordinating the Event where relevant.

• Related Story — Any Campaign, Story Arc, Mission, or Current Storyline directly connected to the Event.

• Premise — What is happening and why characters are gathering.

• Participation Information — What kinds of characters can reasonably attend and whether prior coordination is required.

• Involved Characters — Characters who became part of the Event.

• Involved Organizations — Factions, organizations, businesses, governments, or other groups that materially participated.

• Outcome & Consequences — What changed through play and what remains relevant afterward.

• Related Roleplay — Missions, Hooks, Events, or later stories created or affected by what happened.

Not every Event requires every field. A small social gathering should not be documented like a military operation simply because the template allows it.

Record what future players need in order to understand the event and its consequences.

An Event matters when something from it continues to matter.

Characters may form or damage relationships. Organizations may make agreements, lose influence, or become involved in new disputes. A location may acquire a new reputation. Information may become known. Promises may be made. Crimes may be witnessed. Political positions may shift. A seemingly minor interaction may create the circumstances for an entirely different story.

When those consequences affect other parts of StarForgeRP, update the relevant records.

A character's dossier can reflect a major personal development. An organization page can record a change in leadership or policy. A Galaxy entry can note an important incident connected to a location. A new Roleplay Hook can preserve an unresolved opportunity. Significant developments can be added to the Timeline when their date matters to later continuity.

The Event page records what happened together.

The rest of StarForgeRP records what it changed.

An Event should provide circumstances for characters to respond to rather than a script that requires a particular result.

Hosts may establish the location, occasion, known participants, immediate circumstances, and information available at the beginning of the roleplay. Players remain responsible for their own characters and should have room to make decisions, misunderstand one another, change plans, succeed, fail, withdraw, escalate a problem, or create consequences nobody anticipated.

Large galactic consequences are not required.

A successful Event may be remembered because a treaty was negotiated, but it may also matter because two characters met for the first time, a friendship ended, an employee made a mistake, someone overheard the wrong conversation, or an apparently insignificant promise became important months later.

Persistent roleplay grows from those connections.

Events are only one way to discover stories within StarForgeRP.

Explore Current Storylines for a broader view of what is happening now, browse Roleplay Hooks for situations seeking character involvement, or look through Campaigns and Missions for stories organized around longer narratives or focused objectives.

Completed Events remain part of the archive so that future stories can build upon what happened before.