ClassCastException, whic wass used to make update supression, what is actualy became feature and not a bug, no longer work.
Linked issues
duplicates 1
Comments 7
Thank you for your report!
We're tracking this issue in MC-265132, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
-- I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Dhranios, tnt duping, bedrock breaking, end portal frame breaking, piston releases the block, nether roof portal linking, stacking raid farms - all it become feature after become commonly-abused-bugs. Double standards?
Not a feature, not a feature, not a feature, that one is, unclear (portals linking to other places is not a bug, nor is building on the nether roof, but them linking to above-height portals was never declared a deliberate feature), that one is.
Just because they're not being patched immediately doesn't mean they're by design. CCE wasliterally throwing an exception, there's no defense to calling that a feature.
Dhranios, "feature" it's not allways that "mean they're by design". Actualy "mean they're by design or bug which newer will be fixed in any reason, usualy because developer think it shouldn't be fixed". CCE can't be feature, but effect of CCE can. Tnt dupping wass eventualy fixed in some snapshot and than was removed back. To fix bedrock breacking just ONE line must be deleated. Both of this bugs pathed in custom cores. So, if it not feature, why it's not fixed for YERS? And special for you: feature mustn't be declared as a feature. And there is no need to talk about the status of the report, you already said that the funnel in F3 will not be fixed, because the status "works as intended" to save traffic.
This is not the place to ask for re-introducing that though.
And no "issue that never got fixed" does not make it a feature, no matter how much you call it a feature, it'll only be a feature if the developers declare it as such (such as listing it in a changelog).
The TNT fix got reverted as said fix was actually dependent on java version among other things, and only half-worked, probably breaking more in the process. The fix being undone doesn't mean the issue is not an issue. (And as for bedrock breaking, it's relatively harmless and not a high priority in the slightest. No matter how trivial, if it's not a priority, they're nnot going to look at it unless there's a more pressing reason to look at that part of the code.)
Duplicate of MC-265132, never was a feature, don't confuse commonly-abused-bugs with features.