search

caelwarner / DarknessActivatedTiles

Allows tiles to be hidden when the scene's darkness level is outside a customizable range. Much like lights and sounds.
MIT License
3 stars 1 forks source link

Darkness Activation Range option not present #1

Closed Tronikart closed 3 years ago

Tronikart commented 3 years ago

Hi! Was wondering if this was a known issue but I can't see the options at all.

Tried it with no other mods on and no luck, I initially installed it through Foundry's built-in module browser, removed it and manually installed it with the provided Manifest URL and still nothing.

I'm running Foundry 0.8.8, if there's something I'd need to provide proof or help with debugging I'd be happy to oblige

caelwarner commented 3 years ago

Oh my, I'm so sorry that I took almost 2 weeks to respond. I was on vacation. I'll look into this now

caelwarner commented 3 years ago

Just to rule it out, did you enable the module? Also are you looking at the Basic tab in the tiles config menu? Finally, could you open the console (press F12) and check two things:

  1. Search for "Darkness Activated Tiles | Loaded" and check that has been printed to the console
  2. Check for any errors that come up when you open the tile config menu

Thanks

Tronikart commented 3 years ago

Yes I did enable the module, yes I'm looking in the Basic tab.

The only message in console that has anything related to the module is Foundry loading the localization file, other than that there's nothing

Foundry VTT | Loaded localization file modules/darkness-activated-tiles/lang/en.json

I'm doing this in a D&D5e - Fifth Edition System 1.3.6 room that has Tidy UI - Game Settings, Spellarena Battlemap Collection, and Darkness Activated Tiles, as activated modules, every module updated to work on 0.8.8

Screenshot_1

Screenshot_2

Screenshot_3

Hopp3r commented 3 years ago

Aren't you missing your js file from module.zip?

caelwarner commented 3 years ago

Yea, looks like I was missing it. The workflow I was using to zip the module only included specific files and folders, and module.js wasn't one of them. Anyways, it should be fixed in v0.2.0.