PDA

View Full Version : Token Images Disappearing When Placed on Combat Tracker



Punky2129
March 26th, 2022, 19:44
When making an encounter using the table, I am able to place a token on the map just fine. This token has the image and everything on it. However, when I go to add the encounter to the combat tracker, the image on the token just disappears. Just showing up as a letter of the creature's name. This is a new issue for me, and can't seem to find a reason why or a solution.

Any help would be greatly appreciated!

Zacchaeus
March 26th, 2022, 20:55
I'll need to investigate that. Or at least one of the devs will have to. I can't immediately see what the problem is, but I can reproduce it.

This is only happening with encounters from Xanathar right?

Punky2129
March 26th, 2022, 21:10
I'll quickly run through and check from other sourcebooks and get back to you!

Punky2129
March 26th, 2022, 21:18
Of the encounters I have, the one's from Volo's and Mordenkainen's both show the same problem.

Trying a couple of things, it specifically seems to be the encounters that come with the books.

I made my own encounter, with tokens made myself and ones from the books and they worked as intended. The image appearing with the token on the tracker and not just the letter placeholder.

Zacchaeus
March 26th, 2022, 21:30
Yes, the issue is with the NPCs being pulled in from the Monster Manual. This should also pull in the token but somehow the token is not getting pulled in to the Combat Tracker; so the CT thinks there's no token and therefore defaults it to a letter token. I've alerted the developer but I think he's on holiday this week so it may be a few days before he can get a look at it.

Punky2129
March 26th, 2022, 21:37
Understandable!
Something I came across by sheer coincidence messing around with things.

As long as things still work as intended when making them myself, then no big problem!

Moon Wizard
March 28th, 2022, 00:56
It appears that this has been around for quite a while. It will require a client update to resolve, since it has to do with a specific kind of data used in those modules interacting with a specific API. I'll include in the next client update.

Regards,
JPG