Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when terrain mapper is not active #115

Closed
caewok opened this issue Jul 1, 2024 · 2 comments
Closed

Error when terrain mapper is not active #115

caewok opened this issue Jul 1, 2024 · 2 comments

Comments

@caewok
Copy link
Owner

caewok commented Jul 1, 2024

https://ptb.discord.com/channels/915186263609454632/1193755370607345695/1257140842846752849

Uncaught Error: undefined. Flag scope "terrainmapper" is not valid or not currently active
[Detected 3 packages: elevationruler, lib-wrapper, aedifs-tactical-grid]
at Scene.getFlag (foundry-esm.js:11771:44)
at Ruler._addWaypoint (Ruler.js:157:70)

@Someone2345
Copy link

Someone2345 commented Jul 1, 2024

Yup - it acts the same as the 107 issues.

(I was going to add this as a new bug, but I see that it has already been noted)

Hi, I am afraid that the issues caused by switching to the measure distance tools (as per 107) are still in effect after updating.

It looks like the main cause may now be "flag scop terrian mapper".
Same actions to replicate as before - switch from dragging token using the token select tool to the measure distance tool and all token actions effectively break.
There is a new error message in the console.

image

Not tested with no other modules yet.
FVTT v12.328
D&D5e 3.2.1
[Releases 0.9.6)

[Confirmed that if terrainmapper module is added, then the error is resolved.]

@caewok
Copy link
Owner Author

caewok commented Jul 3, 2024

Fixed in v0.9.7

@caewok caewok closed this as completed Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants