A character dossier helps readers understand a character's life, recognize possible connections, and follow the history that continues to shape them. It brings together their identity, circumstances, relationships, capabilities, and opportunities for future roleplay.
Begin with a clear account of the character's present life. As their story develops, preserve the experiences and changes that still matter. Someone encountering the character for the first time should be able to understand who they are now and how they reached that point.
A character dossier serves three main purposes:
Understanding the character: Explain who they are, what occupies them, where they belong, and what matters to them.
Preserving continuity: Record experiences, relationships, decisions, and consequences that later stories may depend on.
Finding opportunities: Give other players believable reasons to encounter the character or become involved in their circumstances.
Choose details that contribute to those purposes. A daily routine can reveal personality and suggest an encounter. A possession may matter because of its history, practical use, or an obligation attached to it. The aim is not to document everything about a character, but to preserve what helps readers understand them and their place in the setting.
Open with the character's occupation or principal activity, home or recurring base, important connections, and immediate concerns. Give readers a sense of the life the character is currently living before explaining the experiences that brought them there.
Use the Character Creation Guide when developing the underlying concept. Consult Current Setting when the character's circumstances depend on StarForgeRP's shared present; that page contains major SWTOR story spoilers. Use the Timeline to investigate relevant historical context.
The Blank Character Dossier provides the standard sections, optional subsections, and individual fields. For an ordinary dossier, retain its standard sections and include optional material when it adds something useful. Keep established headings when they accurately describe the content, and add character-specific subsections when the circumstances genuinely warrant them.
When a complete dossier development or revision is expressly requested, address every standard and optional field and subsection. If information is genuinely unknown, unsupported, or inapplicable, say so briefly rather than inventing an answer. The following two profiles are conditional and may be omitted when they do not apply:
Droid / Synthetic Profile: Include this profile for an applicable artificial character, addressing the relevant aspects of construction, purpose, programming, memory, autonomy, modifications, and maintenance.
Force Profile: Include this profile when Force sensitivity, use, training, or an established unresolved question about sensitivity makes it relevant. Do not introduce Force sensitivity simply to fill the section.
Complete the constituent fields of an applicable conditional profile. When a definite answer would be misleading, explain the uncertainty or inapplicability. An unknown teacher, for example, should not become an invented one merely because the template asks about instruction.
Remove bracketed prompts, author instructions, and the words “Optional” or “Conditional” from headings in the completed dossier. If two fields concern the same development, explain it in the most appropriate section and refer to it briefly elsewhere. Avoid repeating the same account under several headings.
Explain the significance of the character's household, workplace, community, affiliations, and familiar places. Describe what those connections mean to this individual rather than providing only a list of names.
Use Lore to investigate relevant species, cultures, organizations, factions, and Force traditions. Use Galaxy to identify physical locations, and the Character Directory to find other established dossiers. Where a suitable page exists, link the specific subject and explain the character's connection to it. Readers should not need to open another page just to understand the basic relationship.
Keep different kinds of connection distinct. A character's birthplace may differ from the community that raised them. Their cultural identity need not determine their political allegiance, and membership in an organization does not necessarily imply personal loyalty to everyone within it.
Species, culture, profession, faction, and Force tradition can influence a character without determining their personality, morality, or future choices.
Before adding history, check the existing dossier and relevant character, organization, location, and story records. An experience missing from one page may already have been established elsewhere.
Within your authority over the character, ordinary undocumented details can be developed. These might include appearance, habits, interests, motivations, education, routines, and personal background. Build on existing characterization rather than replacing it, and keep abilities, resources, and accomplishments proportionate to the character's experience.
A detail does not need to be dramatic to be useful. A familiar place, a professional habit, or a long-standing responsibility may explain more about the character's daily life than an additional extraordinary achievement.
During editorial review, identify substantive additions as proposed character material. Explain what supports them and whether they affect chronology, relationships, or other established records. An addition may fit SWTOR lore and the character's existing background without being something that was previously established.
Preserve information deliberately left unknown, concealed, disputed, or unresolved. Do not settle another participant's mystery, assign their character involvement in an undocumented event, or determine the result of an unfinished story simply to complete a field.
If a proposed addition would substantially affect another participant's character or shared history, coordinate it before treating it as established continuity. Until then, a possible relationship, assignment, or encounter can remain a proposal or roleplay opportunity.
Never invent player handles, availability, contact preferences, publication consent, or archive classifications. Use “Not provided” or “Not specified” when the relevant information has not been supplied.
Write the dossier so another player can understand the character without deciphering an elaborate fictional filing system. Clear prose is usually the best way to explain their life, relationships, and experiences.
In-character reports, correspondence, testimony, and similar documents can add perspective when they serve the character's presentation. Remember that such records reflect what their authors know, believe, remember, or want others to believe. A statement appearing in a report is not automatically an objective fact.
Separate established information from allegations, rumors, personal beliefs, and incomplete accounts. When uncertainty matters, explain its nature without inventing an answer. If different people hold conflicting views of the character, identify whose perspective is being represented rather than presenting one account as universally accepted.
A public dossier may reveal information that remains private within the fiction. Readers can know that a character has a concealed affiliation or a disputed past without their own characters possessing that knowledge.
When information has meaningful restrictions, explain how another character might learn it. Possible routes include direct observation, conversation, research, professional access, or experience established through earlier roleplay. Consider what the information's source could reasonably know and whether that source is reliable.
Marking a passage “classified” does not conceal it from website readers. If a future revelation depends on players remaining unaware, leave the revealing details off the public dossier until disclosure is appropriate. Respect information boundaries established by other participants.
If a dossier discusses major SWTOR or StarForgeRP story outcomes, consider a brief spoiler notice before the relevant material. A warning helps readers make an informed choice, but it does not authorize disclosure of another participant's protected information or an intended future surprise.
Consult Roleplay Guidelines for the wider expectations concerning character knowledge, communication, player boundaries, and agency.
Describe established relationships and their continuing significance. Check related records for shared experiences, agreements, obligations, and consequences that belong in the character's history. When names, aliases, or titles differ between records, confirm that they refer to the same individual before connecting them.
Explain the character's own part in a relationship without assuming that both participants understand it in the same way. A character may regard an earlier meeting as a friendship while the other remembers only a professional exchange. Such differences can be meaningful when the perspectives themselves are established.
Coordinate new shared history with the participants concerned. Do not assign another character feelings, decisions, family ties, agreements, injuries, or past involvement that their player has not established.
A possible connection does not need a predetermined history. If two characters could plausibly meet through a common employer, location, or responsibility, the opportunity can remain a roleplay hook until the participants decide what happens.
Select experiences that help explain the character's present skills, beliefs, relationships, choices, responsibilities, or difficulties. A formative event should have enough context for readers to understand what happened and why it still matters, without turning the dossier into a complete account of every event the character witnessed.
Preserve meaningful former affiliations and earlier circumstances. Identify when an appointment, allegiance, residence, or responsibility belonged to an earlier period rather than presenting it as current. Historical information remains useful even after the character's circumstances change.
Use Continuity & Canon when assessing consequential lore claims, conflicting accounts, or intentional revisions. Investigate unfamiliar community history before treating it as an error. A character, relationship, or event established through StarForgeRP does not need an official SWTOR counterpart to belong to the shared setting.
Check that external lore applies to the relevant Old Republic period. Gameplay options, statistics, and equipment do not independently establish a character's biography, training, authority, or achievements. Completing SWTOR missions on an in-game avatar also does not automatically give the roleplay character those experiences, relationships, or accomplishments.
Where SWTOR offers different storyline outcomes, use the version adopted into StarForgeRP continuity when it has been established. Do not choose a branch based solely on an individual playthrough, and do not introduce later developments before the community's adopted story boundary.
Keep significant dates when they help readers understand the character's life. An approximate period is preferable to an exact year that the available information cannot support.
For dated experiences, include the character's age when established birth or activation information supports it and the age adds useful context. When the precise birthday or timing is uncertain, use an approximation or range. A birth or activation entry normally needs no accompanying age.
Check the order of upbringing, education, training, employment, travel, and changes in affiliation. Make sure the character had sufficient time and opportunity for the experiences and responsibilities being described.
New personal dates developed during review should remain identifiable as proposals until established. Ages calculated from those dates depend on the same proposed information.
Use Current Setting for StarForgeRP's shared present instead of repeatedly restating that changing baseline throughout individual dossiers. For earlier experiences and flashbacks, consult the Galactic Timeline to distinguish confirmed dates from reconstructed placements, approximate periods, and events whose sequence is known without an exact year.
Remember that BBY dating is a retrospective convention for readers, not a calendar based on an event Old Republic characters know lies in their future. Use historical dating consistently, especially when a dossier includes several generations or events separated by many years.
When records disagree, investigate chronology, perspective, explicit corrections, and intentional revisions. Preserve meaningful uncertainty rather than silently choosing whichever account is most convenient.
Describe the training and experience behind important abilities. Explain what the character can do reliably, what remains outside their expertise, and which tasks depend on preparation, equipment, assistance, or particular circumstances.
When Force abilities matter, distinguish sensitivity, instruction, practiced disciplines, and the character's own understanding of their abilities. Being Force-sensitive does not by itself establish formal Jedi or Sith training, a particular rank, or mastery of a tradition.
Explain the actual scope of rank, credentials, appointments, and institutional authority. Serving the Galactic Republic, Sith Empire, Jedi Order, or another organization does not automatically provide unrestricted command, access, or influence throughout that institution.
Likewise, distinguish personal possessions from borrowed, assigned, shared, or conditionally available resources. A character may operate a vessel, use an organization's equipment, or request assistance without personally owning everything involved.
Keep the explanation grounded in the character's circumstances. Important limitations help other participants understand what cooperation, preparation, or outside expertise might reasonably contribute.
A useful roleplay hook begins with something already present in the character's life. Give readers a concrete situation, explain what another character could contribute, and provide a believable way to discover or become involved in it.
Work: A service offered, contract sought, professional problem, or need for specialist assistance.
Place: A familiar venue, shared workplace, recurring journey, or community responsibility.
Relationships: An established mutual contact, previous dealing, or unresolved obligation.
Personal stakes: A goal, investigation, disagreement, or practical difficulty that invites someone else's involvement.
Hooks do not need to promise a major conflict or a predetermined adventure. A technician seeking a difficult replacement part, for example, might encounter a supplier, a courier, another engineer, or someone who knows where suitable equipment can be found. Their responses could lead to cooperation, disagreement, or an entirely different solution.
Leave room for participants to refuse, negotiate, misunderstand, compete, or suggest another approach. The hook establishes an opening, not another character's involvement or the result of a future scene.
Keep individual opportunities with the dossier. Use RP Hooks for further guidance and to check for listed opportunities. A published dossier does not, by itself, establish that its player is available for new roleplay.
Review the dossier when roleplay changes something future participants will need to know. Update the opening overview, summary fields, current circumstances, relationships, and relevant history together so the record does not describe different versions of the character's situation.
Preserve lasting consequences without documenting every routine conversation. Significant changes might include a new responsibility, an ended affiliation, an established relationship, an injury with continuing effects, an important discovery, or an unresolved obligation.
Find associated campaigns, missions, and events through Roleplay, then link the specific record where available. Explain this character's participation and the consequences for their life within the dossier. Leave the full account of the event with the story record responsible for maintaining it.
When a change affects another character, organization, or location, consult the connected record and coordinate any necessary correction or revision. Do not assume that updating one dossier automatically changes another page.
Three kinds of status may appear in or alongside a character dossier:
Current Status: The character's condition within the fiction, such as alive, missing, imprisoned, deceased, destroyed, or deactivated.
Archive Status: The dossier's actual archive classification, where one has been specified.
RP Availability: Information provided by the player about arranging roleplay involving the character.
These fields answer different questions. A living character may be unavailable for new scenes, and a deceased character may still have important historical connections. Do not infer a player's availability or an archive classification from the character's fictional condition.
Retain significant history even when the character becomes inactive, their circumstances change, or their player stops accepting new scenes. Earlier experiences may remain relevant to other characters and continuing stories.
StarForgeRP dossiers are public. Include a player's handle, attribution name, contact method, or availability only when that person intends the information to be publicly associated with the character.
Permission to describe a fictional character does not authorize disclosure of the player's private information. Likewise, information supplied privately for an administrative question or correction should not be treated as material intended for publication.
Contribute writing and images only when you are entitled to supply them for publication. Preserve applicable credits and attribution. Crediting a contributor does not replace the permission required to use their work.
Consult Terms of Use for contribution permissions, editorial handling, corrections, updates, removal requests, and rights matters. Use Privacy Policy for information about the treatment of player and contributor information.
Use images that help readers recognize or understand the character. Check visible features, clothing, equipment, and surroundings against the character's description and the relevant era.
Give meaningful images concise alt text describing useful visible information. Keep essential character details in the prose. Use readable paragraphs, descriptive links, and lists where they make information easier to find.
Check the reading order on mobile, particularly when images or columns are used. Keep related material together and avoid relying on color alone to communicate a distinction.
Review the completed dossier as a whole before submitting it. Check that the character's present circumstances, history, and connections make sense together and that the record preserves what future stories may need.
Does the opening establish the character's present life, principal activity, and important connections?
Does the history explain meaningful influences, experiences, and consequences?
Does the coverage match the assignment, including all required fields for an expressly requested complete dossier?
Are the conditional profiles applicable, with author instructions and heading qualifiers removed?
Are newly developed character details distinguishable from established continuity during review?
Do significant dates, ages, abilities, affiliations, authority, and resources fit together?
Have relevant relationships and developments documented elsewhere been checked?
Are beliefs, rumors, disputed claims, and meaningful uncertainty represented accurately?
Are the differences between reader knowledge and character knowledge clear?
Are other participants' agency, protected information, and unresolved outcomes respected?
Do roleplay hooks provide believable access while leaving room for different responses?
Have useful internal destinations been linked to the correct pages?
Have lasting changes been reflected consistently without repeating the same history unnecessarily?
Are the character's fictional status, archive classification, and player availability kept distinct?
Is any published player information intended for public association with the character?
Are contributed materials suitable for publication, with necessary permissions and credits?
Where significant story spoilers appear, is there an appropriate warning without exposing protected revelations?
To submit a new dossier or request a revision, open Contact StarForgeRP and select “Character dossier submission or update” in the contact form. Name the character, describe the material being added or changed, and include the existing dossier URL when applicable, relevant reference links, and necessary credits or permissions.
Submissions are reviewed; publication is not guaranteed. Material changes involving another participant's established contributions may require coordination before they can be adopted.
A useful dossier gives readers a clear understanding of the character and preserves what future stories may need. Let subsequent choices and shared experiences determine what happens next.