Conflict with Levels Module

[AurelTristen]

Foundry v12.330
D&D5e 3.3.1
Terrain Mapper 0.4.5
When Terrain Mapper and Levels (along with its prerequisites) are active, Levels no longer work properly. It seems to somehow interfere with deciding when to draw Tiles that represent higher floors. I narrowed this bug down to Terrain Mapper by disabling all modules but Levels, and turning on everything elevation-related one by one. Then I shut everything off except Levels, double checked that it was working as it should, and then activated Terrain Mapper, and the bug returned.

I see an error in the log, but it persists even with Terrain Mapper off, so I don't think it is related.

1. Create or load a map with at least 2 levels (ground level and a higher floor).
2. Add a level transition using the standard method (Drawing tools while in level edit mode).
3. Move a token into the transition. The token's altitude changes as expected, but the tile representing the next floor remains invisible.

You can work around this by deselecting your token and selecting them again, but it breaks once you change elevation once more.

I understand you can't keep this compatible with every module out there. Levels is quite popular though.

[caewok]

I cannot replicate this. Does it still happen in v0.4.6? I tried in both the Baileywiki farm scene and tried creating a new Drawing stairs. When the token takes the stairs, the token elevation changes as expected and the tile representing the floor becomes visible.

[AurelTristen]

I've updated to 0.4.6 and still have the same issue. I'm having it with scenes I've had set up and working with Levels for multiple years. This video shows what's going on. When I first ran into this issue, I tried everything I could think of with the Levels module and settings, including re-walling and setting up the scene from scratch following Baileywiki's latest video (Since Levels has changed some over the years).
Even if it is user error, Terrain Mapper appears to be changing the behavior of Levels simply by being activated.
Note that this scene has never had any Terrain Mapper features set up on it.

Worst case, I'll just avoid having sessions that use Levels and difficult terrain in one sitting. It has been very useful to automate difficult terrain, so I thank you for your work.

[Commander-Fayne]

I have this same issue. It corrects if I click the next level in the Levels UI, or change levels and go back to the one the token is on. At first I thought this was a Levels bug, as there's a similar issue reported on TheRipper93's discord, but he says that is super old and he hasn't seen issues reported where a token's view of the level doesn't update after transitioning levels.

[NdranC]

I just came here to report the same issue.
Screencast From 2024-10-02 10-36-19.webm
Here is a video showcasing the issue. That was right after enabling Terrain Mapper again. It works the first couple tries and then just stops working and remains not working until I disable the module.