-
Notifications
You must be signed in to change notification settings - Fork 3
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
Registry Object Not Present for EE (only when THIS is utilizing Item Stages) #5
Comments
Try removing lines 21 through 23:
from the restriction file. Honestly as far as I can tell there just isn't an item with that id. |
I am at a complete loss right now. The item totally exists, but that's besides the point. The only reason I put that item on that line is because I tried to load up a restriction where EE/Steel Block was not on there, and I got that error. I thought I needed to make an exception for it to allow it to register. That being said, I fired everything up this morning, and I must have done something differently because now things are working the way they are expected to. The only thing that's missing is the Integration w/ Improved Mobs, but thats just because it isn't present in 1.19 I think :( |
age_1.txt Welp, thats super frustrating. It seems that once you add to the item exceptions/item list, it's causing the Steel Block issue. I attached all 7 of my ages here. Not a single file is calling to emendatusenigmatica, or a steel block of any type. Crash is consistent, I can't even load the client. Would definitely appreciate any help here. Feeling extremely defeated right now, after putting all that work in to get hit in the face with something I thought was gone.. lol I seriously hope I just did something dumb somewhere, and this is an easy fix. Thanks for taking the time to look at this! EDIT 1 |
There appears to be a similar issue on the Emendatus Enigmatica GitHub page (Ridanisaurus/EmendatusEnigmatica#202), the crash is very much the same just the item id is different. Are you sure that T.H.I.S is causing the crash, have you tried running the game without it to see if you still get the crash? |
Interesting! Yeah, in this case it was totally THIS causing it, but it seems it was due to my own mistake. Age 3, for my exception list -- Line 73 was missing a comma. No idea why it was throwing an EE error, but I literally just got the world to load after narrowing it down to that after like 8 reloads and slowly adding things back to that file.. hah. The EE error really threw me off and made this extra confusing. |
I will be implementing a fail safe in the upcoming release of EE to prevent it from showing up as the culprit for the crash by stopping data-gen if another mod failed at an earlier stage. |
Minecraft Version
1.19.2
Forge Version
43.2.14
T.H.I.S. Version
thitemstages-1.19.2-0.1.1
Describe your issue
Here is a pastebin of the test restriction file: https://pastebin.com/ZW898tu1
After a few hours of messing with this, I finally decided to try only emendatusenigmatica and lifting the restrictions. No matter what I do though, I am getting the error report in the Crash Report section. Same report over and over, letting me know about the steel block.
This issue only happens when any Item Stage is utilized. Without, the game loads fine (and the EE steel block exists).
Log File related to your crash
https://pastebin.com/VsWKaYZP
Crash Report
https://pastebin.com/VsWKaYZP
Other mods
EmendatusEnigmatica and THIS
Tried reproducing with just T.H.I.S.?
No
Performance Enchancers
None of the above
The text was updated successfully, but these errors were encountered: