Closed usafphoenix closed 9 years ago
usafphoenix
commented
9 years ago --crash log redacted/deleted-- reason for crash localized to metallurgy config "utility ores" being disabled and ex nihilio/ex astris attempting to output to items contained only when the "utility ores" set is enabled
usafphoenix
commented
9 years ago magnesium, bitumen, potash, sulfur, phosphorous, saltpeter are the offending items. (They were disabled in metallurgy's config "utility ores"), re-enabling prevents crash, but at the cost of 6 items i did not want to add to my modpack, i can reduce the impact by not generating those ores, i guess, but i'm curious: is there a way to prevent the sieve from registering recipes?
usafphoenix
commented
9 years ago basically, if only part of the metallurgy modules are installed it causes a null-item exception of sorts (not sure what the technical term for it is. it's looking for an item that was never registered, basically.
MikeLydeamore
commented
9 years ago usafphoenix
commented
9 years ago took me a minute to understand what i was looking at, but i get it now. update looks good :+1:
having a entity render crash in a custom modpack using the autosieve when i click to view it's inventory. crash log shows item as "null", which i think means there is a possible item ID conflict? but with changes to minecraft/forge, config files no longer enable me to change item/block IDs (or scan through them to find conflicts, but i'm pretty sure it's an item ID override, because viewing recipes the sieve is used for shows gravel and sand having a low chance of outputing fire [animated block]. pretty sure i should not be seeing it output fire. lol.