Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Status effects no longer appear on the token status context menu #570

Closed
Project39 opened this issue Jul 14, 2023 · 5 comments
Closed
Labels
bug Something isn't working

Comments

@Project39
Copy link

Describe the bug
Since update V1.5.5 status effects no longer appear in the status right click menu on tokens

Expected behavior
In previous versions all the status options were displayed in that context menu

Screenshots
image

Platform (please complete the following information):

  • OS: Windows
  • Browser: Running from the foundry VTT window on the host machine
  • Foundry version: 10.303
  • Lancer system version: 1.5.5

Additional context
I spun up an entirely new world to confirm it wasn't just an issue with the world I had before the 1.5.5 update, in my old world the burning and overshield status effects are still in the menu but nothing else.

The new world has no modules installed other than the lancer core system.

The status/condition compendium entry does have all the statuses I'd expect to be there

Discord contact info
Prezo

@Project39 Project39 added bug Something isn't working triage To be assessed by maintainer labels Jul 14, 2023
@MaxPelly
Copy link

same here, just updated a world now only have burn and overshield

@sirbayer
Copy link

Similar issue where the default Foundry status icons are missing. All others are working fine, it looks like.

@MaxPelly
Copy link

anyone know if the 1.6 bump fixed this?

@Eranziel
Copy link
Owner

Sorry I missed this before I put out 1.6.0! I'll release a fix soon that enables the defaults if no icon sets are selected.

@Eranziel Eranziel removed the triage To be assessed by maintainer label Jul 16, 2023
@sirbayer
Copy link

Does that fix also resolve the issue of the defaults not appearing when configured on while others are also enabled?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants