Pride capes #2159
Merged
Pride capes #2159
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
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.
What
Adds pride flag capes to the cape selector, using a new method of adding always-unlocked capes, and tweaks the ui of the cape selector app to work better with multiple rows of capes.
(also adds me to the dev cape list)
Implementation Details
A new set of capes was added to
CapesRegistrythat will always be unlocked for all players, and both CT and non-CT methods to add to it.The weird looking "new HashSet.containsAll" thing was an intellij suggestion that apparently improves performance.
Outcome
Pride flag capes, only 5 months after pride month!
Additional Information
Potential Compatibility Issues
API was only added, so none.