Minecraftforge: Recipe loader bails after first bad recipe
While testing my autogenerator for jsons, it was extremely annoying that the loader quits loading after the first bad recipe it sees. This means that you have to relaunch the game tens to hundreds of times to see all your errors.
The loader should just skip to the next recipe if parsing one errors, and present all errors to the modder at once.
williewillus
All 4 comments
If this is implemented, I would like if it still crashed once all recipes are loaded (instead of only logging to console like models do), because otherwise I can see myself and others missing recipe errors since I only actually check the log when I notice something is wrong.
blay09
on 16 Jun 2017
Will this be fixed by https://github.com/MinecraftForge/MinecraftForge/pull/4043 or is it a more general issue?
Blay's suggestion (crashing at the end) could be added as a feature after.
mezz
on 22 Jun 2017
I have not tested the PR, but based on it's changes I assume not. The issue here is not whether it crashes or not, but that the recipe loader aborts at the first broken recipe
KnightMiner
on 22 Jun 2017
This issue is still present in Forge 1.12-14.21.1.2430. PR #4043 wasn't meant to fix this, it was only meant to log an exception instead of crashing the game.
Choonster
on 1 Aug 2017
Related issues
williewillus
路
3Comments
blay09
路
3Comments
juliand665
路
3Comments
Unnoen
路
3Comments
Sir-Will
路
3Comments
Most helpful comment
If this is implemented, I would like if it still crashed once all recipes are loaded (instead of only logging to console like models do), because otherwise I can see myself and others missing recipe errors since I only actually check the log when I notice something is wrong.