PepperCode1
PepperCode1
This is no longer necessary with the addition of #4599, though that pull request does not resolve the issue of mixined data accessors potentially being out of order and the...
I misunderstood and this issue is entirely unrelated to #4599 (or its predecessor, #3584), though I'm still unsure whether such a complicated approach is needed to allow only two uncommon...
This is not enough information. Send your game log.
There has not been a response from OP in months, so I will close this issue. If it still occurs, open a new one.
I don't agree that it makes sense for the default to respect the existing predicate, and I think adding additional methods only adds unnecessary complexity for the user when they...
To further illustrate my point, if I call `wrapper.addLayerBefore(SLEEP, myLayer)`, it will have no additional predicate besides what my layer checks because the `SLEEP` layer is not in a `SubLayer`....
This is intended behavior that matches OptiFine but I plan to add an option to allow this eventually. Changing the behavior unconditionally will break resource packs that depend on it.
Related to #69.
I agree with this in general, but of course each event and its use cases need to be considered separately. Event results can also be standardized in the contribution guidelines...
I don't agree with this implementation. I think it would be better to add a `CompatMetal.getName(Mods)` overload and have the metal itself provide the correct name for the passed mod....