Back to mods
Blame (Forge) project artwork

CurseForge · Minecraft mod

Blame (Forge)

Those gosh darn crashlogs not saying which worldgen feature is crashing!

Choose a version Pick your version below, then grab the matching file.

Quick answer

Which Blame (Forge) release matches 1.16.4 Forge?

Updated 3 years ago
Best match for your filters Blame v3.7.0 (1.16.5 MC)
Game version 1.16.3, 1.16.5, 1.16.4
Loader Forge

Blame (Forge) Blame v3.7.0 (1.16.5 MC) targets 1.16.3, 1.16.5, 1.16.4 with Forge. The project page does not say whether this file belongs on the client, dedicated server, or both. No extra mods listed for this file.

Where it goes

Is Blame (Forge) required on the client, server, or both?

The project page does not say whether this file belongs on the client, dedicated server, or both.

Client Source doesn’t say
Dedicated server Source doesn’t say
Loader for this release Forge
Required install it here Optional supported, not mandatory Not supported do not install here Source doesn’t say do not assume

The source does not explicitly classify this release as client-only or server-only.

What else does Blame (Forge) Blame v3.7.0 (1.16.5 MC) need?

Blame v3.7.0 (1.16.5 MC) on 1.16.4 Forge. Every mod below is checked against that same setup.

No extra mods listed for this file

This file does not list any required mods. Do not add a library just because a different file uses it.

This file does not list any required or optional mods.

Before you install it

Add Blame (Forge) without breaking your instance.

Built for Blame (Forge) Blame v3.7.0 (1.16.5 MC) on 1.16.4 Forge. Pick another file and the loader, install side or required mods may change.

  1. 01

    Stick to this file

    Use Blame v3.7.0 (1.16.5 MC). It targets 1.16.3, 1.16.5, 1.16.4 with Forge; another release may have different loader, side or dependency requirements.

  2. 02

    Bring the mods it needs

    This file does not list any required mods. Do not add a library just because a different file uses it.

  3. 03

    Put it on the correct side

    The project page does not say whether this file belongs on the client, dedicated server, or both.

  4. 04

    Pick the file you checked

    Use the “Get this file” button beside Blame v3.7.0 (1.16.5 MC). It opens that exact file at the source.

About this project

What does Blame (Forge) add?

Ready to find who to Blame?

Fabric version: https://www.curseforge.com/minecraft/mc-mods/blame-fabric

Blame is a diagnostics tool to be put on only if you are having strange worldgen crashes or commands that break without any stacktrace. But when you have Blame on, it will attempt to gather far more infomation and print the stacktrace to the latest.log file in the logs folder above the mods folder. A much more convenient place with all the info you will need! Keep in mind, Blame only works on singleplayer or on servers. Not on clients connecting to a server.

Note: for better worldgen json parsing help in 1.17+, use Cyanide mod instead: https://www.curseforge.com/minecraft/mc-mods/cyanide-forge

Here's the current list of functionalities that Blame has!

• Prints out the stacktrace for commands that crashed when used.

(Normally, modded commands do not print anything to logs when they crash)

• Will detect and print out all broken commands when starting up a world.

(This will find commands that called an .executes() outside a .then() call because they won't work)

• Prints extra detail for features or structures that crashes during worldgen.

• Logs all ConfiguredFeatures, ConfiguredStructures, ConfiguredCarvers that are not registered.

(Mods that don't register the stuff will cause other mod's stuff to break and not spawn during worldgen)

• Detect if DynamicRegistry is loaded way too early by another mod.

(Doing so causes all other mod's registered worldgen stuff to blow up such as "Unknown Biome ID" issues)

• Logs out exactly which worldgen JSON file is broken from any mod or datapack and shows its JSON too.

• Logs out any missing loot table when the loot is attempted to be generated! Check logs if a chest is empty and this mod might catch why.

• Prints out the name of the crashing structure that has its spacing value set to 0 or if it's separation value is equal to or greater than the spacing value.

(Either one of these condition being true will crash the game.)

• Condense broken Recipe and Loot Table parsing so you can share logs easier and see errors easier.

• Fixes MC-190122 bug so that the actual true number of recipes loaded and stated in logs is correct to help debugging recipes. https://bugs.mojang.com/browse/MC-190122

• Prints out exactly which structure crashed a custom/flat ChunkGenerator because it wasn't added to FlatGenerationSettings.STRUCTURES

• Will print to logs if a Jigsaw Structure attempts to access a non-existent template pool so you know when a structure is not fully generating.

• Will log out if a mod or datapack tries to access a non-existent nbt file for easier debugging.

• Will print out if a mod classloads TagCollectionManager too early and can risk blowing up the tags of other mods that register their tag afterwards.

• Will print out what block, its nbt, and what nbt file crashed a structure processor during structure generation.

If you need to see a registry dump of all stuff in all registries, use this TellMe mod by Masady:

https://www.curseforge.com/minecraft/mc-mods/tellme

FOR MODDERS: USING BLAME IN Forge DEV ENVIRONMENT

In your build.gradle file, add this maven repository. This is where gradle will look for Blame's jar.
repositories {
maven {
url "https://nexus.resourcefulbees.com/repository/maven-public/"
}
}

Now add this to the dependency block. Replace <version> with the Blame version you want to use such as 1.16.5-3.2.1-forge. Check the CurseForge page for what the latest version is.
dependencies {
...
runtimeOnly fg.deobf("com.telepathicgrunt:Blame:<version>")
}

Now here's the important part. Add these two properties to both of your run configs in the build.gradle file. These will allow Blame's mixins to work. After you add the properties lines, refresh Gradle and run genEclipseRuns or genIntellijRuns or genVSCodeRuns based on what IDE you are using.
minecraft {
...
runs {
client {
...
property 'mixin.env.remapRefMap', 'true'
property 'mixin.env.refMapRemappingFile', "${projectDir}/build/createSrgToMcp/output.srg"
}

server {
...
property 'mixin.env.remapRefMap', 'true'
property 'mixin.env.refMapRemappingFile', "${projectDir}/build/createSrgToMcp/output.srg"
}
}
}

Launch the game and Blame should be running! You can tell as Blame will print something like this to the IDE console and latest.log file:
[16:34:10] [modloading-worker-11/ERROR] [co.te.bl.Blame/]: Blame 1.16.5-3.0.1-forge initialized

Discord Link to #telepathicgrunt-mods channel for my mods! :

https://discord.gg/K8qRev3yKZ

discord-logo-png-free-transparent-png-logos-discord-png-logo-300_300 (PNG)  | BeeIMG

Project description from CurseForge.

Pick your setup

Blame (Forge) by Minecraft version and loader

Choose the version and loader you play, then open the matching release.

4 available setups

Check the dependencies, then try the file in a copied instance before changing a world you care about.

Recent files

Blame (Forge) versions and loaders

29 of 32 releases match
Clear filters

Looking for an older file? The official CurseForge project page is in Resources.