Choonster

Please post code in a code block (the <> button in the editor) or on Gist/Pastebin with syntax highlighting. That's not the same NBT structure created by ItemMonsterPlacer.applyEntityIdToItemStack, it uses "EntityTag" rather than "AnimalTag". The target instanceof EntityMob condition is pointless, as it will always be false. When it's reached, target will always be an instance of EntityAnimal and can't be an instance of EntityMob.

It's not obvious which mod is causing this, so you'll need to remove mods until it no longer happens. Try starting with these:

In future, please create the Git repository in the root directory of your mod (where build.gradle is) and include the Gradle buildscript (build.gradle and gradle.properties), the Gradle wrapper (gradlew, gradlew.bat and the gradle directory), the source code and assets (the src directory) and your mod's license and readme files. See my TestMod3 for an example of the proper structure. I'll start debugging it soon.

Just running the game is enough, you shouldn't need to load a world or connect to a server.

Try running 1.11.2 vanilla first, that should allow 1.11.2 Forge to run.

I can't see any obvious issues with your code, could you create a Git repository for it (if you don't already have one) and link it here? I'll try debugging it myself.

What makes you think the cooldown isn't being set to 100? Are you looking at data from the client or from the server? Capabilities aren't automatically synced between the server and client, you need to sync them yourself. I explain how to sync item capabilities here.

Just have the server send a packet to the player's client in PlayerEvent.PlayerLoggedInEvent. There shouldn't be any need for a request packet here.

PlayerEvent.PlayerLoggedInEvent is only fired on the logical server. Sending a packet from the logical server to the logical server makes no sense and will only work if the logical server is running in the same process as the logical client (i.e. single player or LAN host). In addition to this, the event is fired too early for a client-to-server packet to be sent. Because of these two issues, it fails silently on the physical client or with an error on the physical server. Why does the client need to send a request packet to the server for something the server can detect itself (i.e. a player logging in)?

Forge doesn't use JSON for configuration, it uses its own file format. You can still use the Configuration class directly by creating an instance and calling the appropriate getter method for each property. This hasn't really changed since 1.7.10. The new annotation-based system is a layer on top of the Configuration class that automatically creates an instance and calls the appropriate getter methods for each field based on its type. I have a brief explanation of the system as well as links to an example of it here.

Open the game directory. Unless you changed it when creating the profile, this is the .minecraft directory. Open the logs directory inside the game directory. Find the fml-client-latest.log file in the logs directory. Go to the Gist website in your browser. Drag the fml-client-latest.log file onto the browser page. Click "Create secret gist". Copy the URL from the browser's address bar. Paste the URL into the post editor in this thread.

Use an IItemHandler instance whenever you need an inventory. Expose it via the Capability system to allow external access to it (e.g. for hoppers or other item transfer systems). The default implementation of IItemHandler is ItemStackHandler, you can generally use or extend this. ItemHandlerHelper contains Forge's utility methods for IItemHandlers. ItemHandlerHelper.giveItemToPlayer will attempt to insert an ItemStack into a player's inventory and drop the remainder on the ground as an EntityItem. You could adapt this to attempt to insert the remainder into your custom inventory and only after that drop the remainder on the ground.

It's in the logs directory of the profile's game directory (.minecraft by default). You don't put it anywhere else on your computer, you upload it to Gist or Pastebin and link it here.

Malisis Doors is trying to use a class from Malisis Core that doesn't exist. Make sure both mods are up-to-date. If the issue persists with the latest versions of the mods, report it to the author.

Zombie Awareness is trying to call a method from CoroUtil that doesn't exist. Make sure both mods are up-to-date. If the issue persists with the latest versions of the mods, report it to the author of Zombie Awareness.

That advice was for 1.11.2, I missed that you were using 1.10.2. In 1.10.2, use EntityList.getEntityString to get the registry name of an entity instead of using EntityList.getKey. The rest of my previous post still applies to 1.10.2. EntityList.ENTITY_EGGS should exist in 1.10.2 if you're using recent MCP mappings. If it doesn't exist in your workspace, either update your mappings or look for the field with type Map<String, EntityList.EntityEggInfo>.

You can also try GitKraken, which is my graphical Git client of choice.

Something on line 435 of TileHunterBench was null when you tried to access a field or call a method on it. If you don't know what was null, set a breakpoint on that line and run Minecraft in debug mode. When the breakpoint is hit, look at the values used on that line to see which is null.

This error is thrown when you try to load a coremod built for 1.7.10 or earlier on 1.8 or later. Please post the complete FML log (logs/fml-client-latest.log) of a single version (that's at least 1.8) you want help with, it's hard to diagnose issues with small snippets of different logs on different versions.

You need to call World#notifyBlockUpdate from the TileEntity whenever a value used by Block#getActualState changes. This tells the server to send the TileEntity's update packet to any nearby clients as well as telling them to re-draw the chunk containing the block, using the new actual state to select the model. You also need to call World#notifyBlockUpdate from TileEntity#onDataPacket so that the client re-draws the chunk whenever it receives the TileEntity's update packet. You can see an example of a block that uses TileEntity data in Block#getActualState here: BlockColoredRotatable, TileEntityColoredRotatable

LivingSpawnEvent.SpecialSpawn is fired just before an entity is spawned by WorldEntitySpawner (passive spawns) or MobSpawnerBaseLogic (monster spawners).

Use EntityList.getKey(Entity) to get the registry name of an entity, check if that registry name exists as a key in EntityList.ENTITY_EGGS (i.e. the entity has a spawn egg registered) and then create an ItemStack of Items.SPAWN_EGG with the registry name in the NBT. Look at ItemMonsterPlacer.applyEntityIdToItemStack to see the NBT structure you need to create for the spawn egg. You can't use the method directly because it's client-only.

It tells you where and what the errors are. The syntax errors should be relatively easy to fix with this information.

I quoted the relevant errors in my previous post.

The error is coming from Tinkers' Construct, report it to the authors.