MC-251815"Facing" property on paintings renamed "facing", breaking scripts
The "Facing" property for a painting has changed name to "facing", which just changes the initial letter's case.
It also breaks every script in the world that uses the property.
(And, while we're at it, the new 'variant' property uses lowercase, where most properties are uppercase.)
To me this requires a few things to fix:
- Change the property name back (the minimal fix)
- Make the property name matching case insensitive so the user doesn't have to remember case (should be relatively simple)
- After #2, make all properties use CamelCase so they all look the same.
Created Issue:
"Facing" property on paintings renamed "facing", breaking scripts
The "Facing" property for a painting has changed name to "facing", which just changes the initial letter's case.
It also breaks every script in the world that uses the property.
(And, while we're at it, the new 'variant' property uses lowercase, where most properties are uppercase.)
To me this requires a few things to fix:
- Change the property name back (the minimal fix)
- Make the property name matching case insensitive so the user doesn't have to remember case (should be relatively simple)
- After #2, make all properties use CamelCase so they all look the same.
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
is duplicated by
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
![[Mojang] MimmiB](../../../data/avatars/users/18949.svg){kind=small}
![[Mod] Jarl-Penguin](../../../data/avatars/users/92849.png){kind=small}
is duplicated by
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
Thank you for your report!
We're resolving and linking this ticket forward as a duplicate of MC-251815, as that ticket contains more detailed information and/or has already been triaged by Mojang.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
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.
Nevermind, I just realizes that this is a dupe of MC-251815.
I don't think minecraft makes any guarantees about NBT backward compatibility besides world upgrades
Um, maybe so? I don't know. But what is the advantage of this change? Who is better off because of it? I can certainly cite folks who will be worse off, starting with me, but I am surely not the only person who uses stored commands from command blocks and functions. So that's on the negative side. What's on the positive side?
Or should they just randomly change attribute names each release? And if not, why not? When you answer that, you have answered why this should be fixed.
The advantage is that it is more consistent and intuitive for people using it in the future.
Mojang started to use snake case for NBTs, so the change itself could be intentional. Pack format is already raised (making old packs listed as incompatible) too.
As others have mentioned, this isn't about backwards compatability - the pack format has already been bumped. Instead, this is simply reporting an unannounced change.
Yes, MMK21, I agree.
But also, if mojang is going to change property names to a common case approach, that makes it much, much more important and useful to do property lookup ignoring case. If they did that, then a case change would break much less.
We make no guarantees about the internal formats of NBT. This bug tracker is for bug reports, not for requests for format changes.
Ah, so if someone changed the case of every property at every release using RanDoM CAPiTAlizATioN, that would be OK?
This is only a "request for format change" if you ignore the reason for the request, which is to unbreak something that got broken. Where I've worked, that would be bug (maybe a low priority one) unless the change was intentional. You may not guarantee the format, but you should guarantee that you won't make changes capriciously. This feels capricious, accidental even. Either there's a reason for the change, and it's not a bug, or there isn't, and it is a bug.
TBF, the commands that spawned in paintings already broke anyways, with the motif changes; and no, NBT naming is not something Mojang considers worth fixing, except when a typo is involved; you're messing with the save format of the game, and that may change at any moment, without prior notice if the devs feel like it.
The pack format of data packs is exactly for this purpose, preventing broken packs from loading in with newer versions, possibly breaking everything.