mc1.18.x expand covalence loss range and update JEI api #2280
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
* Increase range of values for covalenceLoss config * Update jei api maven url * Increase range for covalenceLoss and update description
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.
Update jei api maven url for 1.18.x
JEI API server is down. According to mezz's discord server, we should be using blamejared instead.
Increase range for covalenceLoss and update description
The main reason this PR was made in the first place.
Allows the "covalenceLoss" value to accept 0 and values past 1.
Accepting 0 lets people "delete" EMC from everything easily if they really want to play around with it.
Values above 1 do work, but is of course not balanced. Mainly added for people who want to mess around on a server.
You can change this back to 1.0 if you want.