Wildcards broken in v13

Help
1

I’ve been trying for about an hour now to get wildcard tokens to work. I followed the documentation provided here Tokens | Foundry Virtual Tabletop

Even wildcard token that worked before are broken now. The only ones still working in my game are done via Too Many Tokens - Online

Is there anything I can do about it? Or am I just screwed until further updates?

1 Like
2

Yes, got the same issue. Was just debugging it because Foundry Discord does not report this as an issue, seems to be related to Forge’s interaction with Foundry

For a Image with the path:
https://assets.forge-vtt.com/*********/extra/Portraits/WolvesDogs/*.png

I get the error

foundry.mjs:23633 
Error: Error retrieving wildcard tokens. Directory https://assets.forge-vtt.com/******/extra/Portraits/WolvesDogs does not exist or is not accessible in this storage location

Note if you select a SPECIFIC art asset in that folder the Token works fine, just doesn’t like Wildcards

Version V13 Stable 2 (Build 342)

1 Like
3

Confirming the same issue and result as fashtas on the same build

4

Just out of interest sake, some wildcards work but I can’t see a pattern

If you point to “Core Data” this folder works:

icons/creatures/invertebrates/*.webp

this doesn’t

cards/backs/*.webp

Not spaces, not length, not which database, no idea so far (Not dashes in the filenames, both these examples have the same style filenames), both folders contain same types of files and both contain more than 1 file

1 Like
5

More information. Vanilla foundry seems to work fine, I got Wildcards working on anything I tried but again I got the same error with the Core Data /cards/ folder on a default Foundry setup

Seems to be some sort of V13 issue but what it is I can’t say

Edit: Default Foundry install on Local machine wildcards, no addons

  • Core Data/cards/ (Fail)
  • Core Data/ui/ (Fail)
  • Core Data/icons/ (Works fine!!!)
  • User Data - Any folder I created or already existed, (Works Fine!!!)
6

Thanks for the reports @fashtas and @rascalpanda and @ms_succubus . I’ll mark this down to look into tomorrow, since we were actually supposed to have just fixed some rather significant wildcard issues recently.

2 Likes
7

Hello,
Is there any solution/workaround to that issue ?
Thanks a lot for your dedication.

8

I want to report that i have the same issue. only “Core Data” works as fashtas said

9

Error still in latest build: v13 Stable 4 (Build 345)

10

I think that I have read somewhere on the Forge Discord that this issue would be addressed in the current (or next) sprint, but no idea about when that would be…
Some of us would be really interested to receive an update status of that issue.
Thank you again.