Combat Tracker Settings not launching

I cannot launch the Settings of the Combat Tracker. I click the button but nothing happens. Suggestions? And no, the other modules are not affecting it as I disabled everything I could except the Combat Tracker.
Thank you

Hi there :wave:
The combat tracker is a built-in part of Foundry Combat Encounters | Foundry Virtual Tabletop. Are you using a specific module that extends the combat tracker that you are trying to open the settings for?

Please open your dev tools console (F12) before clicking the settings button to see if there are any error messages posted there once you click the button. If so, a screenshot of that could help give context to what’s going wrong.

Please let us know if you’re using a specific module that extends the combat tracker as well!

This is what I get:
foundry.js:655 Error: An error occurred while rendering CombatTrackerConfig 30. Cannot read properties of undefined (reading ‘Actor’)
[Detected 1 package: system:worldbuilding(0.8.2)]
at Hooks.onError (foundry.js:654:24)
at :gift:Hooks.onError#0 (libWrapper-wrapper.js:188:54)
at foundry.js:5795:13
Caused by: TypeError: Cannot read properties of undefined (reading ‘Actor’)
[Detected 1 package: system:worldbuilding(0.8.2)]
at SimpleTokenDocument.getTrackedAttributes (token.js:23:58)
at CombatTrackerConfig.getData (foundry.js:76183:53)
at CombatTrackerConfig._render (foundry.js:5838:29)
at CombatTrackerConfig._render (foundry.js:6572:17)
at CombatTrackerConfig.render (foundry.js:5793:10)
at SettingsConfig._onClickSubmenu (foundry.js:86574:16)
at HTMLButtonElement.dispatch (jquery.min.js:2:40035)
at v.handle (jquery.min.js:2:38006)

Thanks for sharing the stack trace :+1:

The bug is in the worldbuilding package, which is the Simple Worldbuilding System.

It’s tracked as an issue by the package repository over here Cannot open Combat Tracker config on v12 · Issue #65 · foundryvtt/worldbuilding · GitHub and would need to be resolved there :slight_smile:

Essentially, there is no solution. Ouch. Thanks Phi.

I’m sure there is one! Just needs to be fixed in the base package where it occurs.

Yeah I checked. It is unresolved. A shame. Anyway hopefully they will fix it in the next minor update. Thanks again Phi.