-
Notifications
You must be signed in to change notification settings - Fork 7
Comparing changes
Open a pull request
base repository: caewok/fvtt-terrain-mapper
base: 0.4.7
head repository: caewok/fvtt-terrain-mapper
compare: main
- 17 commits
- 7 files changed
- 1 contributor
Commits on Oct 6, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 48be3e4 - Browse repository at this point
Copy the full SHA 48be3e4View commit details
Commits on Oct 10, 2024
-
Configuration menu - View commit details
-
Copy full SHA for c771056 - Browse repository at this point
Copy the full SHA c771056View commit details -
🐛 fix|Plateau|Holes causing the cutaway path to fall through floor
Scene floor not getting added correctly in ElevationHandler._cutaway. Adjust how inside was getting counted when starting in a hole.
Configuration menu - View commit details
-
Copy full SHA for fd7b47d - Browse repository at this point
Copy the full SHA fd7b47dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 341d046 - Browse repository at this point
Copy the full SHA 341d046View commit details -
Configuration menu - View commit details
-
Copy full SHA for c7e745d - Browse repository at this point
Copy the full SHA c7e745dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 76b94e3 - Browse repository at this point
Copy the full SHA 76b94e3View commit details -
Configuration menu - View commit details
-
Copy full SHA for ae7787a - Browse repository at this point
Copy the full SHA ae7787aView commit details
Commits on Nov 4, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 7cde817 - Browse repository at this point
Copy the full SHA 7cde817View commit details -
🐛 fix|RegionHoles|Elevation falling to large negative
When moving token into and out of hole in one movement, the elevation drops to large negative and then back. The scene floor polygon was not getting constructed correctly for that situation.
Configuration menu - View commit details
-
Copy full SHA for cbe0714 - Browse repository at this point
Copy the full SHA cbe0714View commit details -
🐛 fix|Steps|Token elevation not syncing with step
Caused by two issues: 1. Steps not always capturing the start and end elevations correctly in the cutaway. 2. Duplicate points in the cutaway polygon screwing up the walk algorithm.
Configuration menu - View commit details
-
Copy full SHA for 6073f84 - Browse repository at this point
Copy the full SHA 6073f84View commit details -
💡 refactor|Steps|Steps overlay confusing with the directions
Change to use ramping straight lines from smaller to larger. Not perfect, b/c the stripes are still weird in some instances. But better.
Configuration menu - View commit details
-
Copy full SHA for ff73a95 - Browse repository at this point
Copy the full SHA ff73a95View commit details -
Configuration menu - View commit details
-
Copy full SHA for 81e32cd - Browse repository at this point
Copy the full SHA 81e32cdView commit details -
🐛 fix|Teleport|Teleporting into elevated region does not set elevation
Cannot set elevation using region segment movement, b/c the token elevation is already set by then. Instead, catch it in preUpdateToken hook. Somewhat undefined if multiple regions cover the area in which is teleported.
Configuration menu - View commit details
-
Copy full SHA for 89c9232 - Browse repository at this point
Copy the full SHA 89c9232View commit details -
Configuration menu - View commit details
-
Copy full SHA for f3685ee - Browse repository at this point
Copy the full SHA f3685eeView commit details -
Configuration menu - View commit details
-
Copy full SHA for 2803b68 - Browse repository at this point
Copy the full SHA 2803b68View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2424040 - Browse repository at this point
Copy the full SHA 2424040View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1d36431 - Browse repository at this point
Copy the full SHA 1d36431View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 0.4.7...main