Posted May 27, 20178 yr When attempting to load an invalid loot table, forge will usually detect that the loot table is invalid and simply reject it, printing a message to the console (which I believe is the intended behavior). However, in some cases, it apparently fails to notice that it is invalid and tries to parse it anyway, producing a server crash when you try to load a world containing that loot table (and, in the case of singleplayer worlds, causing the game to hang on the loading world screen). An example of a loot table that causes this crash (it has an extra comma before the last pool). The log. The crash report. Edited May 27, 20178 yr by SuperJedi224
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.