Fighting Hell Banner

Submission Guidelines

Finley Vorden doesn't work alone. The "& Co." on the cover exists for a reason. He's smart enough to recognize his limitations (and lucky enough to find people willing to compensate for them). When you contribute to this guide, you're becoming one of these writers.

To start, pick an Ilhdeinian name, then decide who that person is. Are they a cautious cartographer who triple-checks every detail? A reckless thrill-seeker who survived plenty of things they shouldn't have? Your character should have a voice distinct enough that readers could tell your entries apart from others without seeing your name. If they're pompous, let it show. If they're terrified of everything, let that seep into their warnings. This guide works because it's messy and full of personalities that sometimes contradict each other. If you're unsure whether an Ilhdeinian name fits, check existing NPCs or ask J.P. Once you pick a name, stick with it across all your contributions.

Each entry on this site should give adventurers reasons to explore. Make them useful, entertaining, and a reflection of your interests.

The Canon Rule

For anyone looking to expand Ilhdeinia, respect what came before.

J.P. Sariz is the steward of this canon. All submissions require his approval, and you'll need to share your work with him (commentator or editor access at minimum. He won't change your words, but he'll flag anything that breaks established lore).

Before you start writing:

  • Check the existing guide to see what's already established about your topic

  • Search for any mentions of locations, factions, or NPCs that connect to what you're planning

  • Check the Writing Tracker, then message J.P. to confirm no one else is currently working on the same subject

  • If you're expanding something another writer created, get their permission first, or even collaborate with them on the expansion!

Speaking of which, expansion is usually the goal. Fill in the gaps and unexplored corners. Add depth to what exists. Rewriting or contradicting existing material should happen rarely, and only when there's a compelling reason that J.P. approves.

Adventure Agnosticism

Different adventuring parties experience Ilhdeinia differently. Maybe your group fought in the War of the Sisters. So did another group. But their companions aren't yours, and your decisions aren't theirs.

When you write for the guide, focus on what's consistent across all versions of events: the war itself, the location, the general outcome. Don't reference specific player characters or unique choices that only happened in your playthrough.

Your character (the writer) can have opinions, experiences, and stories. They can mention traveling with companions or surviving particular dangers. Just keep it vague enough that five different adventuring groups reading the same entry can all picture themselves in that situation.

How to Write for the Guide

Every entry should answer the questions a reader actually has. If you're writing about a location, someone reading it should finish knowing where it is, why they'd go there, what threats exist, and who matters. If you're writing about an NPC, readers should know how to find them, what they want, and why they're worth knowing.

Make sure the essential information is actually there by the end.

Tagging (optional)

You can add inline tags anywhere in an entry using #ardmery, #[epeithia](/Lore/Locations/epeithia), or #vrogallan. Tags show up in the site search modal: readers can filter by one or more tags to find all pages that contain them, or type a tag name in the search box.

What Every Entry Needs (Somewhere)

You don't need to follow a template, but readers need certain information. Make sure you cover these essentials in whatever structure works for you:

For Locations:

  • Geographic position (where is this place?)
  • Key features, districts, or landmarks
  • Threats, dangers, complications
  • Important NPCs, factions, or power structures
  • Local customs or things visitors should know

