Load My F***ing Tags in All the Mods 10: To the Sky

All the Mods 10: To the Sky 2.1.0 ships version 1.1.1+1.21.9 · First seen in 1.0

Checked Sep 17, 2026All the Mods 10: To the Sky 2.1.0Sources: All the Mods 10: To the Sky 2.1.0 modlist.json · Modrinth

Report a mistake on this page

Also in 3 other packs →

Load My F***ing Tags is a mod in All the Mods 10: To the Sky 2.1.0, where it is version 1.1.1+1.21.9. Prevents Incorrect Tag Entries from breaking an entire Tag (Summary from the mod's Modrinth page.)

Load My F***ing Tags guide for All the Mods 10: To the Sky

Written for All the Mods 10: To the Sky 2.0.4 · also fits 1.0 to 2.1.0 · updated Oct 7, 2026

Last verified for All the Mods 10: To the Sky v2.1.0 on Oct 7, 2026 · text last changed Oct 7, 2026

Also applies to:All the Mods 10 2.37 to 8.3All the Mons 0.3.0-beta to 1.3.0FTB StoneBlock 4 1.1.1 to 1.23.0

Sections
5

1 section is written for this pack; 4 are shared from another pack's guide.

Every recipe and number here was checked against All the Mods 10: To the Sky 2.1.0, read from the running game on Oct 15, 2026.

What is Load My F***ing Tags?

2 parts

Same as in the All the Mods 10 8.1 guide

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]

How do you get started with Load My F***ing Tags?

2 parts

Same as in the All the Mods 10 8.1 guide

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]
Tip: The in-game message is the mod telling you that tags were cooked. The log of the running client or server is the place to look for the details.[1]

How does Load My F***ing Tags work?

3 parts

Same as in the All the Mods 10 8.1 guide

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]

Tip: If you're hunting down a broken tag from some mod or data pack, check the server or client log. That's where the mod puts the extra detail.[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.

Which Load My F***ing Tags config options matter?

Same as in the All the Mods 10 8.1 guide

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]

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.

What changed in Load My F***ing Tags between versions?

1 part

LMFT has been in the pack since All the Mods 10: To the Sky 1.0 or earlier. This pack, version 2.0.4, ships version 1.1.1+1.21.9 of it, using the file lmft-1.1.1+1.21.9-neoforge.jar.[4]

Mod changelog highlights

  • 1.0.4+1.21: a straight forward port of LMFT to Minecraft 1.21.[5]
  • 1.1.1+1.21.9: an update so that one jar on NeoForge supports versions all the way back to 1.20.2. This is the version your pack uses.[4][6]

Unverified Whether any All the Mods 10: To the Sky release changed how this mod behaves is told in the pack's own changelog, and the sources here do not show any entries for it.

Sources

  1. Load My F***ing Tags project page (modrinth) · official mod data
  2. All the Mods 10 8.1 mod list · pack file
  3. All the Mods 10 8.1 config: config/lmft.json · pack file
  4. All the Mods 10: To the Sky 2.0.4 mod list · pack file
  5. Load My F***ing Tags 1.0.4+1.21 changelog · changelog
  6. Load My F***ing Tags 1.1.1+1.21.9 changelog · changelog
Where this guide comes from

Written from what All the Mods 10: To the Sky itself ships: its files and recipes, the in-game guidebooks and the mods' own pages. Every statement links to the source it came from, and the numbers are checked against the pack before publishing.

Guide last verified Oct 7, 2026.

Was this helpful?

Report wrong info

A few words are enough, up to 500 characters. Please do not include personal details.

Version in each release

25 releases, first in 1.0
All the Mods 10: To the SkyVersionJarWhere it came from
2.1.0
Oct 15, 2026
1.1.1+1.21.9lmft-1.1.1+1.21.9-neoforge.jarFrom the published release
2.0.7
Oct 5, 2026
1.1.1+1.21.9lmft-1.1.1+1.21.9-neoforge.jarFrom the published release
2.0.6
Sep 21, 2026
1.1.1+1.21.9lmft-1.1.1+1.21.9-neoforge.jarFrom the published release
2.0.5
Sep 21, 2026
1.1.1+1.21.9lmft-1.1.1+1.21.9-neoforge.jarFrom the published release
2.0.4
Sep 11, 2026
1.1.1+1.21.9lmft-1.1.1+1.21.9-neoforge.jarFrom the published release
2.0.3
Sep 9, 2026
1.1.1+1.21.9lmft-1.1.1+1.21.9-neoforge.jarFrom the published release
2.0.2
Apr 1, 2026
1.1.1+1.21.9lmft-1.1.1+1.21.9-neoforge.jarFrom the published release
2.0.1
Mar 27, 2026
1.1.1+1.21.9lmft-1.1.1+1.21.9-neoforge.jarFrom the published release
2.0.0
Feb 24, 2026
1.1.1+1.21.9lmft-1.1.1+1.21.9-neoforge.jarFrom the published release
1.9.1
Feb 5, 2026
1.1.1+1.21.9lmft-1.1.1+1.21.9-neoforge.jarFrom the published release
1.9
Feb 4, 2026
1.1.1+1.21.9lmft-1.1.1+1.21.9-neoforge.jarFrom the published release
1.8
Dec 20, 2025
1.1.1+1.21.9lmft-1.1.1+1.21.9-neoforge.jarFrom the published release
1.7
Nov 28, 2025
1.1.1+1.21.9lmft-1.1.1+1.21.9-neoforge.jarFrom the published release
1.6.1
Oct 23, 2025
1.1.1+1.21.9lmft-1.1.1+1.21.9-neoforge.jarFrom the published release
1.6
Oct 17, 2025
1.1.1+1.21.9lmft-1.1.1+1.21.9-neoforge.jarFrom the published release
1.5.1b
Oct 2, 2025
1.0.4+1.21lmft-1.0.4+1.21-neoforge.jarFrom the published release
1.5
Sep 26, 2025
1.0.4+1.21lmft-1.0.4+1.21-neoforge.jarFrom the published release
1.4
Sep 11, 2025
1.0.4+1.21lmft-1.0.4+1.21-neoforge.jarFrom the published release
1.3.1
Sep 3, 2025
1.0.4+1.21lmft-1.0.4+1.21-neoforge.jarFrom the published release
1.2.1
Aug 28, 2025
1.0.4+1.21lmft-1.0.4+1.21-neoforge.jarFrom the published release
1.2
Aug 28, 2025
1.0.4+1.21lmft-1.0.4+1.21-neoforge.jarFrom the published release
1.1.2
Aug 22, 2025
1.0.4+1.21lmft-1.0.4+1.21-neoforge.jarFrom the published release
1.1.1
Aug 21, 2025
1.0.4+1.21lmft-1.0.4+1.21-neoforge.jarFrom the published release
1.0.2
Aug 15, 2025
1.0.4+1.21lmft-1.0.4+1.21-neoforge.jarFrom the published release
1.0
Aug 14, 2025
1.0.4+1.21lmft-1.0.4+1.21-neoforge.jarFrom the published release

"From pack files" means the list came from the pack's own files; "from the published release" means ForgeBase read the jars of the release itself.

Items and blocks

We can't match this mod to the pack's item list: it registers as lmft, and the pack's recipe dump has nothing under that name. That means we found nothing, not that the mod adds nothing. Search the item browser

Config options (how All the Mods 10: To the Sky sets them)

1 settings this pack ships for the mod. We don't have the mod's own defaults to compare them against yet.

See all 1 settings →

Show settings
SettingAll the Mods 10: To the Sky value
disableIngameError
config/lmft.json
true

Comments and tips

Loading comments...