Crimson Desert Horse Follow Bug Fixed in 1.01.01: What Changed for Mounted Missions
The horse follow bug in Crimson Desert — where horse movement became abnormal during mounted NPC follow missions — is confirmed fixed in Patch 1.01.01. Here is what changed and what to do if the issue persists.
The horse follow bug in Crimson Desert — where holding the button to follow an NPC during mounted missions caused your horse's movement to become erratic or unresponsive — is confirmed fixed in Patch 1.01.01, released March 29, 2026. If you put off doing mounted follow-type missions because of this issue, the behavior should now work as intended.
This was listed as an active known issue before the patch, so the fix is confirmed by Pearl Abyss directly in the 1.01.01 patch notice. It is not a community-reported resolution — it is an official confirmed change.
Quick answer
- Status: Confirmed fixed in
Patch 1.01.01(March 29, 2026) - What was fixed: Horse movement becoming abnormal when holding the NPC-follow button during mounted missions
- What to do now: Install
Patch 1.01.01and retry any mounted follow missions you were avoiding - If it persists: Verify you have the correct build installed and restart the game; if still broken, report through in-game feedback
What the bug was
During mounted NPC follow missions — sequences where you ride alongside or behind an NPC on horseback and hold a designated button to maintain the following behavior — your horse's movement could become abnormal. This manifested as erratic pathing (the horse moving in unintended directions), unresponsive movement inputs (the horse not responding to steering while the follow state was active), or the follow behavior breaking down entirely and leaving the horse in a stuck or confused state.
This affected the reliability of a specific type of mounted mission mechanic. Players who encountered it during story or side-quest content found the missions difficult or impossible to complete normally, as the horse behavior was integral to the follow sequence working correctly.
How it was affecting mounted missions
The follow mechanic in mounted missions requires your horse to match the NPC's movement path while you hold the input. The bug disrupted the interaction between the held button input and the horse's movement system. Instead of smoothly following the NPC's trajectory, the horse would break from the expected path or stop responding to directional correction.
For story missions with follow sequences, this could interrupt progression. For side content or companion missions, it disrupted the intended experience without necessarily blocking completion (depending on the specific mission design and whether the follow state had a hard completion check). However, the abnormal behavior was consistent enough to be officially acknowledged.
What Patch 1.01.01 changed
The fix addresses the interaction between the follow input state and horse movement processing. According to the official 1.01.01 patch notice, the bug was resolved as part of the four targeted fixes in this hotfix. Post-fix, holding the NPC-follow button during mounted missions should result in normal horse movement that follows the NPC's path without the erratic behavior.
The fix applies to all platforms simultaneously, as 1.01.01 was an all-platforms release.
What to do if the behavior persists after the hotfix
If you are on a platform that has Patch 1.01.01 installed and horse follow movement is still abnormal:
- Verify your build. Check the version number on the game's title screen or Options > System. The current build should display
1.01.01. - Fully restart the game. Do not just resume from a suspended state — close the game entirely and relaunch.
- Try the mission from the beginning. If the mission was saved at a checkpoint mid-way through the follow sequence while the bug was active, some mission state may be in an unexpected condition. Loading an earlier save or restarting the mission from the beginning can clear this.
- Test on a fresh mounted follow mission. If you have access to another mounted follow mission, try that one to determine whether the behavior is mission-specific or persists broadly.
- Report through in-game feedback if the behavior continues after all of the above. Any persistence after 1.01.01 is installed would represent a different issue from the originally reported bug.
FAQ
Which specific missions were affected by the horse follow bug? Pearl Abyss did not name specific missions in the patch notice. Any mounted mission involving an NPC follow sequence with a hold-button input was potentially affected.
Does this affect the Constellation Helm or other special mounts, not just regular horses? The official description refers to horse movement during mounted NPC follow missions. The Constellation Helm controls bug is a separate, still-active known issue. See Constellation Helm controls bug status.
Was the White Bear also affected by movement bugs?
The White Bear sprint bug (sprint being unavailable) was a separate issue also fixed in 1.01.01. The horse follow bug is specific to follow-input interaction during missions, not a general sprint or movement problem. See White Bear sprint fixed in 1.01.01.
Do I need to restart missions I started before the patch? If a mission checkpoint was saved while the bug was actively causing problems, restarting from the beginning of that mission is advisable. Post-patch, starting fresh ensures the mission state is clean.
What to read next
More Guides
Crimson Desert Private Storage Guide After Patch 1.00.03
Patch 1.00.03 finally added Private Storage to Crimson Desert. Here is where it is, how it changes your inventory loop, and what it still does not replace.
How to Beat Saigord the Staglord in Crimson Desert
Complete boss strategy for Saigord the Staglord at Icemoor Castle Ruins, including attack patterns, phase breakdowns, Ice Resistance preparation, and all loot drops.
Crimson Desert ROG Xbox Ally X Launch Issue Explained
Pearl Abyss still lists a live Crimson Desert launch problem on ROG Xbox Ally X. Here is the exact driver pair it names, who is investigating it, and the temporary workaround the studio currently recommends.