M.A. (Mana)

As I mentioned before, I'm not the mapper. I tried to get hold of the DD map, but couldn't. Anyway, I squinted around at the map I have ready access...

This probably relates to some PF1 conditions being renamed to have pf1_ prefix. The old names apparently were causing conflicts with core Foundry or something?  Edit: Except those are...

~~The ray distance also always seems to be 100 no matter how far you measure.~~ This was some other problem with my test case.

Measure info module: Tho if you make it async when the base Foundry functionality is not, it's going to break even more things. If you do that however, you better...

Fake result would still make it essentially break compatibility, since although it won't make my module produce NaN display, it will still not work at all, so the conflict persists...

> systems should use the public getRelatedObject This doesn't work since the functions that it is needed in are not async, namely the `title` getter, same for `isTitleVisible()` function, nor...

If the default is inferring on receiving end, yes, that sounds good to me. The optional name override is good for sharing character images tho it would be good to...

Win11, that doesn't matter for route prefix problem. Also seen here with the panicked with the image path being broken due to it:  ^ I can fix that by...

Ref: Fill in routePrefix in `options.json` and use the electron client to easily test how route prefix changes things.

I needed to add `distance: canvas.grid.distance` to the grid init options to the proposed solution for it to work correctly. Ugly solution, but it works 🤷🏻 Still wish for the...