Aedif / TokenVariants

GNU General Public License v3.0
17 stars 12 forks source link

Bizarre issue with Custom Config Token Variant not working with "{ }" file paths #151

Closed Foundry37 closed 3 months ago

Foundry37 commented 3 months ago

Hello,

So I use a folder called "{Spirits}" to keep some of my token art in (for spirit versions of the normal FA tokens), but for some reason while I can Shift-Left-Click in the Token HUD selection to have normal tokens enact a custom config for things like scale or opacity, when I try to use any token from the "{Spirits}" folder it refuses to display any custom changes to it.

To Reproduce Steps to reproduce the behavior:

  1. Name a folder "{Spirits}" - likely just the {}'s are the issue.
  2. Stick some normal tokens that accept custom config changes in there.
  3. Open the Token HUD selection for variants.
  4. Shift-Left-Click the variant that's in a folder called "{Spirits}" and try to add any change to it.
  5. Observe that it doesn't seem to display any of those changes no matter how you refresh or click on and off with another token variant.
  6. Rename the "{Spirits}" folder to just "Spirits" without the brackets.
  7. Now doing a custom config change on that token variant should work just fine.

Expected behavior I have no idea why the {}'s in a file path for a variant token art would stop something so specific from occurring.

Screenshots TVA Issue

Desktop (please complete the following information):

Additional context Honestly lucky I managed to figure out vaguely why this is happening, it confused me a great deal. While for now it's easy to just rename my folders with a {} in them, I'm confused why it's happening in the first place.

Aedif commented 3 months ago

Should be fixed in 4.64.2