The codec for BrushableBlock misspells the word 'completed' as 'comleted' in the field `brush_comleted_sound`. The field should be named `brush_completed_sound`.
This can be seen in the `blocks.json` datagen report, under Suspicious Sand and Suspicious Gravel.
Attached is a screenshot taken from a mapping tool, showcasing this misspelling in the code, as well as a screenshot of this misspelling in the datagen report.
Attachments
Comments 10
This will have an impact on datapacks in the coming weeks when these are further developed. I am reporting ahead of time to ensure that doesn't happen!
Please try to know what you're talking about before saying this issue is invalid.
If it actually has an impact, right now, then it is valid, not "possibly soon", now.
See all these issues: https://bugs.mojang.com/browse/MC-253951?jql=project%20%3D%20MC%20AND%20resolution%20%3D%20Invalid%20AND%20text%20~%20%22gameplay%20impact%22 all closed, by mojang or mods, for having no gameplay impact.
So you want me to wait until this codec is used to generate a JSON file with the typo before reporting the issue, despite having the ability to prevent the issue now?
If someone saw your fusebox sparking and emitting smoke, and reported it to you, would you say "sorry mate but it hsan't actually caught fire and exploded yet, so I don't care"?
There's a major difference between a typo and a safety hazzard... and even then, bad example as the sparkling and smoke is a resulting effect of the issue.
I'm not the one that made this rule, mojang did. These kinds of things are not accepted bug reports per their actions.
Okay, that was an overly ridiculous analogy, but my point is this isn't just a typo in the code, but a typo that will be visible in the JSON files of datapacks in the very near future.
And I think instead of minimodding this issue, perhaps you should leave it to the actual moderators and Mojang themselves to decide the validity of the issue.
If they deem it invalid, then I guess I'll just... wait until the JSON file is generated and submit an issue saying the typo exists in that JSON file... which is exactly the same issue as this.
There are cases of Mojang fixing issues that didn't have impact in vanilla game (yet), so this issue report is fine tbf, let the devs decide™
As mentioned earlier, we only accept bugs that affect gameplay. If you can't identify how this impacts vanilla gameplay, it won't be considered a valid issue.
@unknown: Let's keep the bug tracker a friendly and respectful place for everyone. We appreciate your contributions and value each member's input. Remember, @unknown is a long-term member and former moderator, which means he's well-acquainted with the rules and guidelines.
Sorry, but this has no gameplay impact.
Only issues that have impact on the game or resource/data packs are considered valid reports. A typo in the code is not a valid report, unless it results in observable effects in-game.