--LJL--

Actually, you can check the details of MC-309839, and you should be able to find out the reason.

You're right, I completely missed your point earlier. I re-read your reply and now I understand — this isn't a bug in the code, it's just that the translation hasn't caught up with the source string change yet, and it'll be fine in the next snapshot. I shouldn't have pushed back on this. Sorry about that, and thanks for being patient with me.

I want to point out that this issue was already acknowledged by ManosSef in the original report (MC-309819).

On July 10 at 18:22, he replied:

"The affected string was changed to now use a placeholder variable when it didn’t have one before... The issue will be automatically resolved in the next snapshot for all languages that have made the appropriate change to their translation of the string."

That reply is in MC-309819, not in this new report. I'm mentioning it here because this new report (MC-309839) was submitted as a more organized version of the same issue, and it seems the Triage Team may not have seen ManosSef's confirmation.

If the fix is already in the source template as ManosSef confirmed, then this issue is effectively resolved for future snapshots. I just want to make sure this doesn't get lost in the process.

Original report: MC-309819

Thank you."

I would like to clarify the background of this report, because there seems to be some confusion.

This is a re-submission of MC-309819. That original report was initially closed as Invalid by ManosSef, who said it was a translation issue.

After I provided evidence from 10 languages across 8 language families, ManosSef replied on July 11 (see below) and acknowledged that the source string was missing a placeholder. He confirmed that the issue would be resolved in the next snapshot.

However, today the Triage Team and bl4ckscor3 closed this new report (MC-309839) as Invalid again, stating that translations need to be updated on Crowdin.

These two conclusions seem contradictory. The original report (MC-309819) was closed, and now this new report (MC-309839) is also closed. If the source template has been fixed as ManosSef said, that's great. But if the report is closed as Invalid, who is tracking whether the translations actually get updated?

I'm not trying to be difficult — I just want to make sure this issue doesn't fall through the cracks.

Original report: MC-309819

Thank you for your time."

I would like to respectfully challenge the decision to close this as Invalid.

On July 11, ManosSef confirmed that the source string was missing a placeholder and said the issue would be resolved in the next snapshot. Now, bl4ckscor3 and the Triage Team have closed it as Invalid, stating that translations need to be updated on Crowdin.

These are two contradictory conclusions about the same issue.

My evidence shows that 10 languages across 8 language families all exhibit the exact same missing variable. This is not a translator mistake — it's a source template issue, as ManosSef already acknowledged.

If the fix is already in the source template, then the next snapshot should include the updated translations. But if the report is closed as Invalid, who is tracking whether the translations actually get updated?

I'm not asking for special treatment. I'm asking for a consistent answer: is this a valid bug that Mojang will ensure gets fixed, or is it entirely out of your scope?

Thank you for your time."

Thank you for confirming it's a source template issue and fixing it. Glad to see the evidence helped.

This is not a translation issue. This is a source template issue.

I have tested 10 languages across 8 language families. All of them show the exact same error: the flight duration number is missing from the tooltip.

10 languages, 8 language families, covering multiple continents. The error is identical in every single one: the duration variable is absent.

If this were individual translator mistakes, the errors would be varied and random. But all 10 languages share the exact same missing variable. That is statistically impossible as a coincidence.

The only explanation is that the Crowdin source string is missing the duration variable placeholder (e.g. {duration} or %s). This is not a problem for translators to fix. It is a problem for Mojang to fix at the source.

Please check the Crowdin source template and reopen this issue.

Thank you.

I would like to request reopening this issue.

I have now tested this in 9 languages across 8 language families. ALL of them have the same problem — the flight duration number does not appear in the tooltip.

Summary of affected languages:

9 languages, 8 language families, spanning Europe, Asia, Africa, and Southeast Asia — all exhibiting the exact same error: the duration variable is missing after "Flight Duration:".

If this were individual translator mistakes, the errors would be random and varied (typos, different phrasing, etc.). Instead, the error is identical across all 9 languages.

The only logical conclusion is that the Crowdin source string is missing the duration variable placeholder (e.g. {duration} or %s). This is a source template issue, not a translation issue.

Please check the Crowdin source string and reopen this report accordingly.

Thank you.

In addition to Simplified Chinese, this phenomenon also occurs in English (UK).