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. Pick an Ilhdeinian name, then decide who this 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? A skeptical scholar tired of Finley's embellishments? 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. The guide works because it's messy and full of personalities that sometimes contradict each other.
The Canon Rule
For anyone looking to expand Ilhdeinia, its important first and foremost to 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).
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, only when there's a compelling reason that J.P. approves.
What’s more, before starting any piece, check with J.P. so two writers don't accidentally develop the same location, character, or concept at the same time.
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 their’s.
When you write for the guide, focus on what's consistent across all versions of events, for example: 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, sure. 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.
Technical Requirements
All materials should be submitted through a shareable online platform such as Google Docs, Ellipsus, etc.
Format your work with clear structure. Use headers, markdown, whatever helps organize information logically. The guide should be easy to navigate while still feeling like a collection of travel journals rather than a sterile reference manual.
Include your Ilhdeinian author name prominently. Readers should know whose perspective they're getting.
Style Considerations
- Once you establish your character's personality, maintain it across all your contributions. If you write five entries and they all sound like different people, something's wrong.
- Ilhdeinia was built for the MUSE Engine. If your submission includes mechanical elements, they must be for MUSE, and adhere to its balance and conventions. When in doubt, ask for help.
- Yes, this is a guide that helps adventurers navigate Ilhdeinia. But readers should enjoy the journey as much as the destination. Balance useful details with entertaining narrative. A warning about dangerous terrain can mention the friend you lost there. A tavern recommendation can include the story of why you're no longer welcome at the establishment next door.
- The guide exists partly because Finley Vorden is charming enough to market his mishaps. Your character doesn't need to be funny, but self-awareness goes a long way. Acknowledge failures. Admit when you barely escaped. Let readers laugh with you or at you.
- Don't write like an omniscient narrator. Write like someone who put in the effort to learn things, who has gaps in their knowledge, who might be wrong about some details but is sharing what they genuinely believe based on what they've lived through.
What Not to Do
- Don't write dry encyclopedia entries
- Don't ignore your character. Generic, voiceless writing doesn't belong here.
- Don't skimp on the research. Read what exists before adding to it. Know the world you're contributing to.
- Don't treat J.P.'s feedback as optional. If he says something contradicts canon, it does. Work with him, not against him.