For Creatures:

  • Where they're found and their habitat
  • Behavior, tactics, and how they hunt or defend themselves
  • Complete stat block (this one's negotiable)
  • How to avoid, defeat, or survive an encounter
  • Any useful parts, loot, or information they might have

For Factions:

  • What they want and how they operate
  • Who leads them and how they're organized
  • Where their power is concentrated
  • How adventurers might help, oppose, or get caught up with them
  • Their reputation and how others view them
  • Faction specific Talents for PCs aligned with them to take

For Historical Events:

  • When it happened and where
  • Who was involved and what they wanted
  • How it unfolded and what changed as a result
  • Conflicting accounts if your writer only knows part of the story

For Items:

  • What it looks like and how you'd recognize it
  • What it does (mechanical properties for MUSE clearly stated)
  • Where it might be found or who might have it
  • Any history or significance
  • Dangers or drawbacks

Length Follows Substance

A small village might only need 400 words because there's not much to say. A major city could justify 2,000 words if you're covering multiple districts, factions, and threats. Write what the subject deserves, not what a formula demands.

If you're not sure whether you've covered enough, ask yourself: "Could someone use this entry to actually interact with this place/person/thing in the game?" If yes, you're good.

Balance Story with Utility

Every paragraph should earn its space. If you're telling a story, it should reveal something about the place, person, or thing you're documenting. Entertaining readers matters, but if someone finishes your entry and still can't answer basic questions about your subject, you've prioritized style over substance too heavily.

Mechanics Are Non-Negotiable

Narrative structure has flexibility. Stats, item properties, and mechanical information do not.

If you're writing about a magic sword, a monster, a spell, or anything with game mechanics, that information needs to be clear, correct, and easy to find.

All mechanical content: - Must be designed for the MUSE Engine - Must follow MUSE balance and conventions - Will be reviewed by J.P. (and potentially a designated mechanics reviewer) - Cannot be buried in narrative paragraphs

If you're unsure about balance or how something should work mechanically, ask before writing the full entry.

The Submission Process

Step 1: Claim Your Topic

Message J.P. with what you want to write about. He'll confirm no one else is working on it and flag any major canon concerns upfront.

Step 2: Research

Read existing entries that connect to your topic. Check the canon, and know what's already established.

Step 3: Write

Use Google Docs, Ellipsus, or any shareable writing platform that supports Markdown. Give J.P. commentator or editor access. Write in whatever structure works for you, but make sure you cover the essential information readers need.

Step 4: Submit

Share the document with J.P. and let him know it's ready for review.

Step 5: Review

J.P. will respond within [7-10 days]. Expect comments about lore conflicts, missing information, mechanical errors, or structural suggestions. If you haven't heard back after [10 days], send a follow-up.

Most submissions need at least one round of revisions. This is normal and not a rejection. Common issues include:

  • Conflicts with established lore
  • Missing essential information
  • Mechanical balance problems
  • Grammatical issues
  • Clarity issues

Step 6: Revisions

Address J.P.'s feedback and resubmit. This might happen more than once for complex entries.

Step 7: Approval

Once approved, J.P. will convert your work to Markdown and publish it to the site within [3-5 days]. He'll fix typos and formatting during conversion but won't change your voice or writing style.

Step 8: Publication

You'll receive a link to the published entry. Your Ilhdeinian writer name will be credited, and the entry will be tagged appropriately.

What J.P. Will and Won't Change

He will:

  • Fix typos and grammatical errors
  • Adjust formatting for the site
  • Flag anything that contradicts canon
  • Suggest cuts if something's too long or unfocused
  • Request clarification on confusing passages
  • Correct mechanical errors or balance issues

He won't:

  • Rewrite your voice or personality
  • Change your structural approach
  • Reject entries just because they're different from what others have written
  • Make you sound like someone you're not

If J.P. says something contradicts canon, it does. Work with him, not against him. Sometimes older entries can be updated or clarified. Sometimes your idea needs adjustment. Discuss it, but understand he has final say.

Images

If you would like to add an image to your work, please send the image to J.P. as a PNG or JPG / JPEG only. Include the original artist's name and a link to that artist's profile (official portfolio/ social page where they publish their work) so the site can credit them properly. If you have a specific placement in mind for the image, say so when you forward it; otherwise J.P. will fit it where it makes sense for the guide.

Collaboration Between Writers

Co-writing an entry is allowed, encouraged, and both writers will get credit. Make sure you're working off a shared document also made available to J.P., and that your combined voices still feel like they come from distinct characters.

Featuring another writer's creation:

If Writer A created an NPC and you want to feature them in your location entry, get Writer A's permission first. Respect what they established but feel free to add new dimensions.

Contradicting another writer:

The guide allows for different perspectives, but outright contradictions need J.P.'s approval. Your character can disagree with another character's assessment, that's fine. But you can't say "the merchant guild has five members" if someone else established there are seven.

Frequently Asked Questions

What if my idea contradicts something subtle in an older entry? Talk to J.P. first. Sometimes older entries can be updated or clarified. Sometimes your idea needs adjustment. Don't assume you have to scrap it, discuss it.

Can I write about player characters? Only if you keep it adventure-agnostic. Focus on the broader situation, not specific choices or companions that only existed in your playthrough.

What if I disagree with J.P.'s feedback? Discuss it openly. But understand he has final say on canon and mechanics. If it's a dealbreaker, you might need to shelf that particular piece.

How much can I write? As much as the subject deserves. Don't pad for word count, but don't artificially limit yourself either. A complex topic needs space to breathe.

Can I update my old entries? Yes, but check with J.P. first, especially if it might affect other people's work or established canon.

What if I'm not a strong writer? You don't need to be Finley Vorden. You need to have a distinct character voice and cover the information readers need. J.P. will help with prose, clarity, and structure during the review process.

Can I write multiple entries before submitting? You can, but it's smarter to submit one, get feedback, and adjust your approach before writing ten more. First submissions usually need the most revision as you figure out what works.

What happens if two of us accidentally write about the same thing? This is why you check with J.P. before starting. If it happens anyway, he'll work with both of you to either combine efforts or differentiate the entries.

Artwork by Dean Spencer