StarForgeRP brings original characters and collaborative stories into a shared Star Wars: The Old Republic setting. SWTOR provides the main foundation for its history and lore, compatible Star Wars Legends material supplies additional context, and community roleplay establishes its own continuing history.
Continuity connects those stories. It helps participants understand what happened, who was involved, what changed, and which consequences may still affect other characters. This guide explains how StarForgeRP uses established lore, develops original material, and handles uncertain or conflicting information. You do not need to know every detail of Star Wars history to participate.
For the shared present, adopted SWTOR story boundary, and current galactic circumstances, consult Current Setting. That page contains major SWTOR story spoilers.
Continuity is the history and set of circumstances that stories share. It includes more than major galactic events. A character's former employer, an abandoned settlement, a broken friendship, or an unresolved investigation may remain important years after the original events.
Canon refers to information treated as authoritative within a particular fictional continuity. On StarForgeRP, it helps to distinguish official SWTOR lore, established community history, and what an individual character believes or claims to know. These are not necessarily the same thing.
A character, organization, or event can be part of established StarForgeRP continuity without appearing in an official Star Wars publication. Likewise, an officially published detail does not automatically apply to the Old Republic period or to the version of SWTOR history adopted by StarForgeRP.
For concise definitions of continuity, canon, retcons, character knowledge, and related terms, see Terminology.
SWTOR's narrative provides the primary external foundation for StarForgeRP. Relevant evidence includes story missions, dialogue, cinematics, Codex entries, in-game messages, and other material that establishes information about the setting. Official SWTOR publications can help explain or corroborate that evidence.
Consider how a fact is presented before relying on it. A Codex entry describing an institution is different from a character accusing someone of treachery. The accusation establishes what was said, but it does not necessarily prove the allegation. A speaker's knowledge, motives, and circumstances may affect the reliability of their account.
Where accounts disagree, examine their original context and any subsequent clarification. Give greater weight to directly relevant narrative evidence than to summaries or interpretations that may omit important qualifications.
Star Wars Legends contains additional history, cultures, institutions, and traditions that can help explain subjects SWTOR addresses only briefly. Such material is useful when it fits the relevant period and does not contradict stronger SWTOR evidence.
Historical context matters. A military rank, government office, technology, religious practice, or cultural custom documented thousands of years later may not have existed in the same form during the Old Republic. Shared terminology alone does not establish historical continuity.
Modern Star Wars canon follows a different continuity from the Legends setting associated with SWTOR. Some characters, places, and concepts appear in both, but their histories and circumstances should not be assumed identical. Treat current-canon information as applicable only when there is sufficient support for using it in the setting under discussion.
StarForgeRP also has its own established history. Original characters, organizations, settlements, relationships, discoveries, and roleplay events can become part of the shared setting, along with the consequences of the decisions made during those stories.
The absence of an official SWTOR reference does not make an established community contribution invalid. Before correcting an unfamiliar detail, check the relevant StarForgeRP records and the circumstances in which it was established. An unusual affiliation, personal history, or local development may be intentional and already connected to other stories.
Keep the distinction between official lore and community-created material clear when it matters to the reader. A StarForgeRP organization may have a legitimate place in shared continuity without being described as an official SWTOR institution.
An idea does not become established shared history simply because it fits the setting. A proposed character background, relationship, organization, location, or event remains proposed until its relevant details have been established for StarForgeRP.
Be particularly careful when a proposal involves another participant's material. Do not assume that someone else's character has agreed to an obligation, accepted an appointment, joined an organization, formed a relationship, or participated in an event. Coordinate those connections with the people involved.
A possible relationship or historical connection can remain an opportunity for future roleplay. It does not need a predetermined outcome to be useful.
An event that has actually occurred through coordinated roleplay can become part of shared history before its details are formally recorded on the website. The absence of an archive entry does not, by itself, undo what the participants established.
Interpretation uses available evidence to reach a conclusion that the source does not directly confirm. It may help explain an apparent gap, especially when several established facts point toward a reasonable possibility.
Make the basis of an important interpretation clear, particularly when another character or story may depend on it. If more than one explanation remains possible, do not present your preferred conclusion as an established fact.
Inventing a character's personal history, an original organization, or an undocumented event is creative development rather than interpretation of existing evidence. The idea may fit StarForgeRP, but its plausibility does not make it a previously established discovery.
Some questions remain unanswered because information has been lost, concealed, disputed, or only partly documented. Other claims may lack sufficient evidence to support them. These situations require different treatment, and none automatically proves that a claim is false.
If a search does not find a record, that does not establish that the subject never existed. On the other hand, missing documentation is not a sound basis for confidently inventing an explanation.
Respect uncertainties that are part of ongoing stories. A concealed identity, disputed account, or unresolved discovery may be deliberately left open. When no answer is needed, there is no reason to settle the question prematurely.
Current Setting maintains StarForgeRP's adopted present and the SWTOR storyline developments included in its shared history. The Galactic Timeline provides the wider historical sequence and distinguishes confirmed dates from reconstructed, approximate, or otherwise uncertain placements.
A new SWTOR release does not automatically advance StarForgeRP's shared present. Equally, a date adopted for the community's chronology does not independently establish that date as official SWTOR history. Always distinguish an official story event from the community's placement of that event on its calendar.
Earlier stories and flashbacks must follow the circumstances of their own period. Before establishing a scene, check which events have occurred, which organizations and political arrangements existed, and what information was available at the time. The real-world date on which participants play a scene is not necessarily its date within the fiction.
Dates are most useful when they explain a character's experiences, the order of events, or the consequences of a historical development. Preserve supported dates, but do not assign an exact year where the evidence establishes only a sequence or approximate period.
StarForgeRP uses BBY, meaning Before the Battle of Yavin, for much of its historical dating. Larger BBY numbers represent earlier years. This is a retrospective reference convention for readers, not a calendar that Old Republic characters would ordinarily name after a battle in their distant future.
Calculate character ages only from supported birth information and the relevant event date. If the precise birthday is unknown, an approximate age or age range may be more accurate than an exact number.
When developing an original character, a newly proposed birth date or other personal-history date remains provisional until established. An age calculated from that date is provisional as well. A calculation cannot independently confirm the accuracy of its starting information.
Investigate conflicting dates before relying on them. A page being updated more recently does not necessarily mean its chronology has deliberately replaced an earlier account.
Historical events can shape a character's life without placing that character at the center of galactic history. Military service, education, family responsibilities, employment, displacement, recovery, and changes in local government can all connect an individual to the wider setting.
Connections to major figures and powerful institutions need appropriate context. Serving in the Sith Empire does not automatically mean someone has personal access to the Dark Council. Membership in the Jedi Order does not establish participation in every important Jedi operation. Institutional affiliation, personal relationships, authority, and involvement in particular events are separate matters.
Unusual backgrounds are possible when their circumstances are credible and they leave other participants meaningful choices. Significant accomplishments, privileged access, and exceptional resources should have an understandable basis rather than relying on proximity to famous characters or events.
The Character Creation Guide provides more detailed help with backgrounds, affiliations, personal circumstances, and connections to established history.
SWTOR allows players to make decisions that can produce different versions of the same events. Some choices affect allegiances, relationships, political circumstances, and whether particular characters survive. Those outcomes cannot always coexist within one shared history.
Before treating a particular outcome as established, check whether StarForgeRP has adopted it. A result from one person's game playthrough does not automatically determine what happened for everyone in the community setting.
When an unresolved choice matters to a shared story, discuss the question with the affected participants before building further developments around a particular result. If the outcome has no meaningful effect on the current story, it may be better to leave it unspecified.
SWTOR's gameplay represents the fictional galaxy through systems designed for play. Those systems can be useful for portraying characters, but they do not necessarily establish what is possible or impossible within the setting.
Character-creation options, playable species, Origin Stories, Combat Styles, equipment restrictions, levels, combat balance, and repeatable encounters should not be treated as universal rules of in-universe history or capability.
Likewise, completing a mission on an in-game character does not automatically give a StarForgeRP character the mission protagonist's achievements, relationships, authority, or possessions. Those details require an appropriate basis within the shared story.
Use narrative evidence when establishing lore and gameplay mechanics when they are useful for representing that lore. The two can inform each other without being interchangeable.
Information available to players through the website is not necessarily known to their characters. A character needs a reasonable way to have learned something before acting on it, particularly when it concerns classified operations, concealed identities, restricted archives, or events witnessed by very few people.
Consider where the information originated. Was it personally witnessed, learned through professional duties, passed along by another character, published in an official report, or circulated as a rumor? What could the source reasonably know, and how reliable is the account?
Distinguish an event from the claims made about it. A legitimate document may contain incorrect information. An honest witness may misunderstand what happened. A widely repeated rumor can be part of the setting without its underlying allegation being true.
Preserve participants' control over their characters' responses, disclosures, and future decisions. Knowledge of another character's secret does not automatically establish permission to reveal it or dictate its consequences.
Public website records require additional care. Information presented on a public page can be read by other players even when their characters would not know it. If a secret identity, private plan, discovery, or future revelation must remain unknown to players, do not publish the revealing details prematurely. A spoiler warning or in-character secrecy designation does not prevent access to public text.
Consult Roleplay Guidelines for player agency, coordination, and information access. Character Dossier Guidelines explains how to distinguish player-facing information from in-character knowledge when maintaining character records.
New characters and original stories should fit into the established setting through understandable connections. Consider where something belongs, what circumstances produced it, who is involved, and how it might affect people already living or working there.
A development does not need galactic consequences to be significant. A disputed inheritance, damaged friendship, struggling business, research project, or unsettled professional obligation can affect several characters and remain relevant long after the original scene.
Give important capabilities, resources, achievements, and positions of authority an appropriate foundation. A character may be capable or influential without having unrestricted power, access, or control over the people around them.
Coordinate substantial developments involving another participant's character or established shared material. Agreement about a past event does not predetermine how everyone involved must feel about it or what they will do next.
When bringing an existing character into StarForgeRP, begin with the qualities and experiences that make the character recognizable. Then examine which parts of their previous history fit the Old Republic setting and the continuity already established here.
Check dates, affiliations, titles, resources, achievements, relationships, and important events. Some details may transfer naturally, while others need adaptation or cannot be reconciled with the circumstances of this setting.
Preserve meaningful personal connections where they can fit coherently, but do not silently rewrite another character's history to accommodate the adaptation. Discuss consequential changes with the people whose established material would be affected.
A revised background can preserve a character's identity without requiring every event from their previous setting to have happened in StarForgeRP.
Shared continuity becomes easier to use when important developments are recorded clearly. Future participants should be able to understand what happened, who was involved, when the event occurred if that is known, and what changed afterward.
Preserve ongoing obligations, important discoveries, unresolved questions, and consequences that may affect later stories. Where the distinction matters, identify what was established through play and what remains an account, allegation, interpretation, or unanswered question.
Keep the detailed record with the subject it primarily concerns. A character dossier should explain a character's experiences and changing circumstances. An organization or location page should describe developments affecting that subject. Campaign and mission records should preserve the events, participants, and outcomes of the stories themselves.
Related pages can provide shorter explanations and direct readers to the appropriate primary account. They do not need to repeat the same history in full.
The Story Archive connects concluded roleplay with the history and consequences it leaves behind. Finishing a campaign or mission does not necessarily resolve every question or end every relationship created during it.
Not every routine conversation or minor activity needs a permanent record. Concentrate on information that later participants are likely to need.
To propose an archive entry or request a correction or addition to established records, use Contact StarForgeRP. Explain the development, identify the affected pages or subjects, and include relevant evidence, credits, and contributor permissions.
The Terms of Use explain the site's provisions concerning contributions, rights, permissions, and editorial changes.
When two sources appear to disagree, first determine whether they describe the same subject, period, location, and circumstances. A character may have changed affiliations. A damaged installation may later have been rebuilt. A disputed allegation and a historical account of the underlying event may describe different kinds of information.
For external lore, begin with the most directly relevant SWTOR evidence. Examine the original context where practical, and use supplementary references to clarify rather than automatically override it. Several summaries repeating the same account do not provide independent confirmation.
For StarForgeRP-created history, examine the relevant records and the sequence of events. Check whether an apparent contradiction reflects an earlier circumstance, a later development, a different perspective, an explicit correction, or an intentional revision.
Do not assume an unfamiliar detail is a mistake simply because it differs from what another page describes.
New information can clarify earlier history without changing what happened in existing roleplay. Before incorporating an official SWTOR development, determine when its events occur and whether they fall within StarForgeRP's adopted story boundary.
If two established accounts genuinely cannot both be correct under the same circumstances, identify the conflicting claims and their supporting evidence. Determine whether the issue calls for a factual correction or a deliberate retrospective change to established continuity, commonly called a retcon.
A factual correction addresses demonstrably inaccurate information. A retcon changes how previously established history is understood. Either may affect connected records, but an intentional change to shared history deserves particular care.
Keep necessary revisions as focused as possible. Do not combine incompatible accounts merely to avoid acknowledging a contradiction, and do not replace another participant's established history or outcomes without appropriate coordination.
When a substantial change is proposed, consider the affected characters, organizations, locations, and stories, along with any applicable contribution or editorial provisions.
Not every uncertainty needs an immediate solution. Characters may investigate incomplete evidence, hold conflicting beliefs, or disagree about events without the shared setting requiring a definitive explanation.
Leaving a question unresolved is different from declaring that any answer is equally well supported. Preserve what the available evidence establishes, identify genuine uncertainty, and avoid inventing a conclusion merely to make the record appear complete.
When a shared decision becomes necessary, distinguish information supported by evidence from an interpretation or an original community decision. Coordinate any outcome that would materially change another participant's established contributions.
For a continuity discrepancy or page correction requiring editorial review, use Contact StarForgeRP. Identify the affected material, explain the competing claims, and include the available supporting evidence.
The amount of checking needed depends on the significance of the claim. An ordinary personal preference rarely requires the same investigation as a new institutional position, a major historical connection, or a development affecting several established characters.
Before establishing consequential material, consider the following questions.
Does the idea fit the relevant historical period and StarForgeRP's adopted setting?
Which details are established, interpreted, proposed, or still uncertain?
Do the dates, character ages, affiliations, and surrounding circumstances agree?
Have existing records established relevant relationships, events, or consequences?
Does the idea rely on a gameplay mechanic or an assumption borrowed from another Star Wars era?
What could the character reasonably know, and how would they have learned it?
Would the proposed material assign another participant's character an unestablished history, relationship, decision, or outcome?
If the story changes something important, what should future participants be able to discover about that change?
Which questions can remain unresolved without preventing the story from continuing?
Use established history to give new stories a convincing foundation, not to predetermine their endings. Preserve what earlier participants have created, give consequential developments clear connections, and leave room for characters and their relationships to change through play.