This is happening to me too. I tried to Reset The End, and no Ender Dragon is spawning. The ender crystals are there, but no dragon.
It really sucks that this bug is still around. I slowly watch all my friends die off from Minecraft because we can’t play together anymore without complicated work arounds. I really miss my friends. If this bug was fixed I’m sure they would come back. I want to see my friends again.
Attached a GIF. Still an issue and would like to disable my logs.
LAUNCHER 2.1.5387
Wednesday, June 26, 2019, 06:51:15
d5f0ae544bfc776d9523eef956933480a58d90e7
Confirmed on the following Launcher 'Released'
LAUNCHER 2.1.5322
Tuesday, June 25, 2019, 10:02:57
c179bd360652a0a7ba2e97b1b68715a3456554aa
I can confirm I'm having a similar issue on Multiplayer and appears as it doesn't save the Prefix and Suffix at all.
Additional things that may have fixed and removed:
Candy Crush Soda Saga
Casino Poker
Avast Free Anti Virus
Hello,
I can clearly say this is NOT invalid and it's an issue. Even if you create and run the Minecraft Snapshot through the console. It still creates a `backups` folder outside its directory. This should not be doing this.
This is not invalid and actually does this on Windows as well.
Nothing is modified and completely a vanilla JAR.
Kind Regards,
Cory
The new version fixed the issue for me. I didn't follow any of the advice here regarding creative mode, etc, just connected to the realm and it worked. Thanks for the fix, Mojang team.
Exact same situation as Even. I died twice in the Nether, and on the third the game crashed. Haven't played since (despite trying).
{"app_name":"minecraftpe","timestamp":"2016-12-25 18:47:30.66 -0500","app_version":"1.0.0","slice_uuid":"f68e4464-3201-338e-bfc6-759784b7bf37","adam_id":479516143,"build_version":"1.0.0.18","bundleID":"com.mojang.minecraftpe","share_with_app_devs":true,"is_first_party":false,"bug_type":"109","os_version":"iPhone OS 10.2 (14C92)","incident_id":"1DD739D0-ED92-48AB-8821-31D4C751D388","name":"minecraftpe"}
Incident Identifier: 1DD739D0-ED92-48AB-8821-31D4C751D388
CrashReporter Key: 16045fdbda835ed7d76bca2953820d492fb14f31
Hardware Model: iPad4,7
Process: minecraftpe [834]
Path: /private/var/containers/Bundle/Application/F6381E15-BC4E-4B83-B80F-116DE3C0FE2D/minecraftpe.app/minecraftpe
Identifier: com.mojang.minecraftpe
Version: 1.0.0.18 (1.0.0)
Code Type: ARM-64 (Native)
Role: Foreground
Parent Process: launchd [1]
Coalition: com.mojang.minecraftpe [526]
Date/Time: 2016-12-25 18:47:30.3007 -0500
Launch Time: 2016-12-25 18:46:21.2408 -0500
OS Version: iPhone OS 10.2 (14C92)
Report Version: 104
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Triggered by Thread: 0
The exact same is happening to me (iOS/iPad). I downloaded the realm to try to play locally, but with the same result. The loading messages... generating terrain... Done! ... immediately crashes the game.
Anything over 16 characters would say:
Character count > Maximum count
Originally in 1.10.x and lower it would say:
65 > 16
128 > 16
Here it's showing:
65 > 64
64 > 16
Clearly, something may have changed.
Confirmed for 13w41a.
You cannot also take screenshots in the GUI area before joining "Single Player" or a "Server" anywhere outside before actually joining a game.
Please wait for 1.6.2 - Not much you we do at this point.
Yes it's been confirmed fixed.
Confirmed this works in 1.6.1 as well. I was taking a look at the tutorial page and found the "Security Scan" for TNT and this makes it where you cannot get anything out of your inventory.
Depending on the clock if slow enough, You can obtain the item.
In older clients, I'm also getting this,
After recreatiing the server I've recieved the same error, Instead of making another issue figure this was related.
Confirmed: Tested on "world above" and a "clean world".
Unable to run scripts under an `xfs` filesystem if the `ftype` is set to 0. This issue continues to be a problem and identical to the issue we were having a year ago.
I’ve entirely isolated this issue to a VPS using the service called `Vulr` and replicated the problem by doing the following. This is worth noting as when installing `AlmaLinux` as the (“Host Machine”) with an xfs filesystem it was `ext4` in this environment.
Additional things to note. We do know this isn’t meant to be run on AlmaLinux, and we run our bedrock servers in docker running Ubuntu. However, since the (“Host Machine”) is an xfs filesystem with ftype=0. This will cause (“scripts”) to fail. We isolated it to make sure it wasn’t a docker-related issue, and it’s not.
If you use `Vultr` they do have a scripts area where you can easily copy/paste to build this server from scratch and don’t have to manually do it. The main command is creating partitions with the `mkfs.xfs` parameters.
Once the server has booted or completed the tasks.
If everything looks set up properly. We’re going to build a server mostly from scratch. This will create the essential files/worlds required.
The next step is the scripts. You can find your own scripts or use the one provided. This includes behavior and resource packs and a modified `level.dat` to enable experimental builds. Might want to do this manually to ensure the files get extracted properly.
Next, we will proceed by copying these same files into the new directories/partitions we created earlier.
Modify the ports to avoid conflicts or just run one at a time.
Let us confirm the issue. Go into each directory and start the server respectively.
You will see that `ext4` and `ftype1` works perfectly fine, and for `ftype0` the scripts don’t load at all. Keep in mind these are identical servers we just copied and the 2 main differences are the filesystem and server port.
This is where it becomes interesting…
This will load the scripts fine. However, if we switch to:
Do you notice we’re using the same `screen` command as above? The difference in this case, we ran the command from `/ftype0` and the result is that it failed. However, we run it from `cd /home/new/` directly. It doesn’t fail. Not likely a path issue per Se. This is still a `ftype=0` issue and needs to be resolved.