Ben Kennish
- Bennish
- JIRAUSER663057
- Europe/London
- Yes
- No
Hello Ben Kennish. We use the comments section as a place for supplying more information regarding the bug in question, not actually for discussing the bug. In other words, the purpose of the comments section of a ticket is not to discuss its outcome; please refer to the Bug Tracker Guidelines for more information regarding this.
If you want to initiate a discussion about a bug or need to report someone, take the discussion outside of the bug tracker (see FAQs), do not comment directly on the bug tracker.
As for the "Won't Fix" resolution, explanations regarding the reasoning behind these choices aren't always provided. Mojang does consider this to be a bug but has chosen not to fix it. Once again, please do not comment on this ticket; you are welcome to talk about this further outside of the bug tracker. Thanks! ![]()
How is this "resolved"? I see it's been marked as such by "[Mojang] Moesh" with "Won't Fix" but with no comment or explanation. I am also getting this on my server since upgrade to 1.19.3 and the server lags badly for about a minute when it happens. Even if this only happens once per chunk generated pre 1.19.3, isn't this still a bug and worth resolving by actually fixing the bug?
I don't understand the purpose of the comments section for a bug then, Avoma. My previous comment (asking why this has been marked as resolved and won't fix) directly relates to the bug so why post it on Discord or reddit instead of as a comment on the bug?
Having this problem on my 1.20.1 world. (SMP hardcore.) This bug report is four years old today. UnHappy Birthday bug! 😏