Open InstantZzz opened 1 year ago
This is likely due to the way TokenMold overrides the data coming in when it creates a Token.
This will be handled differently in v3 of Token Mold - but for now this is indeed a bug in the way Token Mold manages token data.
When is V3 coming out if that's ok to ask?
Hello,
I am not sure if I sure label my issue as bug and I am not sure where the issue lies. I would make a post about this on their page as well but the fork (mentioned below) does not have an issue tab.
I am using FVTT v10.291 and I am running Pathfinder 2E v4.5.0 I am using Token-Hud-Wildcard v1.7.1, this is a fork of the original module as the original is not V10 compatible.
Token-Hud-Wildcard has a feature that allows the owner of a token to set a Default image for their wildcard tokens. While I have both this module (Token-Mold v2.15.4) and Token Hud Wildcard v1.7.1, my default wildcard images stop functioning. This causes my tokens to functions as normal wildcard image.