Draft
Conversation
Broken code is to be expected, check classes containing `TODO(Ravel)` in them.
Contributor
|
@Big-Iron-Cheems You can remove all |
Collaborator
Author
|
Welp, from what I see Ravel should support them fine for Java. Might try it again later to be sure. |
Look for remaining `// TODO(Ravel)` and anything else I may have missed.
Not tested yet but it should work.
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
3 participants
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.
Type of change
Description
Future 26.1 update.
This is completely unusable and won't build at the moment.
Still 1.21.11 version but with Mojang mappings partially applied (resolve all
TODO(Ravel)marked files).Might as well manually verify each file just in case, I wouldn't blindly mark the code as reviewed here.
Related issues
Closes #6247
How Has This Been Tested?
Not buildable yet.
Checklist: