Console errors regarding recipes
Dalethium opened this issue · 9 comments
I am not sure if this happens at late start up or at login, however these errors show up in the console
Unidentified mapping from registry minecraft:recipes
feederhelmet:feeder_item.peripheralsplusone:smart_helmet: 9045
feederhelmet:feeder_item.cactusmod:cactushelmet: 9109
feederhelmet:feeder_item.nex:armorhelmetbone: 9102
feederhelmet:feeder_item.avaritia:infinity_helmet: 9018
feederhelmet:feeder_item.shipwrecks_winslow:diving_helmet: 9108
feederhelmet:feeder_item.nex:armorhelmethidesalamander: 9103
peripheralsplusone:recipe_chunk_loader_tile.chickenchunks:chunk_loader|0: 14463
thermaldynamics:cover: 11917
All lines are prefixed with: [Netty Client IO #0/ERROR] [FML]:
I do have all the mods listed there installed, if there's anything else you need just let me know!
This is a bit strange. Can you post a log file and the Name if the Modpack you're playing?
No that is enough. I already know how I can fix this probably. One question, does the recipe for an AutoFeeding smart helmet work?
Sure! It's called Convergence, I just play it with me and a couple friends (I put it together) you can play if you want ;) haha
Log up until server log in
Modlister mod list
Modlister json output (since this pack changes a lot)
The output in question is at line 18595, there's a LOT of output there we recently updated to 1.12 so there's still some bugs to work out. Sorry if it takes forever to load.
Here is a direct upload for you in case the pastebin page takes too long to load:
BFnL78sr.txt
Oh and I've only noticed this client side, however I don't read the server log as much so it could be there too idk.
Do you need anything else?
the recipe works, but i can't take the smart feeding helmet out of the crafting table.
like it shows the end item but i can't pull it out -- idk for sure but it seems like the client thinks it's a recipe but the server does not.
Hey! So, I was going through my storage, and the feeding smart helmet did craft -- however it did not appear to craft at the time, it may have been some sort of desync error. I'll try to investigate further, sorry for taking so long!