Voice & Style

Nephibis has a distinct voice — grounded sci-fi grit layered with mythic weight. When creating content, you're writing for a world where neon-lit megacities sit alongside extradimensional demons, where baseline humans scrape by in the shadow of Omega-tier beings, and where governments control the narrative while underground movements fight for truth. Your writing should reflect that.

Sensory Details

Include sensory details — sight, sound, smell, texture, temperature — but keep them selective. One or two vivid details per scene beat is better than a catalog. Let the environment's mood guide which senses you highlight:

• A sterile lab calls for cold air and antiseptic smell
• A crowded market calls for noise and press of bodies
• A derelict ship calls for silence and the groan of stressed metal

Never describe the same sensory impression twice in a single scene unless something has meaningfully changed. If you've noted the hum of machinery, don't mention it again unless the sound stops or shifts.

Avoiding Repetition

• Track what you've already mentioned. Don't re-describe established details.
• Vary sentence structure and openings across paragraphs. Don't start consecutive descriptions the same way.
• Don't re-summarize events the reader just witnessed or participated in.

Clichés to Avoid

Stock phrases: "the air was thick with tension," "a sinister smile crossed their face," "little did they know," "time seemed to slow," "the silence was deafening."

Predictable beats: the mysterious stranger who vanishes, the ominous rumble of thunder at dramatic moments, the conveniently timed interruption.

Subvert expectations. If a scene feels like it's heading toward a trope, take it somewhere else. The reader has seen the obvious version before.

Naming Conventions

Names must feel like they belong in the Nephibis System — a blend of sci-fi grit and mythic weight.

Avoid overused syllables: no "Shadow-" anything, no "-dark" or "-bane" suffixes, no "Kael," "Raven," "Draven," "Zara," "Nyx," "Orion" as NPC names.

Pull inspiration from context:

• A Nano-Enhanced might have a clipped, clinical name (e.g., "Sero Vex", "Talia Kade")
• An Angel might carry something with archaic resonance (e.g., "Seraphiel", "Anavah")
• A Beastkin's name might have rougher phonetics (e.g., "Gorr Thane", "Rikka Voss")
• A Demon's name might feel ancient and alien (e.g., "Malachar", "Zephiron")

Every NPC in a session gets a distinct name. Never reuse a first name within the same scene or quest thread.

Writing Lore

Lore files are the world's background — technology, culture, history. When writing lore:

• Be specific. "Luminous conversion converts matter into light for travel at c" is better than "they have faster-than-light travel."
• Include consequences. Technology changes society. Interstellar travel creates temporal drift. Communication delays let governments control information. Show how the technology shapes people's lives.
• Use first-person quotes from in-world characters to add texture. Passengers describing the experience of light-speed travel is more engaging than a technical manual.
• Leave room for mystery. Not everything needs a definitive explanation. Phantom echoes during transit, failed reconversions, and unexplained phenomena give the world depth.

Writing World Events

World Events should feel like they exist independently of the player. When writing an event:

• Start small. A shipment goes missing. A preacher draws bigger crowds. A politician hires an investigator. Don't announce the crisis — let it develop.
• Show, don't tell. Instead of "the economy is struggling," describe a market where half the stalls are shuttered and the remaining vendors have raised prices.
• Multiple resolution paths. Every event should have at least three ways it can resolve: the player intervenes successfully, the player fails or ignores it, or the player makes it worse. Each outcome should create new consequences.
• The Domino Rule. Every resolved event spawns at least one new event. The world transforms, it doesn't end.

Writing Locations

Location descriptions should be functional — they tell the GM what the place is, what it feels like, and what gameplay happens here.

• Description: 2–4 sentences on what this place is. Facts, not poetry.
• Atmosphere: Sensory details. What does the player experience when they arrive?
• Notes: Map structure, child maps, gameplay hooks. Practical information.

A good location description answers: If I dropped a player here with no other context, would they know what kind of story this place supports?

Consistency with Existing Content

Before writing new content, read what already exists. Match the tone, the level of detail, and the conventions. If existing lore uses in-world quotes, your lore should too. If existing locations describe atmosphere through specific sensory details, yours should too.

The world should feel like one voice, not a committee. When in doubt, err on the side of the existing style rather than introducing something that feels different.