Open
Conversation
Author
moxie-coder
added a commit
to JS-Engine-things/flixel-JS-Engine
that referenced
this pull request
Feb 22, 2026
|
chat did we forget about the |
Author
I'm not sure I follow, what do you mean? |
|
oh wait I see what this change does, weird why they used the game ticks for this check it makes no sense Basically it's supposed to not run more than once so if the function is called during an update function and it's already doing the checks it will not check again because inputs can be checked more than once if you spam, and doing so can cause lag spikes, so if you are lagging, this should do what It was supposed to do |
swordcube
pushed a commit
to swordcubes-grave-of-shite/flixel
that referenced
this pull request
Feb 22, 2026
was taken from this pr to codename engine's flixel fork: CodenameCrew#21
This file contains hidden or 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
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 fix resolves an issue where
__justPressedand__justReleasedcould fail at extremely high frame rates. In CNE, this issue manifested as sometimes being unable to hit regular notes.