Typo in the Battle of Leyte Gulf mission - "Battle off Engano"

[Malum0ne]

I wasn't sure where to post this, so I'll move it or admin can move it if needed.

Battle off Engano: Mission 2:

Reads: "Destroy an enemy ship from a distance of at least 10 km and survive the battle."
I completed this and didn't get credit for it. So, I contacted Player Support about it and they informed me that it was a typo and should Read:
"Destroy an enemy ship from within the 10 km distance and survive the battle”.
Why they haven't corrected it or even announced it, I don't know.
Maybe they did and I just missed it.

Edited October 29, 2024 by Malum0ne

[Wolfswetpaws]

3 minutes ago, Malum0ne said:

I wasn't sure where to post this, so I'll move it or admin can move it if needed.

Battle off Engano: Mission 2:

Reads: "Destroy an enemy ship from a distance of at least 10 km and survive the battle."
I completed this and didn't get credit for it. So, I contacted Player Support about it and they informed me that it was a typo and should Read:
"Destroy an enemy ship from within a distance of at least 10 km and survive the battle."
Why they haven't corrected it or even announced it, I don't know.
Maybe they did and I just missed it.

My game went through an update process, this morning.

But, because I've completed the Battle Off Cape Engano missions days ago, it's no longer listed in my missions menu of my Port screen.
So, I can't check to see if the wording was revised with today's update.

[Malum0ne]

Yeah, I'm running a bit behind. I haven't been on as much as I usually am. Hoping to get caught up quickly.
My game just updated and it's not been changed.

[Wolfswetpaws]

👍

[HamptonRoads]

It still reads "at least 10km," but I get the feeling that if they tried to change it now, it would screw up something else.  We'll have to see if they append it with the new patch.

[Sambo_Cigars]

6 hours ago, Malum0ne said:

I wasn't sure where to post this, so I'll move it or admin can move it if needed.

Battle off Engano: Mission 2:

Reads: "Destroy an enemy ship from a distance of at least 10 km and survive the battle."
I completed this and didn't get credit for it. So, I contacted Player Support about it and they informed me that it was a typo and should Read:
"Destroy an enemy ship from within the 10 km distance and survive the battle”.
Why they haven't corrected it or even announced it, I don't know.
Maybe they did and I just missed it.

I figured out that this was the intended meaning when I destroyed a ship from 11-12 km, survived the battle and yet the mission remained unfinished.

This is just unacceptable sloppiness on WG's part.

[MidnightPhoenix07]

They announced it on discord and reddit when it was first brought up a week ago, but said they were “currently unable to update the mission description in-game.” Whether that’s simply a technical reason based on how the missions are coded in the game, or a concern that something else might break if they try to fix it with its own update.

That being said, I’m surprised they didn’t at least put a note in the news article for the event, since not everyone is on the discord server or subreddit. 

[Nevermore135]

17 hours ago, Wolfswetpaws said:

My game went through an update process, this morning.

But, because I've completed the Battle Off Cape Engano missions days ago, it's no longer listed in my missions menu of my Port screen.
So, I can't check to see if the wording was revised with today's update.

The 10/29 update was simply the regular occurrence of WGC downloading the new patch. I would expect it to be changed in the new patch, though, because it is a very simple fix to a line of text.

8 hours ago, MidnightPhoenix07 said:

They announced it on discord and reddit when it was first brought up a week ago, but said they were “currently unable to update the mission description in-game.” Whether that’s simply a technical reason based on how the missions are coded in the game, or a concern that something else might break if they try to fix it with its own update.

I suspect it was a purely financial decision vs. anything based on technical considerations. Building, testing, and pushing out an update costs money, and with the the only effect being player confusion regarding a mission that is ultimately performing as intended and is still available for another month I can see someone deciding to leave it be for the week leading up to the release of the new patch.

[Admiral_Karasu]

1 hour ago, Nevermore135 said:

The 10/29 update was simply the regular occurrence of WGC downloading the new patch. I would expect it to be changed in the new patch, though, because it is a very simple fix to a line of text.

I suspect it was a purely financial decision vs. anything based on technical considerations. Building, testing, and pushing out an update costs money, and with the the only effect being player confusion regarding a mission that is ultimately performing as intended and is still available for another month I can see someone deciding to leave it be for the week leading up to the release of the new patch.

Nonetheless, this is a major flaw because not every player necessarily is on Discord, Reddit, or on DevStrike! (feeling obliged to tout or own horn) as @MidnightPhoenix07 pointed out. It's true that they probably can't pull off a major patch up on a short notice, but we've seen WG do some hot fixes really quickly when they've spotted something that is inconvenient for them which leads me to suspect it should have been technically feasible to hot fix this, though I don't have the expertise to know that for certain. Nonetheless, putting up a news item on the official World of Warships game site and in the game client/WGC would have been the bare minimum thing for them to inconvenience themselves instead of letting an unknown number of players get frustrated over trying to complete this mission when the mission description is wholly misleading.

Edited October 30, 2024 by Admiral_Karasu
Admiral_Canttype

[Nevermore135]

49 minutes ago, Admiral_Karasu said:

Nonetheless, this is a major flaw because not every player necessarily is on Discord, Reddit, or on DevStrike! (feeling obliged to tout or own horn) as @MidnightPhoenix07 pointed out.

I agree. I’m not defending WG’s handling of this.

49 minutes ago, Admiral_Karasu said:

It's true that they probably can't pull off a major patch up on a short notice, but we've seen WG do some hot fixes really quickly when they've spotted something that is inconvenient for them which leads me to suspect it should have been technically feasible to hot fix this, though I don't have the expertise to know that for certain.

We’ve seen WG hot patch the technical details of missions (adding game modes and even changing requirements/fixing bugs) before. The thing is that the mission itself doesn’t need to change, because it is working correctly. What’s wrong is just the description (at least in English) which is ultimately just a bit of UI text and shouldn’t interact with any “moving parts” of the game. The most plausible reasons it wasn’t fixed over the last week is that either the code doesn’t allow them to update the description without erasing progress on the mission/chain or, as I said above, it just wasn’t deemed cost-effective to push a patch to fix what is ultimately a UI error on what might be only a single language version of the client. I’m curious if the mission description has been changed with the new update now active on NA, because if it has been that suggests the latter is the case vs. the former.

49 minutes ago, Admiral_Karasu said:

Nonetheless, putting up a news item on the official World of Warships game site and in the game client/WGC would have been the bare minimum thing for them to inconvenience themselves instead of letting an unknown number of players get frustrated over trying to complete this mission when the mission description is wholly misleading.

Yes, there is no good reason there shouldn’t have been an announcement on the main site/in the relevant news article by now, especially if they don’t plan to fix it. Perhaps the thinking is that the text will be fixed with the update and then everyone at WG can pretend this never happened (wouldn’t be the first time). /s

Edited October 30, 2024 by Nevermore135