Mojira Archive
MCM-1565

minecraft:movement.jump doesn't allow for custom mobs to turn

Partner Rank:
**

3

Partner Team Reporting:

Noxcrew

Verification builds:
minecraft_uwp_renderdragon_x64_win10_9930166_release

Minecraft.Windows_1.19.5.0_x64_Test

Summary:
The minecraft:movement.jump behavior is currently broken! Custom entities using this behavior to move can only path directly forward in the direction they're looking. There is an argument available called "max_turn", but it appears to be broken. We had previously used this in our "Dragon Skies" map on two mobs (noxcrew:ds.slime and noxcrew:ds.slime_lava) and it worked as expected.

Worth noting- if the mob rotates itself some other way (random look for example), it will then path forward into its new facing direction when it reacquires a target.

Impact:
These two mobs are now functioning improperly on Dragon Skies. Also, more importantly, two mobs in our upcoming third party IP deal map rely on this behavior, and will not work properly without it.

Repro Steps:

  1. Download "Dragon Skies" by Noxcrew
  2. Walk forward and press the map start button
  3. I'd highly recommend giving yourself resistance 100 and saturation via the /effect command
  4. /tp 635 88 742
  5. Around this area, some altered magma slimes should spawn. You can also do "/summon noxcrew:ds.slime_lava"
  6. Notice the slimes can only path forward, and will only attack you if you move into their path. You can use "/paths" to see that they're trying to get to you (see video below).

Observed Results:

The mobs go straight forward in one direction instead of towards the player.

Expected Results:

The mobs should be able to rotate and go towards the player.

Screenshots/Videos attached:

I'm not sure it's clear from anywhere else in this bug so I just wanted to make sure I noted that the slime in this video is a custom entity slime!

https://youtu.be/-Iz7evD2bC4

Regression Build:

We released Dragon Skies in 1.16.201, and it worked properly then. A member on the partner discord posted a message suggesting this behavior last October 31st, so the bug likely appeared sometime between last April and last October.

Unresolved

[Noxcrew] Joe Arsenault

2022-06-15, 11:08 PM

2022-06-21, 01:25 AM

4

2

Future Release

-