-
Notifications
You must be signed in to change notification settings - Fork 25
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
Compatibility issue with Automated Animations #117
Comments
the root cause of this is possibly: #118 |
Can you re-test with v2.2.5? If it was related, it should be fixed now. |
Thanks again for your work on this! So it isn't 100% fixed, but it is partially fixed and the behavior has changed, so it's definitely related to the changes you made somehow. To sum up, here is how Automated Animations behaves:
Weapons still work as they should, as they did before, and Talents now work as well! Meaning that talents with associated damage rolls do play an animation on the attack roll, with Automated Animations set to "play animation on roll attack." Spells, however, still behave the same way as they did before, as described above. So somehow the patch fixed the issue with Talents but not with Spells |
Fixed by PR #672 in Automated Animations repo. |
There's currently an issue with triggering animations from the very popular Automated Animations module (https://foundryvtt.com/packages/autoanimations) when it is set to play animations on attack rolls and not damage rolls. Details are in the link below, the dev there is working on it but indicated he needed help from someone with insider knowledge of the SotDL system
https://github.com/otigon/automated-jb2a-animations/issues/541
The text was updated successfully, but these errors were encountered: