StarForgeRP brings players together through collaborative storytelling in a persistent Star Wars: The Old Republic (SWTOR) setting. Roleplay can take place in SWTOR, through Discord, or in another format agreed upon by the participants.
Each player controls their own character while contributing to stories that others help shape. Characters can disagree, make mistakes, pursue conflicting goals, succeed, fail, and change over time. Good collaborative roleplay leaves room for those choices and allows their consequences to matter.
These guidelines explain how to play together while respecting character agency, player boundaries, and established continuity. For definitions of common roleplay expressions, consult Terminology. If you are preparing your first scene, Getting Started covers the practical basics.
Describe what your character says, does, intends, and attempts. Other players determine their characters’ significant choices and responses, subject to any outcomes or resolution methods everyone has agreed upon.
For example, your character might try to disarm an opponent, restrain a prisoner, or persuade someone to surrender. The attempt creates a situation for the other character to respond to. Its success may depend on resistance, the circumstances of the scene, an agreed resolution method, or discussion between the players.
The same principle applies outside combat. An accusation does not establish guilt, a persuasive argument does not force agreement, and an attempted deception does not automatically determine what another character believes.
Players can agree on an outcome in advance, but otherwise should not narrate another character’s private thoughts, loyalties, injuries, surrender, or future decisions as established facts.
Respecting agency does not mean protecting characters from difficulty. They can face serious danger, suffer setbacks, and experience lasting changes while their players retain a meaningful part in deciding how events unfold.
Before a scene reaches a contested decision, agree on how uncertain outcomes will be handled. Participants may use dice, SWTOR game mechanics, established combat conventions, negotiated results, or another method they find suitable. No single system is required for every scene.
When a Game Master (GM) is involved, establish what they are responsible for. A GM may describe the environment, portray supporting characters, introduce challenges, and resolve uncertainty within the authority participants have agreed to give them. Running a scenario does not automatically grant control over another player's character.
Scenes can also proceed entirely through interaction between players, without a GM or formal rules. The important part is understanding how contested actions will be resolved before the result becomes a source of disagreement.
Keep gameplay results distinct from lasting narrative consequences. An in-game defeat does not, by itself, establish that a roleplay character has been permanently injured, captured, or killed. Those outcomes depend on the participants’ arrangements and the continuity established through play.
Most everyday interactions do not need extensive planning. Characters should be free to make decisions and respond naturally as scenes develop. However, discuss developments that would significantly affect another player's character, established contributions, or continuing story before treating them as settled.
Matters that warrant coordination include:
Death, permanent injury, prolonged captivity, or another lasting change to a character's circumstances.
Major relationship developments, betrayals, or disclosures involving another character.
New claims about another character's previous actions, experiences, promises, knowledge, or personal history.
Stories involving another participant's family connections, private background, secrets, possessions, or controlled resources.
Exceptional access to restricted locations, organizations, operations, or information.
The destruction or substantial alteration of an established location, organization, or shared resource.
Significant consequences involving characters whose players are absent or have not agreed to the development.
Coordination does not require deciding every result in advance. Players might agree that a confrontation could end in capture, injury, or escape while leaving the actual outcome to the scene.
An agreement about one development also does not settle every later consequence. For example, agreeing that two characters once worked together does not determine their current loyalties, feelings, or future decisions.
Discuss relevant boundaries before introducing potentially sensitive material, particularly romance, coercion, torture, severe injury, captivity, and death. Players may also agree to keep certain events offscreen, reduce descriptive detail, or focus on their consequences rather than depicting the events themselves.
Respect requests to pause, stop, redirect, or change the level of detail in a scene. Someone can establish or revise a boundary after play has begun and does not owe anyone a personal explanation.
Past participation is not a commitment to continue with similar material. A scene can be adjusted, skipped, or ended without inventing an in-character reason to justify the player's decision.
Agree on whether the scene will take place live or through asynchronous exchanges. Discuss a reply pace that everyone can reasonably manage. For scheduled live sessions, confirm the real-world time and time zone.
When several scenes involve the same characters or events, establish their order within the story. A Discord message posted today might describe something that happened earlier in the character's history. The posting date and the in-universe date are not necessarily the same.
If someone becomes unavailable, check in before changing the situation in a way that affects their character. Participants can pause, adjust the scene, or agree on another way forward. Silence should not be treated as consent or as permission to decide an absent character's actions.
Characters can distrust, oppose, deceive, threaten, or fight one another while their players remain cooperative. Hostility within the story does not justify hostility toward the person playing the opposing character.
Likewise, an in-character refusal should not automatically be treated as personal rejection. If a disagreement arises between players, discuss it outside the fiction rather than retaliating through character actions or manipulating the story to punish someone.
An out-of-character boundary takes precedence over an argument about what a character would realistically do. Players should not feel pressured to accept unwanted material simply because it seems plausible within the setting.
The Terms of Use explain StarForgeRP's provisions concerning website conduct, contributions, publication, privacy, and rights.
Conflict works best when the characters have understandable reasons to act and their choices can affect what happens next. They may want the same resource, disagree about an obligation, pursue incompatible objectives, or interpret an event differently.
Establish what the characters are trying to accomplish and what they stand to gain or lose. Leave room for resistance, negotiation, compromise, retreat, cooperation, and unforeseen decisions. Neither participant needs to determine the entire encounter beforehand.
Combat is only one form of conflict. A disagreement over a contract, an investigation into disputed evidence, or competing responsibilities within an organization can create equally meaningful scenes.
A successful action need not settle every problem, just as a setback need not end the story. Both can change the circumstances that characters must navigate afterward.
Characters may have unusual backgrounds, specialized training, considerable influence, or exceptional abilities. Such concepts can work within StarForgeRP when their histories, capabilities, and limitations make sense in the setting.
Consider what the character has actually learned, what they have experienced, and which tools or resources they can reasonably use. Preparation, equipment, assistance, and circumstances can all affect what someone is capable of accomplishing.
Competence in one field does not imply expertise in every other. Military rank, political influence, or institutional membership does not automatically provide unrestricted authority, confidential knowledge, or access to every resource associated with an organization.
The same care applies to Force-sensitive characters. Jedi and Sith may possess different training, responsibilities, traditions, and institutional relationships. Their affiliation alone does not establish a particular level of ability, personal authority, or involvement in major historical events.
Species, culture, faction, profession, and Force tradition can shape a character's experiences without determining their personality, morality, loyalties, or decisions.
A character does not need extraordinary power or galactic importance to contribute meaningfully. Their responsibilities to a crew, family, employer, community, or individual relationship can provide substantial reasons to participate in a story.
Let established outcomes influence later scenes. A failed negotiation might damage trust or leave an unpaid debt. A successful investigation might reveal a new responsibility, create a difficult choice, or bring someone into conflict with an existing obligation.
Consequences do not always have to be severe. A small favor, misunderstanding, professional success, or change in someone's opinion can matter when it affects what the characters do next.
Keep those developments consistent with what participants established. A consequence becomes part of shared continuity through the story and the agreements surrounding it, not simply because one player announces that it has happened.
StarForgeRP's public pages provide information for players, but that does not mean every character knows what those pages describe.
Before acting on information, consider how the character learned it. They might have witnessed an event, spoken to someone involved, consulted an accessible record, received an official assignment, or discovered evidence through earlier roleplay.
The source also affects how confidently the character can rely on what they know. Hearing an accusation establishes that someone made the accusation, not that it is true. A report may be incomplete, mistaken, misleading, or deliberately falsified.
Character dossiers and story records sometimes contain details that remain unknown to other characters. A concealed affiliation, private relationship, restricted investigation, or hidden identity should not become common in-character knowledge simply because players can read about it.
Use Character Dossier Guidelines for more detail on presenting public information, concealed details, rumors, and disputed accounts. Respect another participant's intended disclosures and unresolved discoveries.
Before joining an established story, read its participation information and communicate with the players involved when an introduction or agreement is needed. An active story is not necessarily open to additional characters.
Even when participation is welcome, the character needs a believable way to become involved. A shared workplace, mutual acquaintance, request for assistance, professional assignment, or outstanding obligation can provide that connection.
Reading about a secret operation does not give a character knowledge of its location, access to its records, or a relationship with its participants. Those connections need to be established within the story.
StarForgeRP stories take place within a setting that other participants also use. Decisions made in one scene may affect characters, organizations, locations, and events that already have established histories.
Before introducing a significant development, consider what earlier material it depends on and who else may be affected. A local dispute, changed relationship, new discovery, or damaged facility can have lasting importance without altering the course of galactic history.
As a proposed development reaches beyond the immediate participants, coordinate with the people responsible for the affected characters or established material. Do not decide another player's involvement, resolve an unfinished story, or revise previously established events without the necessary agreement.
For contemporary roleplay, consult Current Setting to understand StarForgeRP's shared present and the SWTOR storyline developments adopted into its history. That reference contains major SWTOR story spoilers.
When a scene takes place earlier in the timeline, establish its approximate or confirmed date and consider what the characters had experienced or could reasonably know at that point. Later discoveries and changes should not be assumed to have happened already.
Continuity & Canon explains how established SWTOR lore, compatible Legends material, StarForgeRP-created history, alternative storyline outcomes, and uncertain information fit together. Gameplay systems and the events of an individual SWTOR playthrough do not automatically determine the history shared by every participant.
Misunderstandings can happen even when everyone intends to collaborate. If a scene begins to cause disagreement or discomfort, pause and discuss the issue outside the fiction before adding further consequences.
Clarify what each participant understood, including any assumptions about actions, character knowledge, boundaries, or the agreed resolution method. Where appropriate, players can clarify an action, revise an outcome, rewind part of a scene, change its direction, or end it.
Respect a request to stop or avoid material without demanding an explanation. If discussion or the agreed resolution method cannot settle a disputed outcome, leave that result unresolved rather than presenting one player's preferred version as established shared history.
Arrange ordinary roleplay and scene-related discussions through the communication channels the participants have chosen. For archive corrections, contribution questions, continuity inquiries, or site-related privacy, attribution, rights, and administrative concerns, use Contact.
When a story changes something important, preserve enough information for later participants to understand what happened and what remains relevant. Not every conversation or routine encounter needs a permanent record.
Keep the detailed account with the story itself and update the records most directly affected by its consequences. Changes to a character's circumstances belong in their dossier. Lasting developments involving a location or organization should be reflected in the records responsible for those subjects. Related pages can provide a concise account and link to the fuller history when useful.
The Story Archive preserves concluded roleplay with consequences that may continue to affect the setting. A finished story can leave behind unresolved discoveries, changing relationships, obligations, or disagreements without requiring another story to resolve them immediately.
Use the Galactic Timeline when an established event's date or position in the historical sequence is important for understanding connected developments.
Be clear about what the story actually established. An event, a character's interpretation of that event, an allegation, and a future possibility are not interchangeable. Preserve meaningful uncertainty rather than presenting a disputed account or proposed outcome as settled history.
Consider what should be publicly disclosed. A website entry labeled “secret” is still visible to readers. If an intended reveal depends on players not knowing particular information, coordinate what can be published without compromising the story.
Agreement to participate in roleplay does not automatically grant permission to publish another person's original writing, artwork, private information, or other protected contributions. Check the appropriate permissions, credits, and disclosure boundaries before submitting shared material to the archive.
The Terms of Use explain StarForgeRP's contribution, publication, editorial, and rights provisions.
The goal is to keep a reliable record of what matters, not to document every exchange. Preserve the established choices, relationships, discoveries, and consequences that another participant may need to understand before continuing the story.
Before starting a scene—or making a significant change during one—consider the following questions.
Have we agreed on the scene's place, in-universe timeframe, format, and expected pace?
Does each character have a believable reason to participate?
Are important character choices and responses left to the appropriate players?
Do we understand how contested outcomes will be resolved?
Have we discussed and respected relevant player boundaries?
Can each character reasonably know or access the information, people, and places the scene requires?
Have the affected participants agreed to significant developments involving their established material?
Does the scene respect earlier events, existing relationships, and unresolved information?
What lasting changes, if any, will future roleplay need to remember?
Begin with a situation the characters have a reason to care about. Give the other players room to respond, and allow the choices made together to determine where the story goes.