Publicized MinecraftClient#textureManager#190
Publicized MinecraftClient#textureManager#190TheGlitch76 merged 4 commits intoPatchworkMC:masterfrom YTG1234:feature/public-MinecraftClient#textureManager
Conversation
…ecraftClient#textureManager`.
patchwork-access-modifications module and publicized `Min…|
Maybe we could also move all Forge's access modifications that are already in Patchwork to this new module, idk how it's going to be possible to "load" the access widener when developing other modules. Any thoughts? |
|
Moving access wideners to their own module isn't the right solution yet because nobody has made a jar processor to make access wideners transitive. |
|
I think it may be used in the forge |
|
Yep. It's only used in |
|
I will put it in the FML module |
|
Moved it to the FML module for now. I didn't bump the version - as the commit msg says. |
|
Turns out I put a |
|
Updated the title so it's less confusing |
|
@famous1622 I changed things up a little, can you review again? |
I think in the future the rendering stuff should have their own package. But for now I would agree that this aw should be in |
|
It's interesting that in most places Forge uses |
|
Was probably public forever ago and they don't want to break mods |
I thought Forge was the opposite of backwards-compatibility |
|
Forge is more than just Lex and all of them do try to maintain back-compat for some things. |
Just saw this on #125 so I decided to do it.