Hexmancer Notes (Optional Appendix)
System: Hexmancer v1.2 Author: Martin Ralya (Traverse Fantasy) Status: Optional hexcrawl supplement - NOT core to WH
Why Hexmancer Isn’t Core to Western Horizon
The Fundamental Mismatch
Hexmancer’s model: Players wander hex-by-hex, generating terrain procedurally
Western Horizon’s model: Players declare destinations, DM preps that specific location
WH doesn’t need procedural hex generation because:
- Players post quest intent, not “we wander northwest”
- Travel is often abstracted
- Content focuses on destinations, not journey
When Hexmancer MIGHT Be Useful
Limited Use Cases
Hexcrawl Mode (Optional): If your table wants detailed exploration where the journey IS the content.
Random Waypoint Seeding: Use the d20 feature table to quickly generate discoveries during travel. Wizard tower (11-12), Temple (13-14), Castle (15-17) become waypoints. Hand off to Street Magic for detailing.
What Western Horizon Actually Needs Instead
See 03 - Wilderness for the destination-focused travel system:
- Complications table (d20)
- Waypoints table (d12)
- Encounters table (d12)
- Weather table (d12)
Recommendation
Move Hexmancer to Appendix B with note:
“Most Western Horizon campaigns focus on quest destinations rather than hex-by-hex exploration. If your table prefers detailed wilderness hexcrawling, use these Hexmancer procedures.”
Hexmancer Tables (Appendix Only)
Three-dice method:
- d30: Terrain generation (influenced by adjacent hex)
- d24: Feature presence (by region type)
- d20: Feature type (ruins, roads, structures, villages)
Plus special rules for byways and waterways spanning multiple hexes.