p4535992 / foundryvtt-arms-reach

FoundryVTT Door little Utilities, Arms Reach for door
MIT License
3 stars 4 forks source link

Module does not show in module settings and seems to do nothing when activated #27

Closed KammaKhazi closed 2 years ago

KammaKhazi commented 2 years ago

Environment Details

Issue Description

Hi bit of a strange one here... I have just tried to switch from the old version of the previous module (Arms Reach v1.1.1), I disabled it and then uninstalled it. Then installed "Foundry VTT Arms Reach" v2.0.10, restarted server and activated it. But the new module doesn't show at all under my module settings and doesn't do anything for me or on my player test account. Any ideas? I've rolled back to the previous module and it works fine (but obviously I'm a bit concerned with compatibility issues with that one)

p4535992 commented 2 years ago

It is a known bug of the passage from version 1.XX to 2.XX, due to my mistake during development, the best solution is to take the "settings.db" file of your world and remove the setting related to this module . Then reinstall the module and everything should be fine.

KammaKhazi commented 2 years ago

ok thank you, I'll give that a go cheers.

BigMacDJ commented 2 years ago

Environment Details Foundry VTT Version: 0.8.9 Operating System: Windows 10 64bit How Are You Using Foundry: (Hosted on Forge) Which Game System: PF2E Modules Enabled?: yes (including drag-ruler v1.8.2, Libwrapper v1.10.6.0)

Issue Description

Having the same issue. Foundry VTT Arms Reach" v2.0.10, when active doesn't show up.

p4535992 commented 2 years ago

Environment Details Foundry VTT Version: 0.8.9 Operating System: Windows 10 64bit How Are You Using Foundry: (Hosted on Forge) Which Game System: PF2E Modules Enabled?: yes (including drag-ruler v1.8.2, Libwrapper v1.10.6.0)

Issue Description

Having the same issue. Foundry VTT Arms Reach" v2.0.10, when active doesn't show up.

If you have upgraded from 1.X.X to 2.X.X the solution should be the same as described for KammaKhazi. Otherwise I would not really know why in my tests it works check the webconsole for any errors.

JonathanAlumbaugh commented 2 years ago

This fixed the error I was getting before, and the module works for clicks now (also awesome module, really love the experience it gives!). Now I get a new error when trying to use the e hotkey, should I open a new issue for this?

image

p4535992 commented 2 years ago

No need (but yes for the future is preferable) for a new issue, i will fix this weekend sorry for the trouble

p4535992 commented 2 years ago

This fixed the error I was getting before, and the module works for clicks now (also awesome module, really love the experience it gives!). Now I get a new error when trying to use the e hotkey, should I open a new issue for this?

image

This specific bug should be fixed with 2.012 try out and le me know