Tag Rescue
No reviews yet
Puts back the tag entries a mod deletes with "replace": true. Silently, Minecraft lets them go.
Includes quality of life improvements and small tweaks to enhance and customize gameplay.
Neoforge is a fork of the Minecraft Forge available for versions 1.20.1+ of Minecraft. Many Forge mods are compatible with Neoforge and vice versa.
Community voices
Reviews
Click once to include, again to exclude, again to clear
No reviews yet. Be the first to review this project!
Get it on
Available Platforms
About
Project Details
For authors
Embed Badge
If you're the author of this project, you can embed a live badge anywhere that supports HTML or Markdown. It updates automatically whenever ratings change.
Use HTML for any page that supports it, or Markdown for README files and Markdown-based descriptions.
Identifiers
Platform IDs
Resources
External Links
About
Description
# Tag Rescue
A mod sets `"replace": true` on a tag, and every entry the other mods put there is gone.
No error. No warning. Not a line in the log.
Blocks stop being mineable. Ores stop generating. Structures stop spawning. You notice in week
three, and spend an evening bisecting a 300-mod list.
## What actually happens
When a tag file declares `replace`, Minecraft empties the entry list before the replacing mod
writes its own — taking everything the packs below it contributed with it:
```java
if (tagfile.replace()) {
list.clear(); // everything another mod added: gone
}
```
The replacing mod means *"I define this tag now."* It has no idea a second mod already added to it.
Nobody is told.
**What counts as damage.** A mod redefining a *vanilla* tag is usually doing exactly what `replace`
is for, and the default policy lets it have that. The damage is when a replacer deletes **another
mod's** entries — that mod is nowhere in the replacer's file, nobody is told it lost, and the feature
it added simply stops working.
## What Tag Rescue does
Every entry in that list knows which pack it came from. So the wipe does not have to be
all-or-nothing. Tag Rescue keeps what should never have been deleted.
| Policy | What survives |
|---|---|
| **KEEP_MOD_ENTRIES** (default) | Entries other mods added. The replacer may still drop vanilla's. |
| KEEP_EVERYTHING | Everything. `replace` stops meaning anything; the tag is merged. |
| VANILLA | Nothing — the original behaviour, if you want it back. |
The default honours what `replace` almost always means — *"I am redefining this vanilla tag"* —
while refusing to let it delete a third party's work as collateral.
`replace` is not automatically a bug. A mod emptying a vanilla tag on purpose is using the feature
correctly. It becomes a bug the moment somebody else has already added to that tag. Individual tags
can be excluded in the config.
## Seeing it work
Rescues are logged, and `/tagrescue` lists them in game:
```
Tag Rescue
policy: KEEP_MOD_ENTRIES
Put back 1 entr(ies) across 1 tag(s):
minecraft:dirt
'file/wipe-test' wanted them gone
kept: farmersdelight:rich_soil
```
## Not the same as Load My F***ing Tags
That mod (8.2M downloads, and worth having) fixes a **different** bug: one **invalid** entry in a
tag makes Minecraft throw out the whole tag. It does nothing about `replace`. The two do not
overlap — run both.
## Notes
- Client and server. Safe on either alone.
- No dependencies.
- Configurable per tag, in `config/tagrescue-common.toml`.
- MIT licensed.
Screenshots
Gallery
Versions
Files
Relations
Project Relations
More like this
Similar Mods
Suggestions use data such as tags, dependencies, dependents, descriptions, titles, and more to rank how much they overlap with this mod.
On ModDex
Community snapshot
By the numbers
Statistics
Want to reach Minecraft players?
We're looking for a server hosting partner to feature here and other parts of the site. Interested? Send us a message!
Get in touchGet it on
Available Platforms
On ModDex
Community snapshot
By the numbers
Statistics
Resources