mojira.dev
MC-296348

NoAI:1b mobs cannot be ridden in 1.21.5+

With no changelog notice mobs in 1.21.5 with NoAI:1b are no longer rideable

Steps to Reproduce:

  1. Summon a rideable mob (e.g., a horse, pig, or camel) with NoAI set to true:

    /summon horse ~ ~ ~ {NoAI:1b,equipment:{saddle:{id:"minecraft:saddle",count:1}}}

  2. Attempt to ride the mob (right-click / mount). ‘Use movement keybinds’ (edit)

Expected Result:
You should be able to ride the mob as normal. The mob would stay still (not move on its own), but you could interact and ride it.

Observed Result:
You cannot ride mobs that have NoAI:1b. They are stuck in place. This effects all rideable mobs

Notes:

  • This behavior worked as expected in Minecraft 1.21.4 and earlier versions.

  • No mention of this change appears in the 1.21.5 changelog.

  • It affects all mobs that are normally ridable, including pigs, horses, camels, and striders.-

  • Many maps used NoAI to prevent mobs from wandering while still allowing riding. This change breaks builds relying on stationary rideable mobs.
    update: still broken in 25w15a, post updated

Environment

Minecraft Java Edition 1.21.5 (vanilla)
Windows 10
No mods or datapacks affecting mobs
Tested in mods and plugins to (Fabric, Spigot)
Tested in singleplayer and multiplayer with and without mods

Comments 4

was able to summon a rideable NoAI:1b mob. Possibly lag was responsible for your bug.

Can confirm it doesnt work

I wanted to specify for clarity, the mobs can be mounted but they will not move and are frozen.

Can confirm, have been using this feature for a while and was disappointed to see it not work. Also happens with pigs, striders, camels, and all the other steerable mobs.

Z A

gegy

Community Consensus

Platform

Important

Commands, Mob behaviour

1.21.5, 25w15a

25w16a

Retrieved