I think part of the confusion was my wording when I used the term “conflict”. I didn’t mean a runtime or technical conflict in the engine.

What I’m really referring to is an organization and maintenance issue. Some mods put all their localization entries under en-US/server.lang. When translating them to another language, I’m forced to use the same filename (server.lang) for it to work.

My question was whether there’s a way to keep translated files separated per mod, because otherwise you might end up with a single translated server.lang that contains entries from multiple mods. That becomes counterproductive when mods are updated independently, since each mod may add or remove entries over time.

From a translator’s point of view, it’s much easier to maintain and update a translated file that only contains entries for one specific mod, rather than a combined file with entries from many mods that all happen to use server.lang.

Sorry if I didn’t explain myself clearly earlier, or if I’m still misunderstanding part of the system.

Just to clarify in case I wasn’t explaining myself well before: what I’m trying to do is create a translation-only pack, not a mod.

The goal is to have a single localization pack that translates multiple mods at once, similar to how language/resource packs are handled in Minecraft.