Artwork by Dean Spencer

Submission Guidelines¶

Ilhdeinia will never be complete. I know this already, and going into this you should too.

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

But before we get into the business of creating for Ilhdeinia, allow me to lay out a few requirements:

1. You should know J.P. Sariz, and be in contact with him regarding what you would like to create. As the creator of the world, and the keeper of its lore, he'll be the first to tell you if something fits like a glove, or breaks established canon. The day of tomorrow he's not here, that'll change, but for the time being, he's to be consulted.

2. It's recommended that you have played in at least one Ilhdeinian game (whether that be a simple one-shot or sprawling campaign) before attempting to add to the world. Take a stroll in Cehdale, start a fight in Reathien, pick wild turnips in Persephe. Get to know the world before you expand it.

3. Familiarize yourself with the existing wiki. You don't need to know every page, but a basic understanding of Ilhdeinia is essential.

If you meet the requirements above, and are ready to begin, there's no better place to start than picking an Ilhdeinian name. This will be the in-universe name you write under, a co-conspirator with Finley Vorden (J.P. Sariz's in-universe pen name). Decide who this person is, as their personality should shine in your articles. Maybe you're a cautious cartographer, or maybe a reckless thrill-seeker. Your character should have a voice distinct enough that readers could tell your entries apart from others without seeing your name.

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 it against existing NPCs or ask J.P. Once you pick a name, stick with it across all your contributions.

Ilhdeinia was the reason the MUSE Engine came into existence, and as such, it is the only system that will be natively supported by this wiki. All submissions made to this site that will require mechanics should be built for the MUSE Engine. If you're unsure about balance or how something should work mechanically, ask J.P.

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

Respect What Came Before¶

As referenced above, J.P. Sariz is the steward of all canon, and every submission requires his approval. When sending documents his way, please afford J.P. Commentator or Editor access. He'll never change your words, but he'll flag anything that breaks established lore, or needs further refinement.

Before you start writing, make sure that what you're interested in has not already been covered by the wiki. It's also recommended to search for any mentions of Locations, Factions, or NPCs that connect to what you are planning. Once you've done so, let J.P. know the topic you plan to cover so he can add it to the Writing Tracker.

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

Adventure Agnosticism¶

Different adventuring parties experience Ilhdeinia differently. Maybe yours fought in the War of the Sisters, but its just as likely another party did too. Their companions aren't yours, and your decisions aren't theirs.

As such, 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 can read 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 what they want, what they look like, and why they're worth knowing.

You can add inline tags to the YAML at the top of an entry, such as #Location, #Event, or #Character. Tags show up in the site search modal, allowing readers to find what they are looking for easily.

What Every Entry Needs (Somewhere)¶

You don't need to follow this as a template, but the following should be present in any entry covering any of the following:

For Locations:

• Geographic Position (I mean, where is it?)
• Key Features, Districts, or Landmarks
• Important NPCs, Factions, and/or Power Structures
• Local customs or things visitors should know

For Creatures:

• Where they're found/ their habitat
• Behavior, tactics, and how they hunt or defend themselves
• Complete Stat Block (for the MUSE Engine)
• Any useful Part(s), 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

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

While the above should be covered, a small village might only need 300 words because there's not much to say; whereas a major city could easily hit 10,000 words if you're covering multiple districts, factions, and threats. Write what the subject deserves, not what the formula above demands.

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

No AI Writing or Images¶

AI-generated text and images are not allowed in submissions, and any entry found to contain them will be returned for revision/ overhauling rewrite before the review process can properly begin.

Feel free to use tools to check your spelling, grammar, etc., but we draw the line at generative work. If a language model wrote your sentences or produced your artwork, it doesn't belong here. If you can't be bothered to write it, we shouldn't be bothered to read it.

The same applies to images. Every piece of art on this site is credited to a living artist. See the Images section below for how to submit artwork properly.

If you're struggling with prose, J.P. can help during the review process. That's what the revision rounds are for.

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. 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.

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

Step 3: Write Use Ellipsus, Obsidian (if you've been given vault access), or any shareable writing platform that supports Markdown, and give J.P. commentator or editor access.

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.

Step 8: Publication You'll receive a link to the published entry. Your Ilhdeinian writer name will be credited.

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, etc., provided it exists) 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 a new entry is not just allowed but 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 your respective 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.

Obsidian Access¶

Frequent contributors in good standing with J.P. will be given access to the local Obsidian vault for Ilhdeinia. All writing and work for this project is done from within this local vault, and access will give you the ability to directly edit files within the wiki.

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 shelve 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, and something small doesn't warrant a novel.

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! All this site requires is a distinct vision and character voice. J.P. can 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.