
Hello, everyone!

Hello~!
Hello!

While working on the English version, I’ve already noticed a few things, so I’d like to share them this time!

Especially when I ask AI to check my translations and wording, it keeps pointing out things that make me think, “You know what? That’s actually true!” Sometimes I can’t help but laugh. (lol)

They’re not major problems, but we’ve encountered some unexpected challenges that only became apparent once we actually started working on the English version.
This time, we’ll talk about the challenges and discoveries we’ve made while developing the English version.
📝 [Common] Project Information and Recent Activity
Originally, I planned to start this journal by documenting the development process of my 2D action game.
However, I decided to begin with my RPG instead, as there are some things I’d like to document along the way.
①Share the current development progress.
②Introduce game content without revealing major spoilers.
③Share other updates and information worth discussing.
I’ll be writing about various things as they come to mind!
🎮 Progress on the English Version

First, let me share our current progress.

We’re continuing to translate the system-related text into English!

As I’ve been translating, I’ve come across cases where Japanese names and class names can’t simply be used as they are in English.

In those cases, AI also suggests alternative expressions and translations, which I use as references while making adjustments.
We have a few examples, so I’ll explain them below.


Also, I’m keeping the internal markers used for reference in Japanese.
That makes it easier to check things later and make sure there aren’t any mistakes.
🌎 Japanese-Made English Doesn’t Always Work

For the Japanese version, I came up with skill names based on how catchy they sounded…

But it turns out that quite a few of them don’t sound natural or make much sense to English speakers.
Skill names are a good example. The protagonist’s skills had particularly many issues.
- Fighter Intention → Not quite right
- Ignore Sword → Unnatural
- Dizziness Sword → Unnatural
- Physical Speeder → Doesn’t really sound like a skill name
- Ignore Slash → Unnatural

After getting this many names pointed out, all I could think was “😂” (lol).

For names and skill names that were flagged, we sometimes ask AI to suggest alternatives after explaining things like these: (lol)
- The visual effect looks like XX, and the attack works like this.
- This skill is used by a certain monster, which is why I chose this name.
- The skill has a particular additional effect, so I named it this way.

By explaining the image and intention behind a skill, AI can suggest alternatives like, “In that case, this name would be more suitable!”
The more specific you are about the image you want to convey, the wider the range of suggestions AI can provide.
🌎 How Pronunciation and Meaning Vary by Region

This was one of the challenges I encountered while translating character names.

For example, there’s a pirate martial artist named “ジェノルク” (Jenoruku) in the game…
Here are some of the English spellings that were initially suggested.
- Genork/Genolk
- Jenork/Jenolk
- Xenork/Xenolk
- Genoruk (a direct result from a translation tool)
- Genoluk (manually changing the final consonant based on the above)

Those were roughly the kinds of results I kept getting.

Even after trying really hard and changing individual letters one by one, the results were…
- ジェノーク
- ジェノック
- ゲノルク
- ゼノーク/ゼノルク
※I intentionally left this in Japanese.
Hmm… What are we supposed to do about this…? (lol)

Well, I can understand why a name starting with “Xe” might be pronounced with a “Ze” sound, but the first two were a bit disappointing! (lol)

Maybe the “l” sound is being interpreted differently, somewhat like the pronunciation of “folk,” causing it to come out as “nork.”

In the end, I settled on “Genoluk.” Both translation tools rendered it as “ジェノルク,” and when I checked with AI, it also said the spelling was perfectly acceptable.
However, I was told that the name has a distinctly JRPG-style feel. Since it originally came from the Japanese version, I decided that was acceptable.

Although both translation tools gave me “ジェノルク,” I feel that people in some regions might pronounce “Genoluk” more like “Jenoluck.”

But if we worry about every possible pronunciation, we’ll never get anywhere. Since it’s not too far from the intended pronunciation, we decided it was good enough.
I don’t think it’s possible to get everyone to pronounce a name exactly the same way. As long as it isn’t too far off, that should be enough.

If I ever reach a point where I really can’t find a solution, I might consider asking a professional translator for help.
🌎 UI Issues Caused by English Localization

I expected this, but there are places where Japanese can express something briefly using kanji, while the English translation ends up being much longer.

We knew we’d run into this problem somewhere along the way…

Thinking about it now, perhaps I should have designed the UI and names with both Japanese and English in mind from the very beginning.
For example, let’s take a look at this confirmation screen during character creation.


Here’s an example where the text actually extended beyond the UI box. I solved this by adopting the alternative suggestion, “Undo Change.”

We also confirmed that both expressions convey the meaning of “revert the change” when translated, so the intended meaning is preserved.
We’ve solved this issue for now, but I’m sure the quest-related UI will need some major changes.
🌎 Localization Involves More Than Just Translation

This is something I learned while translating class names.
The Gacha character “Leesha,” who starts as a Hunter, eventually becomes a “Mythic Huntress.”
Since she’s female when you first encounter her, we chose “Huntress” for her initial class name.

And here’s what AI pointed out to us.
“Mythic Huntress” is an excellent name if the character is female.
However, since your game allows character customization, players can also choose a male character.
In that case, “Huntress” would no longer be appropriate because the word specifically refers to a female hunter.
Tool used: ChatGPT

Apparently, keeping the name “Huntress” for a male character could feel strange to English-speaking players…
We could technically add an extra entry to the database and handle the name change internally, but…

Honestly, we’re still considering whether we should actually do that…

Encountering issues like these has made me realize that creating an English version involves much more than simply translating the text.
📢 Follow and Support

If you’d like to support what DiceCreation does going forward, following us on social media means a lot and keeps us motivated to post!

I’d be so happy if you followed us. We’ll keep the updates coming quickly, so please do~!

The latest news from DiceCreation is published on our official site.
Site updates and announcements are also posted on the official social accounts below.



