Tuff Backport (Compatible Namespace)

What it adds

Why the minecraft: namespace?

Most backport mods register their blocks under their own mod id (somemod:tuff_bricks). That’s the safe default, but it means those blocks never become the “real” vanilla blocks even after you upgrade they stay tied to the mod forever.

This mod instead registers everything as minecraft:tuff_bricks, minecraft:polished_tuff, etc the exact IDs the real 1.21+ blocks use. The goal: if you later move to a Minecraft version where these blocks exist natively and remove this mod, your existing builds should, in principle, keep working with the real vanilla blocks instead of turning into missing/purple blocks.

• This is not an officially supported or tested technique it works because nothing currently prevents a mod from registering under `minecraft:`, not because it’s a documented feature.

• Don’t run this alongside another mod that does the same thing for the same blocks. For example, two mods claiming minecraft:tuff_bricks will conflict. However, if another mod adds minecraft:tuff_bricks and you want to add this mod as well, it will work and keep the blocks as long as you remove the old mod.

• Blockstates/hardness/blast resistance/sounds here were built to match the real 1.21 tuff family as closely as possible, but there’s no guarantee that upgrading later will be perfectly clean back up your world first either way.