Skip to content
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

[1.14.4] Search Tree should be populated after config load #6006

Closed
F43nd1r opened this issue Aug 2, 2019 · 2 comments
Closed

[1.14.4] Search Tree should be populated after config load #6006

F43nd1r opened this issue Aug 2, 2019 · 2 comments

Comments

@F43nd1r
Copy link

F43nd1r commented Aug 2, 2019

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.

@F43nd1r F43nd1r added the Triage This request requires the active attention of the Triage Team. Requires labelling or reviews. label Aug 2, 2019
@LexManos
Copy link
Member

LexManos commented Aug 2, 2019

They are loaded at startup, and then reloaded again after data packs are loaded.

@LexManos LexManos closed this as completed Aug 2, 2019
@F43nd1r
Copy link
Author

F43nd1r commented Aug 2, 2019

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.

@autoforge autoforge bot removed the Triage This request requires the active attention of the Triage Team. Requires labelling or reviews. label Feb 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants