Wandering traders sometimes run extremely fast for no reason

I just had this happen trying to make a raid farm in my creative test world. I have a "village" about 30 blocks underground, so the Vex can't get to it. A trader spawned (I don't know if he spawned to me or to the "village", though). I killed one of the llamas and this happened. Maybe the "run back to village" and "panic because the llama was hit" speed multipliers stack?

The wandering trader starts running around once it lost both its llamas.

The last 3 wandering traders to spawn in my world which is on version 1.14.2 have had super speed. The first 2 that I encountered were dragging llamas behind them on invisible leads. Eventually one of the leads would break and one of the llamas would be set free, but this took a while and had no effect of the trader's speed. Imagine the video attached to this post but the llamas are being dragged behind the villager at super speed.I didn't see the third one loose its llamas, but I came out of a hole in the ground to find two trader llamas just sitting next to each other not moving with a wandering trader zooming around the area.

In a new turn of events I managed to get the llamas into a boat and this solved the villager speed thing for some reason.

I still have this issue on every 1.14.4 world. With or without the llamas, the trader will zoom around.

Also seeing this. Playing on Linux (Ubuntu 19.04) with OpenJDK (build 1.8.0_222-8u222-b10-1ubuntu1~19.04.1-b10).

As per Grayson's comment, I'd been deep undergound (y=11), and when I got back to the surface, I found two llamas, but only one trader. The trader was about 2 chunks away from the two llamas when closest to them, he was constantly running around very fast in an area probably no bigger than a 2x2 chunk area, which were roughly centred on my ladder that takes me straight down to y=11.

The boat trick didn't work. I pushed each llama into a boat, then moved them towards the trader. The trader himself then entered a boat. On breaking both boats, the trader continued running around.

If I'm quick enough and right click the trader, he does stop whilst trading, but on closing the GUI, he's off again!

I've found if I whack him with a sword, he then slows down to a normal running speed again for 5 seconds max, but then starts rushing around again.

Killing the llamas doesn't slow or stop him running around at warp speed.

The trader seems to just go invisible when during the night, but he's still there, as I can hear his 'eerrgh' noises. After sleeping the night, when i woke, I saw for a split second what looked a partial texture showing just his folded forearms darting around (sorry, my eye sight isn't the best, and it was for no more than a few tenths of a second), then the full texture appeared.

Saving and quitting, then loading the world again did make him return to normal speed, and the trader then started venturing outside of the approximate 2x2 chunk area he was previously darting around in.

This is a single player world generated in 1.14.4, with no client side mods what-so-ever. I am launching with MultiMC though.

This is probably more speculation than anything, but has anybody looked at the Wandering Trader's AI vis-a-vis villager AI?

Apparently, the trader's NBT data stores a "WanderTarget", an XYZ tuple representing a spot the trader is trying to get to.

I wonder if, perhaps, the trader is "required" to go to these spots in much the same way villagers are "required" to go to job sites or home at certain times of day, and begins running faster and faster to try to get there.

In a number of cases, it's probably a nonissue since vanilla terrain is benign enough that it's likely going to pick an easily reached spot. But, if a trader spawns within a player's turf that's particularly "exotic" in design, it might be continually trying to reach places it just simply can't get to, and ends up frantic.

I just had the same issue. Wandering Villager was standing still outside my house, and after I prompted to trade with him he started zooming around, but within a certain radius.

As is with most bugs in Minecraft, quitting to title and re-entering fixed the issue.

This is still an issue in the latest snapshot 19w42a.

I just noticed this happening in 19w44a, the latest snapshot of 1.15. Still not fixed yet, apparently. I managed to get a video of it happening, and I've attached it to this comment. Hope this helps!

I found that in reddit