generated from League-of-Foundry-Developers/FoundryVTT-Module-Template
-
Notifications
You must be signed in to change notification settings - Fork 26
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
[BUG] "stretchTo" breaks looping via "persist" #269
Comments
Codas
added a commit
to Codas/FoundryVTT-Sequencer
that referenced
this issue
Jul 23, 2024
Codas
added a commit
to Codas/FoundryVTT-Sequencer
that referenced
this issue
Jul 23, 2024
Codas
added a commit
to Codas/FoundryVTT-Sequencer
that referenced
this issue
Jul 23, 2024
Codas
added a commit
to Codas/FoundryVTT-Sequencer
that referenced
this issue
Jul 23, 2024
Codas
added a commit
to Codas/FoundryVTT-Sequencer
that referenced
this issue
Jul 23, 2024
Codas
added a commit
to Codas/FoundryVTT-Sequencer
that referenced
this issue
Jul 23, 2024
I believe this has been fixed in previous versions |
Coincidence that this was closed 2 hours ago but as of the newest versions (Foundry 12 build 330, Sequencer 3.2.12, and P2e 6.0.4) This is still happening. The webm for the effect stops looping. |
This bug appears to still be happening on version 3.3.6. |
Fixed in 3.4.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When an effect uses the stretchTo method, the effect will cease looping properly when it's also using the persist method.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The effect animation should loop to the beginning of its animation again,
Screenshots
Screen.Recording.2024-07-17.180617.mp4
Here's a recording of a macro I use that uses stretchTo to create a conduit between two points. As you can see, it stops animating after one loop.
Setup:
Active modules:
Additional context
This problem appears to be exclusive to the 3.2 versions. I tried a few different releases and found that. 3.1.4 is the latest one that does not have this issue.
The text was updated successfully, but these errors were encountered: