Seconded
I've had this issue for so long and it's made me not want to use the creator at all because I know it'll corrupt if I breathe too heavily.
How has Microsoft not figured out a way to back up character creator?
[RANT START]
Why is Bedrock so buggy that Switch has a random chance to just not log you in and you just have to hope it works?
Why is Bedrock so buggy that mobile has a chance to just stop me from logging in unless i'm screen recording?
ik this is unrelated but the next bedrock update should entirely focus on fixing usability issues like these.
and revamping switch entirely, as is it's almost impossible to even play a lot of the time for seemingly no reason
[RANT OVER]
The words "biscuit" and "cookie" aren't interchangable in UK English. We almost always refer to the chocolate chip kind as chocolate chip cookies, just like Americans would. I feel this is an error in Java Edition and I was just about to file a bug report about it.)
TL;DR the item name is incorrect in Java Edition anyway
(source: I'm British)
I can't even get into PS4 Edition now. It crashes but without an error handler right when it normally switches. I wish I could just get a rollback
UPDATE: Works again after a reinstall.
Loads fine for me, either your internet sucks or the marketplace is too eager to define a connection as unusably slow and give up.
The bigger bug here is probably that the game even lets you place signs on cacti in the first place
In the case of the polar bear, it's cold. So it probably makes more sense for its food to drop raw even if it was burning. However zombies aren't cold. I'd say the zombie being on fire would warm the potato up quite a bit, would you?
This is a bug IMO.
Generally, when you want to colour some text, you would still like to read it.
If you make it black, and then it just so happens that a drop shadow is being put behind it that makes it unreadable, it's not your fault.
It's the fault of whatever put that drop shadow there. They shouldn't have tried to put a black shadow behind black text. If that didn't happen, the text would be just fine.
For this reason, I consider this a bug. It's not technical per se, but it's erroneous enough that I would still call it a bug and not a feature request.