matthias

Also still reproducable on 1.21.6-pre3 and 1.21.6-pre4

I can still reproduce this issue on 1.21.6-pre1 and 1.21.6-pre2

This issue makes teleport_duration with rotation unusable on 1.21.5, it would be awesome if this could be fixed for 1.21.6.

I’m also experiencing this bug, and I’ll share some more information to reproduce this issue.

Use this command to summon a block entity with a teleport_duration set to 20 ticks:

/summon block_display ^0.5 ^1 ^2.5 {Tags:["test"],block_state:{Name:"minecraft:cyan_concrete"},teleport_duration:20}

Then you can rotate the entity using a teleport or rotate command:

execute as @e[tag=test] rotated as @s run rotate @s ~180 ~

Repeat this command multiple times. The entity should rotate 180° consistently in 1 second, but instead, it gets randomly stuck and doesn’t finish the transition.

I’ve also attached a small sample world with command blocks to reproduce this issue easily.

I also have the same problem on switch, all coins and world are lost. but the world and coin is normal on iphone.

Just the extra vertical velocity from the jump boost...

On Sun, May 22, 2016 at 3:38 AM, Marcus L (JIRA) <[email protected]> wrote:

> Marcus L <https://bugs.mojang.com/secure/ViewProfile.jspa?name=NukeML>
> commented on an issue
>
> Re: Sprinting stops after autojump
> <https://bugs.mojang.com/browse/MC-102131>
>
> However if you have jump boost it will always retain the sprint
> afterwards. Very strange.
> [image: Add Comment]
> <https://bugs.mojang.com/browse/MC-102131#add-comment> Add Comment
> <https://bugs.mojang.com/browse/MC-102131#add-comment>
>
>
> Minecraft <https://bugs.mojang.com/browse/MC> / [image: Bug]
> <https://bugs.mojang.com/browse/MC-102131> MC-102131
> <https://bugs.mojang.com/browse/MC-102131>
> Sprinting stops after autojump <https://bugs.mojang.com/browse/MC-102131>
> Auto jump is activated, and if you sprint up a block the sprint stops
> instantly.
> This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
> [image: Atlassian logo]
>

Added 3 new example images. Auto jump will try to jump even if there is no room for the player. Auto jump will also try to jump onto the diagonal block even if it is obstructed. In my old screenshot it is difficult to tell what is actually happening, repeating command block is actually above the block i jumped off of, i took the screenshot mid-jump if i remember correctly... all are reproducible in 18w03b Some exceptions apply...

Can you please change your language to en_us and provide the above again, also paste the screen shot into paint, save the picture, then upload that picture.

1.10 is the last version i reproduced it in, not saying it is fixed though.

Oh, sorry, yes i see that, One in survival, other in creative...
Can he try throwing the ender pearl sideways into the portal?
Ill get back to this when i test this bug a bit.

You threw your ender pearl up, it landed in the block above the other portal.

This can be closed, it works as intended, if you are too far from the place the map was made, you will not see your location on the map

What resource pack were you using?
Cant tell, it got cut off

Turn it to redstone activated, activate it, then turn it back to always active, fixes it for me, I confirm this bug, i can reproduce it.

Someone forgot to check if windows was automatically resizing their crosshair...
I have not tested it yet.
I recommend you put your java version in the environment as well.

Looks like the bug in MC-94010 is fixed for creative, but not when you run away from the angry wolves...

One more thing, if you sprint at +/-90 +/-180 or 0 degrees, you can still succeed while sprinting.

I would say auto jump does not take the players velocity into account, when sprinting you run into the top of the block, when charging your bow, it fails.

The UUID nbt tag is no longer parsed check MC-86082, Sarge commented there. It is fixed in version 33c.

this error is fixed in 15w31c by making summon check if it can summon a mob with that uuid and will respond with:"Unable to summon object" if a mob with that uuid already exists.

if the zombie still exists this error happens when /kill is used