-
-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Guard against item BakedModels using incorrect RenderTypes #1822
Conversation
Last commit published: 2032d12445c0a371f97ac45a5cfbe6229d44636a. PR PublishingThe artifacts published by this PR:
Repository DeclarationIn order to use the artifacts published by the PR, add the following repository to your buildscript: repositories {
maven {
name 'Maven for PR #1822' // https://github.com/neoforged/NeoForge/pull/1822
url 'https://prmaven.neoforged.net/NeoForge/pr1822'
content {
includeModule('net.neoforged', 'neoforge')
includeModule('net.neoforged', 'testframework')
}
}
} MDK installationIn order to setup a MDK using the latest PR version, run the following commands in a terminal. mkdir NeoForge-pr1822
cd NeoForge-pr1822
curl -L https://prmaven.neoforged.net/NeoForge/pr1822/net/neoforged/neoforge/21.4.55-beta-pr-1822-item-rendertype-check/mdk-pr1822.zip -o mdk.zip
jar xf mdk.zip
rm mdk.zip || del mdk.zip To test a production environment, you can download the installer from here. |
Sadly we can't really backport this, although I would have appreciated it yesterday. |
Is it necessarily the case that every model that doesn't use |
Not necessarily, no. In principle, one could use a |
🚀 This PR has been released as NeoForge version |
Should we backport this to 1.21.1? This might break some models, but using the wrong RenderType can lead to subtle correctness or performance issues.