Wuthering Waves Can't Keep Doing This...

preview_player
Показать описание
Wuthering Waves Can't Keep Doing This...
Come play Genshin Impact with us and join the discord and streams on twitch! Watch on twitch to get channel points so I can summon on YOUR account!

▼▼EXPAND ME▼▼

DON'T FORGET TO LIKE, COMMENT AND SUBSCRIBE!

#wutheringwaves #GenshinImpact #BranOnline
Рекомендации по теме
Комментарии
Автор

At this point, Kuro should sign up for the gwr of "most translation errors in a single patch" LMAO😂

McNugge.
Автор

Yeah, i was surprised when i got reward:"Obtain 30k points"by having 21 or something, making mistakes with numbers are wild and this for some reason are still here

Dima_Vovk
Автор

"mistranslated" numbers IS CRAZYYYY
I love kuro but they need to stop thissss

Aoharu
Автор

PGR is almost 5 years old but that problem never goes away. It's like an incurable disease that attacks Kuro. I'm very sure that things like that will happen again in future versions. We are used to it but we also hope they are at least a bit more professional in handling Wuwa.

acircle
Автор

Ridiculous fact: male rover voiced red riot from mha.

chimelxatrindad
Автор

I'm not suprise honestly, kuro always has localisation mistake in their game even in pgr, it's very good to immediately report bcs sometimes it's just so ridiculous how bad their localisation are ..

rahoais
Автор

Its fhe same as the upcomming event tomorrow. It says 420 asterite on ingame news but it says 800 on their social platform

reedsad
Автор

Mistranslate numbers, now thats something new

pancakes
Автор

Reason why these numbers are "Mistranslated" is because the "Mistranslated" numbers are the old scores required for said rewards, these rewards were revised prior to the event releasing, but someone in the translation teams forgot to change the required scores from 140, 000 (Old) to 90, 000 (New). Still bad mistake, but just wanted to give an explanation as to why it happened (It also happened due to just how much piles of work the devs have due to Kuro deciding to launch the game in such a messy state, as well as having to rush 1.1).
Also to anyone having troubles with this event; you can reach 90, 000 points day one of this event because of the damage multiplier you get from the first three levels, you don't even need high level characters, just use the trial characters and keep switching characters when your concerto bars are full.

heresywithana
Автор

I think its a last second change that they forgot to put on english. most likely it was 140k at the test of the event but last seconds devs lowered it but forgot to also change it on english.

Myosotis
Автор

all i can say is that they need to hurry up on their localization department, i dont want them to repeat the japan incident especially with the upcoming banners

ozoahameg
Автор

As a game developer, I have no idea how this even happens. things like values in displays like that are usually saved in a variable so it can be flexible, but since theres a mistake in english but not in the original or jp this means this text is hard coded, which is incredibly unprofessional

entegi
Автор

How tf they mistranslate fricking numbers!! 😭😭

krishleysahani
Автор

At this point they are intentionally making mistakes to have the excuse to compensate the players

FormerEmiliaBestWifi
Автор

they probably changed the numbers last minute and forgot to notify the EN localization team

Kusada
Автор

At this point it feels like lack of editing in general, not just localization. I have so many subtitles that have spelling errors and/or don't match what's being said out loud

halleycat
Автор

Junior dev: Let me just push this hotfix real quick (5 minutes before the event)
Senior dev: LGTM, approved, merged.

lucasteo
Автор

Well the famous quote “its over 9000” was a mistranslation

rankfrombottom
Автор

The most diabolical localization error I've seen is the Your and You're. Still gives me nightmares

reincarnatedtobuildaharem
Автор

Man it's just CRAZY to me as a programmer that the text display isn't somehow properly referencing the variable they're trying to display. Like this could have been so easily avoided.

fredxu