-
Notifications
You must be signed in to change notification settings - Fork 75
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.20.1 Forge] Curios menu does not appear #347
Comments
That is not the default Curios GUI. You would need to report this to the developer of the mod that adds the Curios GUI as a tab like that. |
@TheIllusiveC4 The normal curios tab flow is not working either however - it appears and disappears. Being the click on the icon, keybind, etc |
What do you mean by appear and disappear? Please share screenshots of your situation if possible. Also, this may be a result of the mod that has added the Curios GUI as a tab in your original post so be sure to remove that mod first before testing in order to isolate a 3rd party mod conflict. |
Hey C4! I've been getting this exact same issue too and I initially thought it was the mod adding the tabs like in the original post. The tabs are added by the mod L2Library: https://www.curseforge.com/minecraft/mc-mods/l2library L2Library is not the cause of the disappearance though. I was able to get this to happen on my client without L2Library installed. I'm not quite sure if I can recreate it with only Curios at the moment. But, I do have a log entry that happens when attempting to click on the Curios button in the inventory GUI:
Another strange issue is that when this disconnect/disappearance happens the Trash Slot mod shows an error in-game that the server does not have Trash Slot enabled despite it being on my client and in the mod list. Another error that happens in the log is when a Sophisticated Backpack is slotted in a Curios slot:
Let me know how I can help further, MC: 1.20.1 |
Hm, interesting. I'm not quite sure what the cause could be, it could theoretically be anything that touches the player inventory screen. The fact that Trash Slot is also showing errors despite being seemingly unrelated makes me wonder if it's some kind of network error from something else that is cascading to Curios for some reason. Are you able to reproduce this reliably? If so, reproduction steps and a mod list could help me narrow this issue down further. Also, is this in single player or on a server? |
Heya @TheIllusiveC4 , I'm working on getting more information for you right now on stream. I'm thinking this issue may be related to Trash Slot. I am working on an instance with Just Trash Slot and Curios to see what happens. This issue occurs in Single Player, I have not tested on a server yet. On my modpack instance, it was reliably happening close to 100% of the time. Since removing Trash Slot, it has seemingly stopped. This issue may be related: TwelveIterationMods/TrashSlot#104 I'll get back to you with more information as I find it |
This seems to be some loading / packet handling race condition. Some factors that may be relevant:
Healthy Path (only Curios in dev):
Unhealthy Path (when reproduced in modpack):
|
Thanks for all the info. I do agree that it seems likely to be some kind of packet handling race condition, it would make the most sense all things considered. Since I'm unable to reproduce this in-dev, @Darkosto would you mind testing this jar in your modpack instance(s)? curios-forge-5.4.4-packetfix+1.20.1.zip I've reworked some of the networking that I think is causing the issue, but I don't have a way of testing this reliably on my end. |
Hey @TheIllusiveC4 Just loaded this testing jar up and it seems like the issue is fixed. I clipped testing it out in case you want to see what's going on visually: https://clips.twitch.tv/InexpensiveBovineFinchKAPOW-i7nShsjsa6PjpSml Would you like me to send over any logs or other information to finalize the fix? Thanks again! |
That's alright, I have everything I need. Thank you very much for testing it, I'll be releasing the update with this fix very soon. |
Versions (Be specific, do not write "latest"):
latest.log
debug.log
The text was updated successfully, but these errors were encountered: