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

Actor transformation does not override the Token Ring configuration of transformed tokens in V12 #3743

Closed
dev7355608 opened this issue Jun 17, 2024 · 1 comment · Fixed by #3744
Assignees
Labels
bug Functionality which is not working as intended
Milestone

Comments

@dev7355608
Copy link
Contributor

Originally reported by nonchalantwombat: https://discord.com/channels/170995199584108546/1184176415139184731/1251140525831229531

ALL MODULES DISABLED? true
OS, Hosting, Browser (if applicable): Windows 11, Hosting locally with Foundry client, Foundry v12.
Short Description of bug: When using polymorph/token shapeshifting, the custom scaling and dynamic token ring fails to transfer
Simple steps to reproduce the bug: Make two actors with different sizes, art, and scaled dynamic tokens. Polymorph/wildshape one into the other. The dynamic token ring will scale incorrectly, and not be the size of the intended prototype token, instead retaining the initial token's settings.

@dev7355608 dev7355608 added the bug Functionality which is not working as intended label Jun 17, 2024
@dev7355608 dev7355608 self-assigned this Jun 17, 2024
@unsoluble
Copy link

Does this PR also address this 3.2.1 behaviour? If you have a DTR Subject Path set for a token, then as the transformation completes, this original subject path pops back onto the token (it should not).
https://github.com/foundryvtt/dnd5e/assets/801582/443bc558-7ff0-466d-a316-98602fd86130

@dev7355608 dev7355608 added this to the D&D5E 3.3.0 milestone Jun 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Functionality which is not working as intended
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants