Skip to main content

Academy 101: How to Write Collaborative Fiction

Master the Art of Collaborative Storytelling

Learn the art of writing collaborative fiction for PBeM games. Master techniques like avoiding god-modding, leaving hooks for other players, using LCARS format, and creating engaging collaborative stories.

DATA-ARCHIVE: ACADEMY_101_52

Academy 101: How to Write Collaborative Fiction

INTRODUCTION_DATA

The Art of Collaborative Storytelling

Play by Email (PBeM) games are a unique form of collaborative fiction. Unlike solo writing, you're creating stories with other players, not just alongside them. This requires specific skills and techniques to create engaging, interactive narratives.

This guide teaches you the fundamentals of writing collaborative fiction for PBeM games, focusing on techniques that make your posts engaging, interactive, and respectful of other players' characters.

TECHNIQUE_01

How Not to God-Mod

God-modding is controlling other players' characters or dictating outcomes without their consent. It's one of the most important rules in collaborative fiction.

What NOT to Do:

"Lieutenant Smith grabbed Commander Jones by the arm and forced him to the ground. Jones struggled but couldn't break free."

Problem: You're controlling Commander Jones's actions and reactions. The player of Commander Jones should decide how their character responds.

What TO Do:

"Lieutenant Smith reached for Commander Jones's arm, his expression urgent. 'Commander, we need to get down—now!'"

Better: You're describing your character's action and leaving Commander Jones's response open for their player to write.

Key Principles:

  • Control only your character: Describe your character's actions, thoughts, and dialogue. Never dictate how other characters react.
  • Use "attempt" language: "Smith tried to grab Jones's arm" instead of "Smith grabbed Jones's arm."
  • Leave reactions open: End your posts with actions that invite responses, not outcomes that force them.
  • Respect other players: Their characters are theirs to control. Your character can influence, but not control, others.
TECHNIQUE_02

How to Leave Hooks for Other Players

Hooks are elements in your post that invite other players to respond and continue the story. Good hooks make collaborative fiction flow naturally.

Types of Hooks:

🎣 Direct Questions

Ask another character a question that requires a response: "What do you think, Commander? Should we proceed?"

🔗 Action Invitations

Create situations that invite other characters to act: "The door slid open, revealing..." (invites someone to describe what's inside)

💭 Emotional Moments

Show your character's vulnerability or need: "Smith looked uncertain, waiting for guidance."

🎭 Character Interactions

Reference other characters by name: "Smith turned to see what Commander Jones was doing."

Example of Good Hooks:

Lieutenant Smith stepped onto the bridge, PADD in hand. The readings from the research outpost had been puzzling her all morning.

"Captain," she said, approaching the command chair, "I've completed my analysis, but I'm seeing something unusual. Commander Jones, could you take a look at these sensor readings? I'd value your perspective."

She handed the PADD to the Captain, then glanced at the Science station where Ensign Chen was working. Maybe Chen has seen something like this before? Smith thought, making a mental note to ask after the briefing.

Notice: This post includes multiple hooks—a direct question to Commander Jones, a reference to Ensign Chen, and an open-ended situation that invites responses from multiple characters.

TECHNIQUE_03

How to Use the LCARS Format

At Star Trek: Freedom, we use the LCARS (Library Computer Access/Retrieval System) format for posts. This format helps organize information and creates an immersive Star Trek experience.

Standard LCARS Post Format:

USS Hades - Bridge
Stardate: 2446.09.18
Lieutenant Sarah Chen - Science Officer

[Your post content goes here. Write in third person, describing your character's actions, thoughts, and dialogue.]

Format Elements:

  • Location: Where the scene takes place (e.g., "USS Hades - Bridge", "Starbase Freedom - Promenade")
  • Stardate: The in-game date (provided by the CO or mission briefing)
  • Character Name & Rank: Your character's full name and position
  • Post Content: Written in third person, past tense (e.g., "Chen walked" not "I walk" or "Chen walks")

Tips for LCARS Formatting:

  • Keep location and stardate consistent with the mission briefing
  • Use your character's full name and rank for clarity
  • Write in third person throughout (even thoughts: Chen thought not I thought)
  • Use past tense for narrative consistency
  • Keep formatting clean and readable
TECHNIQUE_04

Creating Engaging Collaborative Stories

Show, Don't Tell

Instead of stating emotions or reactions, show them through actions and dialogue:

  • Tell: "Smith was nervous."
  • Show: "Smith's hands trembled slightly as she adjusted the controls, her voice quieter than usual."

Include Internal Thoughts

Use italics to show your character's internal thoughts, which adds depth and helps other players understand your character's perspective:

Chen studied the readings, her mind racing. This doesn't make sense. The energy signature is familiar, but I can't place it. Could it be related to the incident last year?

Balance Action and Reaction

Good collaborative fiction balances:

  • Action: What your character does
  • Reaction: How your character responds to others
  • Interaction: Engaging with other characters
  • Reflection: Your character's thoughts and feelings

Leave Room for Others

Don't resolve everything in your post. Leave questions unanswered, situations unresolved, and opportunities for other players to contribute. The best collaborative stories are built together, not by one person.

TECHNIQUE_05

Common Mistakes to Avoid

❌ God-Modding

Controlling other characters or dictating outcomes. Always leave other characters' reactions open for their players to write.

❌ Resolving Everything

Don't solve the entire mission in one post. Leave problems, questions, and situations for others to address.

❌ Ignoring Other Characters

Writing posts that don't interact with others. Reference other characters, respond to their actions, and create opportunities for interaction.

❌ Writing in First Person

PBeM posts should be in third person ("Chen walked" not "I walked"). This creates a narrative style consistent with Star Trek episodes.

CONCLUSION_DATA

Ready to Start Writing?

Now that you understand the fundamentals of collaborative fiction, you're ready to start writing your own Star Trek stories!

Star Trek: Freedom offers optional Academy training to help new players master these techniques. Learn more about what makes Star Trek: Freedom unique or explore our guide to Star Trek PBeM communities.