-
Notifications
You must be signed in to change notification settings - Fork 293
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
Log spam - Creative tab loop found when adding Block{quark:monster_box} next to Block{minecraft:spawner} #4764
Comments
I'm also experiencing this (seems intermittent?) and it results in entire creative tabs vanishing from the menu. |
It's definitely not Copycats+ in my case since I'm not using it in my pack. Nice to see someone else has spotted this too though! |
Forge 1.20.1
|
Also experiencing significant issues with this bug. It completely hides the contents of entire creative tabs. |
Experiencing this as well |
I think this is related to Every Compat somehow - I had the exact same error (and missing torches in JEI along with other items), and removing Every Compat solved the issue. Needs more testing, but just in case! Edit: Never mind, error still being thrown (but items returned) |
Seems to be just any mod that adds a lot of new items/blocks from what I can tell, if I make Supplementaries go into it's own creative tab it happens less but still occasionally does. |
I added some debugging tools to the config. If you can still reproduce this in the next version please reach out to me on discord. |
Looks like this is still happening. Version 1.0-16 should have more options to test. I personally have never managed to reproduce this issue, so here's some points I think could be good to try and figure it out:
Asking for anyone who can reproduce this to reach out on discord as well so we can try and track it down, thank you. |
I'm a bit new to bug reporting MC stuff, but I have the same error (on a relatively fresh ATM9 modback install, ATM9 0.2.58 ) I turned on verbose logging captured the following. I hope it's what you're looking for. I don't get an error/stacktrace, but I do get a ton of this spam: (file attached) It keeps on going. I can share a full log if that would help too, but maybe I'm not sharing anything useful, so I didn't want to clutter up the thread more than I already am. |
Still happening in 1.20.1 with version 1.0-19 |
This comment was marked as duplicate.
This comment was marked as duplicate.
I am also having this same problem today in a modpack that I am making |
Still happening here.
|
Hello @Vazkii ) I don't know if this will help. I was looking through the log and remembered about the Zeta error that burned my log of 1200 errors, I went to this GitHub and saw your message, I turned on These errors have completely stopped:
|
Still getting this error |
I think it would be great if Quark had an option to add their own separated creative tab because from what I can tell other mods that cause this issue and don't have their own creative tab, if they have an option to add their own creative tab and the same is toggled on the mod in question stops causing this error (ex: Supplementaries) |
When you tried to reproduce this issue, have you tried with large modpacks? because this issue doesn't seem to happen on small modpacks, it looks like the more mods that add items directly to the vanilla creative tab you have installed bigger the chance for this issue to happen. the issue is intermittent, and as far as I know, it only affects the redstone blocks and functional blocks creative tabs if you join your minecraft world and the issue is not present, it won't happen during gameplay. It will only have a chance to happen again when you exit and join the same or a different world |
Hi.
While putting together a mod pack I noticed the following appearing a lot in my logs.
[18:44:05] [Render thread/WARN] [zeta/]: Creative tab loop found when adding Block{quark:monster_box} next to Block{minecraft:spawner}
It doesn't seem like it's intended to do that and something has clearly gone wrong, though nothing is amiss as far as I can see. I figured it's worth reporting just in case. If nothing else it causes a fair amount of log spam.
I've reported it here because Zeta is specifically cited in the warning, but it might be a Quark issue. I'm not certain.
The text was updated successfully, but these errors were encountered: