search

caewok / fvtt-terrain-mapper

Paint coded terrain values on Foundry maps
MIT License
6 stars 6 forks source link

Dragging a token doesn't change elevation. Arrow key movement does. #65

Open ullantra opened 1 month ago

ullantra commented 1 month ago

Steps to reproduce:

  1. Scene is 0 elevation
  2. Make a region -inf to 0 elevation, Plateau at 0
  3. Make a region -inf to 20 elevation, Plateau at 20
  4. No behaviours

Drag the token from the 0 region to the 20 region. Hover-tooltip says "+20ft", but on releasing the mouse and the token moving, its elevation does not update.

Do the same action of moving between regions with the arrow keys: works fine.

Other modules: fuckloads, I have no idea if there's a conflict.

Screenshots (and my frustration, sorry about that) here: https://discord.com/channels/170995199584108546/513918036919713802/1294518214696505434

ullantra commented 1 month ago

Another related issue even when using keys: going from a 20 to 30 plateau doesn't work under certain situations (the 30 plateau is split over 2 areas and the problem region is the smaller of the two areas. image

gringoireDM commented 3 weeks ago

I observe exactly the same behavior. Similarly, difficult terrain does not calculate the actual movement speed if the token is dragged and dropped. Same for cliffs and water.

caewok commented 2 weeks ago

In TM v0.4.8? I cannot replicate this. But I don't know what modules you are running. If you can replicate this without modules or with 1 or 2 modules, let me know and I can look at it some more.

KLSteinwand commented 2 weeks ago

It does the same for me. Currently not home, but i can test when I get home to see if there is a module conflict going on.

KLSteinwand commented 2 weeks ago

Ran Find the Culprit! to see what was causing it on my end. PF2e Token Drag Ruler was causing it. If someone can verify that on their end, then I think we've got a better lead as to what's causing the problem.

gringoireDM commented 1 week ago

Yeap. also the D&D version of it (Drag rule) causes the problem. Removing that one fixes the issue. still it's quite a useful module to have to track player's movements. Did anyone find a fix to use both?

Thank you all.