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

[KammaKhazi]

Environment Details

• Foundry VTT Version: 0.8.9
• Operating System: Windows 10 64bit
• How Are You Using Foundry: Chrome Browser as GM permission user (Hosted on Forge)
• Which Game System: dnd5e
• Modules Enabled?: yes (including drag-ruler v1.8.2, Libwrapper v1.10.6.0)

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]

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]

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

[BigMacDJ]

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]

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]

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?

[p4535992]

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

[p4535992]

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?

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