mojira.dev

JoePCool14

Assigned

No issues.

Reported

MC-256906 Using a Glow Ink Sac on hanging signs does not grant Glow and Behold! advancement Duplicate REALMS-3009 When on a Realm, the pause menu displays name of world as "world" instead of the name of the Realm. Duplicate MCPE-63280 Minecraft on Nintendo Switch crashes when saving with error "The software was closed because an error occurred." Duplicate MC-132911 Italic hyphen appears strange / broken Duplicate MC-131367 Fullscreen resolution in Video Settings is incorrectly capitalized Fixed MCPE-26845 Dirt Path not treated as solid block Confirmed MCPE-23448 Sign text displayed too low Cannot Reproduce MCPE-23434 [Resolved] Realm name cutoff when opened in settings Cannot Reproduce MCPE-20065 [Resolved] No "Delete Realm" button Invalid MCPE-19571 [Resolved] Breaking a door will remove the block above it. Cannot Reproduce MCPE-19566 Diamonds to you achievement is broken. Cannot Reproduce MCPE-19385 [Duplicate] Color codes glitch names of Realms, Can't change name of Realm Duplicate MCPE-19384 [Resolved] Commands printing line by line, multiple times. Duplicate MCPE-19292 Cannot change name of Realms if color codes were used in the name originally Cannot Reproduce MCPE-15363 [Resolved] Signs won't allow for inputting text Duplicate MC-98982 [Resolved] Small gray bar on left side of open chat Works As Intended MCPE-13678 [Resolved] Double flowers duplicate if destroyed with the top block Duplicate MCPE-13632 [Resolved] Options Menu has Gray Line on Bottom Cannot Reproduce MCPE-10547 [Resolved] Color on Signs (in GUI) do not function correctly. Fixed MCPE-10545 [Resolved] Signs (in GUI) do not display correctly. Works As Intended

Comments

Updated the affected versions to add 1.16.100 and 1.16.200.56 Beta.

Also on Nintendo Switch, I can confirm no images load anywhere. This bug also affects version 1.16.1.

Just chiming in that on 1.16.0 on the Switch, I cannot upload worlds to my Realms. Every time I try, I get the same "An error has occurred." that many other people have gotten. I hope this issue is fixed very soon, otherwise I expect some days to be compensated back to me, since I can't use the Realm I just bought in the way I need to!

This ticket should absolutely remain open. This bug still exists in 1.15.2 as well as the latest snapshot for 1.16 as of writing, 20w09a. I have attached a few screenshots to better visualize the changing color rendering as you rotate the sign. East-west signs look fine. North-south signs look darker and the text appears harder to read.

 

@violine101 - It's worth mentioning signs may also be dyed in Creative mode. Dying signs is a vanilla feature, therefore it is worthy of receiving support for related issues or bugs.

Update: I was playing on my Switch after updating to 1.14.30, and lo and behold I had the game crash on me not once, but twice in just the span of 45 minutes. One was when I tried to open the settings menu, the other just after I clicked save and quit in my world. Please add 1.14.30 to the list of affected versions for this bug.

@Dave D - That's interesting. I might just have to try that myself. For me, my game usually crashes when I'm saving and quitting. Sometimes it is successful, sometimes not. Even worse, sometimes when it crashes I lose some progress (sometimes upwards of a half hour, which is unacceptable!). But the auto-backup thing is a good suggestion, and I'll try turning that off to see what's going on.

Please Mojang, focus on game-breaking glitches like this before implementing any new features!

@Seb - Not really. Lapis and Redstone ores do not share the textures of the other ores. I'm personally fine with this, and would call this intentional.

I've been getting this issue too on 19w13a, brand new world. Win10, Intel Integrated Graphics.

Just tried it, color codes didn’t even work at all when choosing the name of my Realm. Not sure if this is intentional.

Agreed. The sound is absolutely awful in 1.13, and will definitely turn people away.

I've still got a lighting issue in 1.13-pre8. The original glitch that I posted about earlier is fixed, however, when I removed all torches from this mine, it still appears bright as day down there.

[media]

I'm not sure if this is relevant to this bug or not. Either way, there is still an issue here.

Still affects 1.13-pre8.

Confirmed still broken on 1.13-pre7.

Might as well comment about my experience.

Lighting appears to be massively broken in 1.13-pre6. I was working on a strip mine, digging down within the side of a mountain, and no matter how far down I dug, it was still as light as day down there.

Night fell, and now, there's no moonlight whatsoever. And to add to that, I placed torches down in the mine and this is the result: 

[media]

So, in essence the lighting engine is completely broken in 1.13 at the moment, at least for me.

I just ran a quick test to ensure that I'm not going crazy.

On both Java Edition 1.12.2 and Bedrock Edition 1.4.2 on my Windows 10 PC, I created new worlds, set the time to day, turned off daylight cycle and created a 6x6 square of Dirt above a flat Grass Plains biome. I started a timer, and at just around 7 minutes, Java Edition was already finished spreading. Meanwhile in the same amount of time, Bedrock hadn't even reached the halfway mark (16 of 36 blocks).

Very clearly, the speed is still much slower than what it needs to be. It isn't unreasonable, but it can make certain builds very frustrating when you don't have access to Silk tools.

Hope this can be looked into by Mojangstas. 🙂

Wow, it's been a while since this issue's been updated.

After playing Bedrock again on my Survival Realm for quite some time, and struggling to build with Path blocks, I'm realizing that grass spread is still slower than on Java Edition. Once again, this is a pointless change since having grass is more-or-less just an aesthetic thing. But, then again building is important to Minecraft, so I would think having proper grass spread would be important.

I know they claimed to have previously fixed this, but it's only been a small improvement and still isn't quite there.

So, I'm going to say that I can confirm this on 1.4.2.

99% sure this was a feature.

Also can confirm on my Xbox One S with 1.2.6.

Yes, it still affects the latest version.