On the other axis would be a score combining Advantages gained by the characters in their Lore Test made before the Journey with the Eye of Mordor score.
On one axis you'd have the number of hexes travelled in the region (modified by season and means of transportation). I'd have one table per region (West Anduin Vales, East Middle Vale, etc.). The big advantage is that the Terrain difficulty (for speed of travel) and Region (for Fatigue TN) would be taken into account in the table entries. Yes, there's a cost (the number of pages in the core book that have to be dedicated to the traveling tables), but the gain in speed while playing would be immense for players. The first suggestion that comes to my mind is building tables that players and LM can consult instead of relying on multiple formulas that are not that simple and fast to use. It's imperative that the process be simplified. Considering it's one of the main themes and mechanics of the game, it is problematic to say the least. That stoppage time became such a burden that players ended up dreading the simple fact of having to travel in game. Sometimes, the game came to a full stop while I (As LM) was frantically calculating everyhting according to the path chosen by the players. Some of these steps require multiple things to be done.
The Journey Resolution consists of five steps.
0 kommentar(er)
