Character Backstories checklist for MUDs

Check that the character's birth date falls within the documented timeline of the setting and does not overlap with major historical events that would prevent the character's existence.

Confirm that any mentioned organizations, guilds, or factions exist in the MUD's current helpfile system or lore documentation.

Verify that all locations referenced in the backstory are accessible areas in the MUD's room database or documented in the setting's atlas.

Ensure the character's abilities, equipment, and knowledge match the technological or magical advancement level documented for their native region and time period.

Verify that the backstory does not contradict established historical events (wars, plagues, regime changes) documented in the MUD's timeline or news system.

List at least three specific situations or needs that would logically bring the character to the current game location and motivate interaction with other players.

Verify that the character's primary motivation can sustain roleplay for more than one session without requiring immediate resolution or external intervention.

Ensure that any mentioned mentors, family, or enemies are either available as NPCs with staff approval, playable by other consenting players, or written as departed/deceased.

Confirm the backstory avoids amnesia, secret royalty, sole survivors of extinct races, or direct lineage to major NPCs without explicit staff permission.

Verify that claimed possessions, social status, and wealth align with starting character statistics and do not exceed new-player equipment limits.

List specific themes, topics, or scenarios from the backstory that require fade-to-black treatment or advance negotiation before inclusion in scenes.

Obtain explicit OOC agreement from any players whose characters are mentioned as relatives, former companions, or significant relationships in the backstory.

Submit a list of potentially triggering content (violence, loss, abuse) to staff via the consent/safety system before roleplaying these elements.

Confirm understanding of the MUD's safety command syntax (e.g., +xcard, +safeword) for pausing or retconning scenes that breach comfort limits.

Store detailed trauma or dark backstory elements in a staff-visible note or journal system, keeping the public version appropriate for general audiences.

Identify specific current in-character political events or power struggles that would logically involve the character based on their faction affiliations.

Review current plot announcements or global events to ensure the character arrives with motivations that can intersect with ongoing narratives.

Share relevant backstory secrets with the MUD's scene coordination staff or tool (e.g., +story requests) to enable organic integration into planned events.

Confirm staff approval for any backstory involving named NPCs of significance (rulers, guild masters) or access to restricted locations.

Ensure that any declared enemies or antagonists have clear, achievable conflict resolution paths or ongoing reasons for rivalry that do not require PvP consent violations.

Create a tiered list of secrets from the backstory mapped to specific OOC dates or IC milestones when they become available for discovery by other players.

Embed subtle behavioral cues or physical tells in the character description that hint at hidden backstory elements without explicit exposition.

Submit plans for backstory reveals that would permanently alter the game world (destruction of locations, death of NPCs) to staff for timeline approval.

Identify which backstory elements are flexible versus fixed, creating a versioning system for potential retcons if canon conflicts emerge during play.

Enter backstory summary and reveal timeline into the MUD's persistent journal or note system for reference by admins and future players of the character.

Convert the backstory into plain text and upload to the MUD's character wiki, database, or +profile system for reference by other players and staff.

Write a 200-word synopsis excluding spoilers for the +finger, +info, or public bio command, highlighting only currently known information.

Input available backstory hooks and availability into the MUD's scene request or plot coordination system (e.g., +scene, +request).

Attach relevant helpfile references or lore article URLs to the character notes to justify canon-heavy elements for admin audit trails.

Set calendar reminders to review backstory alignment with evolving canon at 30, 90, and 180 days after character creation.