Lord of Mysteries guild guide: Pathways, versions, and group goals

Lord of Mysteries brings an established fictional world into a game. Familiarity with the novels is valuable context, but it does not prove that a playable Pathway has a particular ability, role, or progression requirement. Plan your group from the current game version.

Identify the release your members play

Put the region, server, client language, and version in recruitment. Link the appropriate current game announcement. Do not treat regional availability or access to one test as a promise of access elsewhere.

Ask applicants for their character, current Pathway choice, preferred group responsibility, play times, and actual experience with the content you plan. Keep lore discussion separate from practical readiness questions.

Record confirmed plans and open choices

Members can have a firm character plan, an experimental choice, or no decision yet. Label those honestly. Officers should not construct a progression roster around a rumored role or a character the player has not committed to preparing.

For a first learning session, ask each participant what they can demonstrate in the current client. Turn observed strengths into assignments. If a role assumption fails, revise the plan without pretending the novel’s description settles the gameplay question.

Keep group invitations specific

Name the activity, current entry requirement, meeting time, expected duration, and the leader responsible for the briefing. Verify group capacity in game. Separate exploration sessions from organized progression so members know whether the group will stop for discoveries or push an objective.

Explain how substitutes are called and what preparation they need. An available reserve is only useful if they can enter the same content.

Agree on rewards only where assignment exists

Check whether rewards are personal, shared, or assignable before choosing a loot policy. Points should document a real guild agreement, not imply that officers can redistribute something the game locks to a player.

After the session, keep a short note of the next target and what actually worked. Mark test-specific observations with the version so later recruits can distinguish useful experience from obsolete assumptions.

Put the plan into practice

Keep your roster, event commitments, and decisions together with Guild Manager’s guild tools. For Discord setup and participation checks, read the command guide and voice attendance guide.

Browse all Lord of Mysteries guides.

Sources

• The franchise’s licensed-game announcement. Use the publisher or server operator’s current information for mechanics and access rules.
• Guild Manager features. The planning recommendations above are our editorial advice, not publisher requirements.

Published October 5, 2026. Check the edition, region, and current patch before applying game-specific rules.