ForceSequence - Add 'loop', 'speed' arguments + Fix animation speed bug #431
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Animation speed bugfix differs from #409 by hooking into the function that changes animation speed rather than setting local velocity, which may affect the bNoFreeze argument. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request allows developers to loop and change the speed of forced sequences.
Additionally, this fixes a bug that would cause forced sequences to play at an accelerated rate if the player was running.
This video demonstrates the functionality of this pull request with a call to the function:
client:ForceSequence("pickup", _, 10, _, true, 10)