Environment And Mod Information:

• Minecraft Version: 1.12.2
• Forge Version: 1.12.2-14.23.1.2562
• Doggy Talents Version: 1.12-1.14.2.314
• Java Version, Build, and Byte Type: 1.8.0_101, using 64-bit architecture
• OS Name, Edition, Byte Type, and Build Version: Kubuntu Linux 17.10

Logs

crash-2018-01-28_09.55.25-client.txt

Issue Description:

When joining my server (on my LAN) the Minecraft client crashes. It appears to be a bug in Doggy Talents.

Steps to reproduce:

Just attempt to join the server?

Additional Information:

I logged off near a doggy talents dog last night (near a food bowl) and now I can't join the server anymore because my client crashes. My 10yo son really loves your mod and he can login just fine so removing the Doggy Talents mod isn't really an option, haha.

Please try running the mod with the recommended version of Forge (1.12.2 - 14.23.1.2555). The latest versions always have some sort of bug to them

Same crash running Forge 14.23.1.2555:

crash-2018-01-28_19.05.57-client.txt

I also tried Forge 14.23.1.2604 (latest as of typing this) and it has the same crash.

Strange.. I'm not getting this crash at all. Also, put the logs on pastebin, please

25 days later and it's still not fixed. here's a paste your gonna ignore because it's on the latest forge version now build 2619. https://pastebin.com/UimynQz6

You realize other mod authors including those with the famous mods compile against the latest forge versions.

I still have yet to encounter such a bug.. and unfortunately, I haven't seen Percy around in the last few months (last time I got in contact with him was back in October). And.. I did recently had my workstation reformatted, hence losing access to the project all together. I feel that he is still working on the mod, but busy with his job in real life.

The code itself not lost, but there's a particular setup that @ProPercivalalb has for the repo since he has a custom compiler for the multiple versions of code

I'm sorry I haven't been active. I have still not been able to reproduce this bug :( . I am however making a standalone 1.12.2 (I have decided to only update 1.12.2 (the 1.13 when it comes out) and do bug fixes for 1.7.10 version) which may fix this bug. I still can't recreate the bug on this new version I will upload this version soon and please can you test and see if it works for you.

Based on the crashlog, it seems that the launcher OneSix is erroring aswell.. May I ask if this is a cracked launcher?

at org.multimc.onesix.OneSixLauncher.launchWithMainClass(OneSixLauncher.java:196) at org.multimc.onesix.OneSixLauncher.launch(OneSixLauncher.java:231) at org.multimc.EntryPoint.listen(EntryPoint.java:143) at org.multimc.EntryPoint.main(EntryPoint.java:34)

@NovaViper @riskable Your error is related to a config setting in your forge.cfg

Simply turn these two lines

# Set this to true to remove any Entity that throws an error in its update method instead of closing the server and reporting a crash log. BE WARNED THIS COULD SCREW UP EVERYTHING USE SPARINGLY WE ARE NOT RESPONSIBLE FOR DAMAGES.
    B:removeErroringEntities=false

    # Set this to true to remove any TileEntity that throws an error in its update method instead of closing the server and reporting a crash log. BE WARNED THIS COULD SCREW UP EVERYTHING USE SPARINGLY WE ARE NOT RESPONSIBLE FOR DAMAGES.
    B:removeErroringTileEntities=false

to

# Set this to true to remove any Entity that throws an error in its update method instead of closing the server and reporting a crash log. BE WARNED THIS COULD SCREW UP EVERYTHING USE SPARINGLY WE ARE NOT RESPONSIBLE FOR DAMAGES.
    B:removeErroringEntities=true

 # Set this to true to remove any TileEntity that throws an error in its update method instead of closing the server and reporting a crash log. BE WARNED THIS COULD SCREW UP EVERYTHING USE SPARINGLY WE ARE NOT RESPONSIBLE FOR DAMAGES.
    B:removeErroringTileEntities=true

This should fix all of your issues and won't result in any damage to the world or otherwise.

@darkshadow1809 Thanks for providing the solution! This would explain why we couldn't reproduce this error. I am going to close the issue now.