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

CharSelect polish #3439

Closed
wants to merge 3 commits into from
Closed

Conversation

MaybeMaru
Copy link
Contributor

Briefly describe the issue(s) fixed.

Fixed "duplicate" bf's when opening the char select screen.
Fixed memory leak at the unlock character sequence.
Fixed inputs being allowed at the unlock character sequence.
Fixed spam causing errors displaying the current character / nametag.
Made it remember your last selected character.
Optimized a bit by checking for changes only on key presses.

Include any relevant screenshots or videos.

Before

8mb.video-uor-jKOnXSzl.mp4

After

8mb.video-rG1-5FnA0AXU.mp4

@MaybeMaru MaybeMaru changed the title Char select fix CharSelect polish Sep 23, 2024
Copy link

@trayfellow trayfellow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

holy peak

@AbnormalPoof
Copy link
Contributor

Fixed inputs being allowed at the unlock character sequence.

#3355 already handles this, but everything else seems good.

@EliteMasterEric EliteMasterEric added the status: pending triage The bug or PR has not been reviewed yet. label Sep 25, 2024
@ninjamuffin99
Copy link
Member

some changes may have been fixed with #3457 although what was the specifics with the memory leak?

@MaybeMaru
Copy link
Contributor Author

some changes may have been fixed with #3457 although what was the specifics with the memory leak?

Was refering to the slowdown when switching to a character for the first time since it has to load the full character atlas mid-frame, precaching characters on create fixes the issue
Ive seen a lotta prs fixing these issues tho so i should prob close this one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: pending triage The bug or PR has not been reviewed yet.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants