We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As discussed here https://www.minecraftforge.net/forum/topic/74068-1144-disabling-blockitems-based-on-configuration/?tab=comments#comment-355585, the creative search tree should be populated after mod configurations were loaded.
The text was updated successfully, but these errors were encountered:
They are loaded at startup, and then reloaded again after data packs are loaded.
Sorry, something went wrong.
Alright, idk whats going on here. One guy tells me to create an issue, the other closes it instantly.
As Animefan8888 noted, this is a real issue: I shouldn't have to call populateSearchTreeManager after the ModConfig.ModConfigEvent.
populateSearchTreeManager
ModConfig.ModConfigEvent
No branches or pull requests
As discussed here https://www.minecraftforge.net/forum/topic/74068-1144-disabling-blockitems-based-on-configuration/?tab=comments#comment-355585, the creative search tree should be populated after mod configurations were loaded.
The text was updated successfully, but these errors were encountered: