Journeyometer 2: Rivendell is live!

[Glorelendil]

Alas. I just spent some time trying to set up Valarian's map, with the idea being that it would autoload, but you could then manually load an official map if you had that available.

I got the numbers tweaked so that the hex map was at the same scale as Valarian's, but it seems like the overall layout is simply different. If, for example, Beorn's House has the same coordinates on C7 maps and Valarian's map, then Woodland Hall coordinates are different. Which means all the boundaries of the regions will be off.

So for now it's C7 maps or nothing.

Sorry.

[Morgoth]

Official maps are fine with me.

[Glorelendil]

Official maps are fine with me.

Unfortunately, it seems many folks only have the hardcopy of the maps.

[jamesrbrown]

Everything is looking good...except one last gripe. If you select both the starting hex and the ending hex and choose "Skip First Cell", the total miles are correct (according to RAW), but the dates are off. The date also skips the first cell. The work-around for this is to actually not select the starting hex when calculating the journey, while choosing "Count First Cell".

Therefore, I can't see the point in selecting the starting hex and the ending hex while choosing "Skip First Cell." Why would anyone do that?

The instructions I would give to Loremasters is to always choose "Count First Cell", but DO NOT select the hex of origin; otherwise the total miles will be off according to RAW.

Of course, if you can fix the dates to be accurate when choosing "Skip First Cell" while selecting the hex of origin, then I would instruct them to do so. In other words, the "Skip First Cell" option should be removing 10 miles from the total distance of the journey, but it shouldn't affect the speed rate. If companions were travelling by foot and left on January 1 in Easy terrain, they should still arrive two hexes from the starting hex on January 2. Right now, "Skip First Cell" has them arrive three hexes from the starting hex on January 2.

[Morgoth]

James, I think that is how it is supposed to work, isn't it? Selecting 10 hexes and counting the first hex, or selecting 11 hexes and skipping the first hex puts you in the same place at the same time. Isn't that how it's supposed to work, or am I misunderstanding?

[jamesrbrown]

Ok, take a look at this screenshot:



I have chosen a journey from Beorn's House to the Eagles' Eyrie. I have selected both the starting hex and the ending hex. I have also chosen "Skip First Cell".

You cannot see it this shot, but the Total Distance calculated is 50 miles. This is correct, because even though there are 6 hexes selected, only 5 of them count for distance according to the RAW and the reason why I selected "Skip First Cell". Otherwise, it would have counted all 6 hexes in the Total Distance = 60 miles.

However, when looking at the dates, it says that you arrive on the third hex from Beorn's House on January 2, rather than 2 hexes away. By choosing "Skip First Cell", the app placed the January 1 date on the cell after Beorn's House and calculated 20 miles from that before labeling January 2. To be accurate, it still needs to count the hex of Beorn's House as January 1 and label 2 hexes away as January 2. Therefore, the "Skip First Cell" option should not affect the speed of travel, which is how the dates are calculated.

Like I said, however, the work-around is to choose "Count First Cell" but do not select the starting hex. Then, everything is accurate.

[jamesrbrown]

Actually, let me change my comments. If you do not choose the starting hex, everything is still messed up. The only way to get everything accurate is to leave out the ending hex (which is backwards IMHO).

Here's what you have to do to be accurate:

[jamesrbrown]

The last screen shot shows the company arriving at the Eagles' Eyrie late in the day on January 3rd.

[Glorelendil]

Will have to be a quick reply because the car is loaded up and we're about to head to the mountains for the weekend.

James, I think it's working correctly, but maybe my language and metaphors are confusing. In your example screen shot, if you highlight the final hex you will still be arriving January 3rd. The first two hexes are traveled on Jan 1st, the 3rd and 4th hexes on Jan 2nd, and the final hex January 3rd, but you are only traveling half a day.

That's to include the first hex, which you have selected. If you...

Oh, wait...I think I understand the problem. You are reading the tooltips to mean instructions for the LM. They are instructions for the computer, not the human. So if you want to count both beginning and ending hexes, you select "Count First Cell". If you want RAW, you select "Skip First Cell" but you still select start and end cells on the screen.

Does that make sense?

[Valarian]

Alas. I just spent some time trying to set up Valarian's map, with the idea being that it would autoload, but you could then manually load an official map if you had that available.

I got the numbers tweaked so that the hex map was at the same scale as Valarian's, but it seems like the overall layout is simply different. If, for example, Beorn's House has the same coordinates on C7 maps and Valarian's map, then Woodland Hall coordinates are different. Which means all the boundaries of the regions will be off.

So for now it's C7 maps or nothing.

Sorry.

I can try to fix that. My maps are based on the maps in the books (I think done by Christopher Tolkien). They're a little different. They don't have the Haunted Hills for instance. Changing the locations means that won't be quite the same as the books ones, but if we can use them for this it's possibly worth doing that.