Unknown2k
Assigned
Reported
Comments
Reading the comments from others regarding this, I see I am not the only person who has issue with the "Working as intended". I'm sure mojang is at least aware of the poor classifications.Thank you for your time.
Ok. I'm not entirely proficient at submitting bug reports, I've only did a few. Let me see if I follow.
The bug still exists in the most recently released snapshot, and you are labeling it as a dup for a previous snapshot, and tagged it as Resolved and working as intended.
So, massive block lag is the planned outcome of the newest snapshot and is indeed, "working as intended".
If I am wrong in my assessment, Did I incorrectly submit? I don't understand how Mojang can confirm a bug in a snapshot, but label it resolved, dup and working as intended despite evidence it isn't? Whats the point in continuing to report bugs?
Kumasasa,
Forgive this if it sounds rough, but did you review my log snip? It isn't resolved, I just tried the snapshot. This isn't a log from weeks ago, its today with the release. It isn't fixed or resolved in the current snapshot.
Its listed as resolved, when will this resolution be put into a snapshot?
Nope. Even turned Cmd blocks off in config and it didnt start doing it until 3 snapshots ago
I know. I said TEST after it teleported me. It happens to everyone, randomly. I cant find a pattern.
It just happened to me again. I was Teleported to the Map's Spawn point at the second someone died in the End and me and that person both spawned at Spawn.
It seems to happen when someone dies in the End and the person who also gets Teleported to spawn doesn't have a bed set.
If you search for "Test" I said Test after it happened to me. I was Teleported to the Spawn Point of the map.
Yes. I will review logs tonight on the incident and post it.
This remains unfixed. We can't use any snapshots above 47c. We run our server in Adventure mode at first, to control the block people spawn in on.