-
-
Notifications
You must be signed in to change notification settings - Fork 185
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
Do not fail tag datagen when removing IDs not present at runtime #1798
Do not fail tag datagen when removing IDs not present at runtime #1798
Conversation
|
This is queued to be merged after #1799 as that removes the EFH entirely, possibly superseding this PR. |
Right, but that PR targets the latest version as opposed to 1.21.1. Are you suggesting that the EFH removal would also likely be backported to 1.21.1 in place of this? |
Previous comment by @marchermans was mistaken (asked via Discord), as this PR is for 1.21.1 while the ExistingFileHelper changes are in 1.21.4. As those changes will not be backported due to their compatibility-breaking behavior, this PR can move forward. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry missed that this is for 21.1 this is now fine. My mistake
🚀 This PR has been released as NeoForge version |
Continuing on from the discussion on (the now seemingly redundant PR) #1794, this PR allows Tag data generation in 1.21.1 to proceed as normal in the event that the
ITagAppenderExtension::remove
methods are used with IDs which may not exist at runtime, bypassing theExistingFileHelper
checks for such IDs should they be marked as removal entries.