Describe the bug
I've been unable to use the 'e' key to open and close doors while in range with a token, I see the below error in the console log. I have tested this on a newly created world with just Arms Reach and Lib Wrapper activated, both up to date as of 25/11/2021. When logged in a GM or player upon having a token selected being next to a door, the 'e' key will do nothing to open or close it, and the console will report an error. Additionally, when the selected token is outside of the maximum interaction distance, I do get notified that no door was in -token-'s reach.
To Reproduce
Steps to reproduce the behavior:
Go to a FoundryVTT canvas
Create a token and a door, placing the token next to the door
Press the 'e' key with door selected
Nothing will happen, and console will produce the error
Expected behavior
The door should open, or close.
Screenshots
Browser:
Google Chrome
FoundryVTT application
Foundry Version:
0.8.9
Game System:
Simple World-Building, but also experience error with the DnD5e system
Additional context
This has been tried with a multitude of different settings, such as owned tokens/unowned tokens, active scenes, inactive scenes, freshly created worlds, different configured settings alongside default settings
Module Version: v2.1.4
Describe the bug I've been unable to use the 'e' key to open and close doors while in range with a token, I see the below error in the console log. I have tested this on a newly created world with just Arms Reach and Lib Wrapper activated, both up to date as of 25/11/2021. When logged in a GM or player upon having a token selected being next to a door, the 'e' key will do nothing to open or close it, and the console will report an error. Additionally, when the selected token is outside of the maximum interaction distance, I do get notified that no door was in -token-'s reach.
To Reproduce Steps to reproduce the behavior:
Expected behavior The door should open, or close.
Screenshots
Browser:
Foundry Version: 0.8.9
Game System: Simple World-Building, but also experience error with the DnD5e system
Additional context This has been tried with a multitude of different settings, such as owned tokens/unowned tokens, active scenes, inactive scenes, freshly created worlds, different configured settings alongside default settings