Load My F***ing Tags in All the Mods 10

This mod is a small safety net for tags. Normally, if one or more entries in a tag are invalid, Minecraft throws out the entire tag. The mod stops that from happening, so one bad entry doesn't take the rest of the tag's contents down with it.^[1]

Here's why that matters. Say a mod or data pack adds an invalid entry to minecraft:mineable/pickaxe. Without this mod, all pickaxe-mineable blocks could become unmineable, which breaks the game.^[1]

What you'll see when it kicks in

If the tags are "cooked", the mod shows a message in the game. More detail, similar to what the base game writes, ends up in the log of the server or client the mod is running on.^[1]

In this pack

The pack includes version 1.1.1+1.21.9 of the mod, using the NeoForge build (file lmft-1.1.1+1.21.9-neoforge.jar). It was first included in version 2.37 of the pack or earlier.^[2]

Good news: there is nothing to craft for this one. The mod is a simple safety fix that works in the background, so your first steps are about knowing what it does and where to look if something goes wrong.^[1]

What it does for you

Normally, if a mod or data pack adds one invalid entry to a tag, Minecraft throws out the whole tag and its contents. This mod prevents that, so one incorrect entry no longer breaks the entire tag.^[1]

The mod's own example is an invalid entry added to minecraft:mineable/pickaxe. Without the mod, all pickaxe mineable blocks would become unmineable, which breaks the game. With it, a mistake in a mod or data pack can't break a whole portion of the game.^[1]

What to check if something looks off

1. Watch for the in-game message. The mod shows one if the tags are "cooked".^[1]
2. Open the log of the server or client that is running the mod. It has more info, similar to what the base game prints.^[1]
3. If you want to understand the in-game chat message better, or silence it, the mod author has an info page on the mod's GitHub project.^[1]

This one is a short section, because this mod has no machines, multiblocks, power, fluids or item automation. Nothing in the sources describes any of those systems, so there is nothing to build or wire up. It works quietly in the background instead.^[1]

What the mod does

Normally, if a mod or data pack adds an invalid entry to a tag, Minecraft throws out that tag's entire contents. This mod stops that. It prevents the whole tag from being lost when one or more entries inside it are invalid.^[1]

The mod's own example is an invalid entry added to minecraft:mineable/pickaxe. Without the mod, that mistake could leave every pickaxe-mineable block unmineable, which breaks the game.^[1]

How you find out about problems

If a tag is "cooked", the mod shows a message in the game. You can also find more detail, similar to what the base game gives you, in the log of the server or client the mod is running on.^[1]

Pack configuration

The pack sets disableIngameError to true in its config file.^[3]

Unverified The mod's page says the in-game chat message can be silenced, but the sources don't spell out exactly what disableIngameError changes. It's likely tied to that message, but this is unconfirmed here.

There's only one option worth knowing about here, and this pack sets it for you. The mod stops one bad entry from wiping out a whole tag, and it can tell you in game when a tag has been "cooked". That's the message this option relates to.^[1]

• disableIngameError is set to true in this pack.^[3]

The mod normally shows a message in game when tags are cooked. It also writes more detail, similar to the base game, to the log of the server or client it's running on. So even with the in-game message turned off, the log is where you'd look to track down a broken tag entry.^[1]

Unverified The sources don't confirm the mod's default for this option, so I can't say whether the pack changed it. They also don't describe exactly what the option silences beyond its name, so treat it as the switch for the in-game error message.

This mod has a short history in the pack. The pack changelogs only record when it was added and when it was updated, so there is no feature-by-feature changelog here.^[4][5]

• All the Mods 10 2.37: the mod was added to the pack at version 1.0.4+1.21.^[5]
• All the Mods 10 4.13: the mod was updated from 1.0.4+1.21 to 1.1.1+1.21.9.^[4]
• All the Mods 10 8.1: the pack ships version 1.1.1+1.21.9, using the file lmft-1.1.1+1.21.9-neoforge.jar. That is the same version the 4.13 update brought in.^[2][4]

Unverified What changed between mod versions 1.0.4 and 1.1.1 is not shown in the sources here, because no changelogs are stored for the shipped jars. The mod's own changelog is the place to look for what that update added or fixed.