ZephaniahNoah
- ZephaniahNoah
- zephaniahnoah
- Europe/Stockholm
- Yes
- No
MCPE-15457
MC-111585
0.15.0 is fine. 0.15.1 st
yretches two edges of all blocks. It' very subtle buther annoying once noticed. I'm using a kindle fire 5th gen. I'm using the city pack in this photo.0.15.0 is fine. 0.15.1 stretches two edges of all blocks. It' very subtle but super annoying once noticed. I'm using a kindle fire 5th gen. I'm using the city pack in this photo.
0.15.0 is fine. 0.15.1 and 0.15.2 stretches two edges of all blocks. It' very subtle but super annoying once noticed. I'm using a kindle fire 5th gen. I'm using the city pack in this photo.
32xcitytexturepackstretches two edges of all blocksAl 32x textures stretch
All 32x textures stretch
0.15.0 is fine. 0.15.1 and 0.15.2 stretches two edges of all blocks. It' very subtle but super annoying once noticed. I'm using a kindle fire 5th gen. I'm using the city pack in this photo. This happens to any 32x pack. Including JohnSmith and Faithful. This is a miserable terrible bug that's been around for almost a month! Since June 26, release date of 0.15.1...
0.15.0 is fine. 0.15.1 and 0.15.
2stretches two edges of all blocks. It' very subtle but super annoying once noticed. I'm using a kindle fire 5th gen. I'm using the city pack in this photo. This happens to any 32x pack. Including JohnSmith and Faithful. This is a miserable terrible bug that's been around for almost a month! Since June 26, release date of 0.15.1...0.15.0 is fine. 0.15.1, 0.15.2 and 0.15.3 stretches two edges of all blocks. It' very subtle but super annoying once noticed. I'm using a kindle fire 5th gen. I'm using the city pack in this photo. This happens to any 32x pack. Including JohnSmith and Faithful. This is a miserable terrible bug that's been around for almost a month! Since June 26, release date of 0.15.1...
0.15.0 is fine. 0.15.1, 0.15.2 and 0.15.3 stretches two edges of all blocks. It' very subtle but super annoying once noticed. I'm using a kindle fire 5th gen. I'm using the city pack in this photo. This happens to any 32x pack. Including JohnSmith and Faithful. This is a miserable terrible bug that's been around for
almosta month! Since June 26, release date of 0.15.1...0.15.0 is fine. 0.15.1, 0.15.2 and 0.15.3 stretches two edges of all blocks. It' very subtle but super annoying once noticed. I'm using a kindle fire 5th gen. I'm using the city pack in this photo. This happens to any 32x pack. Including JohnSmith and Faithful. This is a miserable terrible bug that's been around for over a month! Since June 26, release date of 0.15.1...
In versions 0.15.0 - 0.15.2 redstone acts normally. But in versions 0.15.3 - 0.15.9 redstone connects directly to pistons as shown in
the secondscreenshot. This doesn't happen in Minecraft PC because if it did it would make redstone less compact. If you wanted to run a wire alongside a piston it would need a one block gap or else it will dirupt the piston. You might think this is good but most of the time it causes many problems when building with redstone.In versions 0.15.0 - 0.15.2 redstone acts normally. But in versions 0.15.3 - 0.15.9 redstone connects directly to pistons as shown in one of the screenshots. This doesn't happen in Minecraft PC because if it did it would make redstone less compact. If you wanted to run a wire alongside a piston it would need a one block gap or else it will dirupt the piston. You might think this is good but most of the time it causes many problems when building with redstone.
In versions 0.15.0 - 0.15.2 redstone acts normally. But in versions 0.15.3 - 0.15.9 redstone connects directly to pistons as shown in one of the screenshots. This doesn't happen in Minecraft PC because if it did it would make redstone less compact. If you wanted to run a wire alongside a piston it would need a one block gap or else it will disrupt the piston. You might think this is good but most of the time it causes many problems when building with redstone.
I was just playing then this black stuff appeared in the sky then my player started rapidly moving back and fourth as if stuck in a ghost block. Then the game froze.
I was just playing then this black stuff appeared in the sky then my player started rapidly moving back and fourth as if stuck in a ghost block. Then the game froze.
EDIT: This has happened to me three other times before
I was just playing then this black stuff appeared in the sky then my player started rapidly moving back and fo
urth as if stuck in a ghost block. Then the game froze.
EDIT: This has happened to me three other times before
The search function doesn't work. Please fix it and I will use it. Also this is not a duplicate as it states that USB mice and Bluetooth mice aren't working properly.
What!? This isn't a duplicate of that bug report! Nor is it resolved.
Am I going to have to make a duplicate of this report? Someone not very intelligent marked it as resolved. This bug was never fixed and still exists in PE 1.0
@PlantSeed Those are called tile entities.
2021-11-17_12.42.09.png
Visible chunk border in windswept hills
Its very quick! And its hard to take a screenshot of. But I'll make a screen recording.
Here is the video: https://youtu.be/QgNczRGxAig
I meant to say, "stretches"
Ok. I edited it. The mobile site wouldn't let me do it.
Does nobody see this uglyness?! This putrid festering glitch!? I BEG YOU MOJANG! PLEASE FIX THIS BUUUUUUUUUG!!!!!!!!!
I already tried three 32x packs when I discovered the bug. That's what it says in the description. But it's fixed now in 0.15.4
This bug still exists in 0.15.8... When will MOJANG ever fix this?
It seems like this may be a good idea to make redstone easier but there is a reason that PC doesn't do it this way. It makes contraptions less compact. It makes redstone harder to use. Please fix this! I will be posting this to the forums.
This bug exists in Minecraft PE 1.0...
What about skins?
Rare? That's very subjective. Me and many people have very large worlds and see this often. I've seen this issue frequently in my tests.
Why is the resolution set to, "Won't fix"? You guys are probably super busy and have other things to prioritize. But you could at least keep the issue open and fix it in a later 1.18.X update.
Maybe I just don't understand how this works.
That world was generated in Minecraft 1.6.4 and is about 650MB
Here is a much smaller world created with Minecraft 1.17.1.
Test World.zip
I then updated it to 1.18pre5 and found an ocean ruin here:
Did you test the world I uploaded? It's still happening in that world with prerelease 7.
You can use this command to see the issue /tp @p 116 91 -324 -10 70
1.17.1
1.18 prerelease 7