Luring mobs onto blocks at Y=-64 will instead make them pathfind to the highest elevation
when spawning a creaking in a flat world it will atttempt to pathfinnd tto the highest elevation (show in video below)
- Spawn in a creaking
- place a block on a wide flat surface
- go survival and look away from the creaking (or go creative mode and speed the tick rate up)
- Watch as creaking ignores its target and attempts to walk to highest elevation
Linked Issues
Created Issue:
Creaking's ignore ttarget / player and pathfind to highest elevation
when spawning a creaking in a flat world it will atttempt to pathfinnd tto the highest elevation (show in video below)
- Spawn in a creaking
- place a block on a wide flat surface
- go survival and look away from the creaking (or go creative mode and speed the tick rate up)
- Watch as creaking ignores its target and attempts to walk to highest elevation
Creaking's ignorettarget / player and pathfind to highest elevation
yep same issue persists is both gamemodes [^2025-01-12 13-44-56.mp4]
Creaking's ignore target / player andpathfind to highest elevationLuring mobs onto blocks at -64 will instead make them pathfind to the highest elevation
Luring mobs onto blocks at Y=-64 will instead make them pathfind to the highest elevation
is duplicated by
Thank you for your report!
We're tracking this issue in MC-279417, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Please confirm if this is still the case when being in survival after placing some blocks at a higher elevation. Currently you are in creative, in which creakings will not target the player.
same issue persists 2025-01-12 13-48-54.mp4
I am able to reproduce the reported behavior. It was introduced in 24w34a. I would like to suggest updating the Summary to be more descriptive of the actual issue:
Can confirm.
Not sure if any other mobs have this issue.