Skip to content

Getting Started

LlaGuiTo edited this page Oct 4, 2026 · 1 revision

Getting Started

Applies to Mystical Realms Translation & Fixes 1.0.1 for Minecraft 1.21.1 (resource pack format 34).

Requirements

Minecraft 1.21.1 exactly
Resource pack format 34
Loader any — NeoForge, Fabric, Vanilla
Java 21

Nothing else is required. The pack has no dependencies, and it does not need the mods it translates to be installed — an unused translation file is simply ignored.

Install it

Drop MysticalRealms_TranslationFixes-1.0.1.zip into your resourcepacks folder and enable it in Options → Resource Packs. That is the whole installation.

To have it applied for everyone automatically, see Server Setup.

Which side needs it

Setup Result
Client only Translations and fixes apply to you.
Server only The server serves it; clients download it on join.
Both Works.

There is nothing server-authoritative in this pack — it is pure assets — so a client-side install is perfectly coherent and needs no server cooperation.

What you are installing

Assets only. No items, blocks, entities, recipes, advancements or sounds. The only behavioural effect is that certain error messages stop appearing in the log.

Two things worth knowing:

  • It never modifies another mod. Everything lives in this pack's own files, under the other mods' namespaces. That is how Minecraft's translation merge works, and it is also why the pack is safe to remove at any time.
  • It will not translate a mod that has no English text to begin with. Translation starts from each mod's own en_us.json.

If some text stays English

That is the intended behaviour, not a bug. This pack only supplies keys a mod is missing:

  • If a mod already ships a complete Spanish locale, there is nothing left to add and the pack changes nothing for it.
  • If a mod ships no Spanish at all, every key is supplied.
  • If a mod ships a partial one, only the missing keys are supplied.

The full per-mod breakdown is in Translations. If a specific string is still in English and should not be, that is a missing key — open an issue naming the mod and the string.

Checking that it loaded

The pack appears by name in your resource pack list. If a fix worked, the corresponding parse error is simply absent from the log — the fixes are silent by design, so the only way to confirm one is to look for the error it would otherwise have produced.

Removing it

Delete it from your resource pack list. Because it never touched the mods, removing it restores vanilla behaviour with nothing to clean up and nothing broken.

Clone this wiki locally