📄 Compatibility with .mcfunction files — Personal experience + workaround
Hello, @zVictorium 👋
I’d like to share my experience with your translator — and a little story behind it — because I believe it might help with future improvements to the project.
🎯 The mod I wanted to translate
Today I woke up wanting to play a mod called Nice Villagers Remastered 1.0.
It’s like an expansion or overhaul for Minecraft villagers: they have emotions, dialogue, and a whole system that makes them feel more human — which I found super fun and charming.
But... the entire mod was in English, and I really wanted to share it with friends who only speak Spanish.
🧪 Trying out your translator
I came across your tool, Minecraft Mod Translator, and honestly — I thought it was brilliant.
It’s well-structured, intuitive, and super useful. I tested it on a few other mods that use .json and .lang files, and it worked flawlessly.
However, when I tried to use it for Nice Villagers, the translator simply didn’t do anything.
That’s when I realized: the mod uses .mcfunction files to store dialogues and scripted events — not .json or .lang.
🧠 What I did to fix it (DIY)
Since the tool doesn’t currently support .mcfunction files, I decided to build my own workaround using Python. I’m not a professional developer, but I managed to write a script that:
- Recursively scans all
.mcfunction files inside the mod folder
- Extracts the text between double quotes (e.g.
"Hi, I’m a silly villager who loves emeralds. Do you have any?")
- Automatically translates it to Spanish using
googletrans
- Overwrites the original files with the translated text
It started off very basic, but I eventually added:
- Error handling
- Retry logic
- Delays to avoid triggering Google’s rate limits
With all of that, I successfully translated Nice Villagers into Spanish — including all the emotional dialogue from the villagers themselves.
💡 Why I’m sharing this
Because your tool is genuinely amazing and has a lot of potential to support even more file types.
It would be awesome if someday it could also support .mcfunction files — or maybe allow users to define custom patterns or regex-based translation targets for other file formats.
☝️ To be clear: my main goal with this post is to suggest support for .mcfunction files in future versions.
I won’t share my script here because:
- It only works locally on my setup
- It’s hardcoded for Spanish
- It depends on the files being extracted and structured in a very specific way 😅
🙏 Final thoughts
Thanks again for creating this tool.
It helped me understand how mod translation is structured — and even motivated me to dive deeper into Python and automation.
If you ever expand the tool to support .mcfunction or other formats, I’d be happy to help test it.
Greetings from Argentina 🇦🇷
Broken
📄 Compatibility with
.mcfunctionfiles — Personal experience + workaroundHello, @zVictorium 👋
I’d like to share my experience with your translator — and a little story behind it — because I believe it might help with future improvements to the project.
🎯 The mod I wanted to translate
Today I woke up wanting to play a mod called Nice Villagers Remastered 1.0.
It’s like an expansion or overhaul for Minecraft villagers: they have emotions, dialogue, and a whole system that makes them feel more human — which I found super fun and charming.
But... the entire mod was in English, and I really wanted to share it with friends who only speak Spanish.
🧪 Trying out your translator
I came across your tool, Minecraft Mod Translator, and honestly — I thought it was brilliant.
It’s well-structured, intuitive, and super useful. I tested it on a few other mods that use
.jsonand.langfiles, and it worked flawlessly.However, when I tried to use it for Nice Villagers, the translator simply didn’t do anything.
That’s when I realized: the mod uses
.mcfunctionfiles to store dialogues and scripted events — not.jsonor.lang.🧠 What I did to fix it (DIY)
Since the tool doesn’t currently support
.mcfunctionfiles, I decided to build my own workaround using Python. I’m not a professional developer, but I managed to write a script that:.mcfunctionfiles inside the mod folder"Hi, I’m a silly villager who loves emeralds. Do you have any?")googletransIt started off very basic, but I eventually added:
With all of that, I successfully translated Nice Villagers into Spanish — including all the emotional dialogue from the villagers themselves.
💡 Why I’m sharing this
Because your tool is genuinely amazing and has a lot of potential to support even more file types.
It would be awesome if someday it could also support
.mcfunctionfiles — or maybe allow users to define custom patterns or regex-based translation targets for other file formats.I won’t share my script here because:
🙏 Final thoughts
Thanks again for creating this tool.
It helped me understand how mod translation is structured — and even motivated me to dive deeper into Python and automation.
If you ever expand the tool to support
.mcfunctionor other formats, I’d be happy to help test it.Greetings from Argentina 🇦🇷
Broken