Implement mapping and exporting of custom sounds - #32
Merged
eclipseisoffline merged 7 commits intoMay 29, 2026
Conversation
# Conflicts: # README.md # client/src/main/java/org/geysermc/rainbow/client/command/PackGeneratorCommand.java
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
1 participant
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 PR implements the mapping and exporting of custom sounds - which is quite simple, given the differences between Java's and bedrock's sound definitions aren't huge. Users are able to optionally map and include all loaded custom sounds when using Rainbow, by running the
/rainbow auto soundscommand. They can also include custom sounds only from certain namespaces, using the/rainbow map sounds <namespace>command.Depends on languages#150Languages have been pushed to eclipseisoffline/geyser-languages for now, pending Crowdin fixes upstream.This PR also fixes #34.