p4535992 / conditional-visibility

a FoundryVTT module to hide tokens from some players, but not from others
MIT License
5 stars 8 forks source link

[BUG] Console error on startup #7

Closed dmrickey closed 2 years ago

dmrickey commented 2 years ago

Module Version: v0.3.2 image image

Describe the bug Error in console on startup

ConditionalVisibility.js:158 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'restrictVisibility')
[Detected 1 package: conditional-visibility]
    at new ConditionalVisibility (ConditionalVisibility.js:158:55)
    at Function.initialize (ConditionalVisibility.js:306:42)
    at readyHooks (Hooks.js:23:27)
    at conditional-visibility.js:67:5
    at Function._call (foundry.js:294:14)
    at Function.callAll (foundry.js:253:12)
    at Game.setupGame (foundry.js:5547:11)
    at async Game._initializeGameView (foundry.js:6479:5)
    at async Game.initialize (foundry.js:5415:5)

To Reproduce Steps to reproduce the behavior:

  1. Start a world in pf1
  2. observe error in console
    • I have a scene configured and active as well

Expected behavior I don't know if this error is benign or important or not. I haven't configured anything yet and haven't yet tried.

Screenshots If applicable, add screenshots to help explain your problem.

Browser: chrome 97.0.4692.71

Foundry Version: 9 242

Game System: pf1 0.80.4

dmrickey commented 2 years ago

Now I'm getting this one

ConditionalVisibility.js:179 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'testVisibility')
[Detected 1 package: conditional-visibility]
    at new ConditionalVisibility (ConditionalVisibility.js:179)
    at Function.initialize (ConditionalVisibility.js:311)
    at readyHooks (Hooks.js:24)
    at conditional-visibility.js:68
    at Function._call (foundry.js:294)
    at Function.callAll (foundry.js:253)
    at Game.setupGame (foundry.js:5547)
    at async Game._initializeGameView (foundry.js:6479)
    at async Game.initialize (foundry.js:5415)
p4535992 commented 2 years ago

This issue is closed, because the new series 0.4.X is just to different, checkout the last version of the module.