Almost two months after launch, players are charting the deepest waters of the Anvil engine overhaul. While the majority of the voyage has been incredibly smooth, a handful of terrifying squalls have emerged in the form of progression-halting bugs. The most severe issue currently circulating the community is a catastrophic softlock occurring in Kingston, which seemingly wipes the main campaign from your quest log and disables the fast travel system entirely.

If you are approaching the mid-game sections of the campaign, you need to be aware of this glitch. Alongside this progression blocker, completionists are also struggling with a DNA tracker bug affecting the iconic “Raise the Black Flag” sequence. Here is everything we know about these current issues, the strange lore implications of the Kingston glitch, and the necessary workarounds to keep your Caribbean adventure afloat.

The Anatomy of the Kingston Softlock

The trigger for this devastating bug is tied to a very specific moment in the campaign. If you have just arrived in Kingston and are preparing to meet up with “Kid”—the enigmatic pirate whose true identity plays a massive role in the overarching /story/—you need to pause and make a manual backup save immediately.

According to multiple community reports over the last 24 hours, the glitch activates right after finishing this specific main scenario block. Normally, players would return to the Jackdaw or engage in open-world activities, utilizing the revamped /gameplay/parkour/ mechanics to explore the colonial rooftops. However, while free-roaming in Kingston shortly after the mission, the game will suddenly forcefully pull you out of the action.

Without warning, the screen fractures into an Animus loading simulation. This is not a standard memory corridor transition. Players report hearing a bizarre, disembodied “eagle voice” warning Edward Kenway not to listen to the simulation. Once this unprompted and highly unusual cutscene concludes, the player is dumped back onto the streets of Kingston—but the state of the game has been irreparably damaged.

The Mysterious “Eagle Voice”: A Glitch or Scrapped Lore?

The audio associated with this bug is fascinating and has sparked massive speculation. In normal gameplay, there is no sequence where an “eagle” directly speaks to Edward to warn him about the simulation. The Animus anomalies in the game usually feature Abstergo Entertainment employees or modern-day hacker dialogue.

Some players theorize that this audio file is a leftover trigger for a scrapped Isu encounter or a displaced narrative event meant for the very end of the game. Because the engine overhaul integrates entirely new narrative connective tissue, it is highly likely that a scripting error is calling an audio file and a cutscene state from an entirely different memory block. When the game tries to resolve this out-of-bounds cutscene, it fails to return the player to the correct quest state, effectively derailing the entire campaign logic.

Symptoms: Stranded in the Caribbean

Once the glitch finishes its bizarre playback, you will immediately notice the consequences. The primary symptom is that your main quest marker is completely gone. It is not just untracked in the HUD; if you open the main menu and navigate to the Quest Log, the primary campaign tab will be entirely blank.

The game’s internal tracker desperately tries to find an active objective to display. Consequently, players report that the HUD briefly forces an Officer Quest onto the screen—specifically, Lucy Baldwin’s “The One With the Gun” mission. However, completing this officer side-quest does nothing to restore the main storyline.

To make matters worse, the fast travel system becomes entirely greyed out. Because the game believes you are still trapped in a transitional Animus state or a restricted memory corridor, it revokes your ability to fast travel between islands or even back to your ship. You are essentially marooned in Kingston. Attempting to force a reset by engaging in combat and deliberately desynchronizing will simply respawn you in Kingston with the exact same broken quest log.

This situation is highly reminiscent of the earlier progression blocker we covered in our /news/2026-08-18-black-flag-resynced-how-to-avoid-the-not-even-a-real-captain-softlock/ article, where corrupted quest states forced players to abandon dozens of hours of progress.

Workarounds and Prevention

Currently, there is no known mechanical fix once the Kingston softlock has occurred. Reloading recent autosaves will not work, because the game aggressively autosaves the moment the glitched Animus cutscene ends, permanently overwriting your safe state.

Your only defense against this bug is preventative manual save management. Black Flag Resynced graciously allows multiple manual save slots, an upgrade over the original 2013 release.

Follow these steps to protect your save file:

Create a hard manual save the absolute moment you dock the Jackdaw at Kingston for the main story.
Create a second, separate manual save right before starting the mission marker involving “Kid”.
After completing the mission, do not linger in Kingston. Immediately fast travel back to the Jackdaw and sail out into the open ocean to force a zone transition.
Do not engage with the Lucy Baldwin Officer Quest until you are safely in a new sequence.

If you are already a victim of this bug and do not have a manual save, you are unfortunately at the mercy of Ubisoft Singapore. You will need to wait for a hotfix. Given the severity of the bug and the volume of reports pouring in across various /platforms/, it is highly likely that this will be addressed in the upcoming Title Update 1.0.7.

The “Raise the Black Flag” Completion Bug

While the Kingston softlock destroys mid-game progression, another bug is actively torturing end-game completionists. The mission titled “Raise the Black Flag” (often reported by the Spanish community as Iza la bandera) is failing to register as completed upon finishing the campaign.

Players who have rolled the final credits are opening their DNA trackers to find that this specific mission remains unchecked. This is incredibly frustrating, as it holds your synchronization rate hostage at 99%, completely locking you out of the Platinum trophy and the exclusive 100% completion rewards.

Community testing has revealed that replaying the memory from the DNA menu does not solve the issue. In fact, some users report that replaying the mission creates a duplicate ghost entry in the log, further confusing the UI. If you are sitting at 99% because of this specific flag, hold your fire. Do not attempt to force the game to recognize it through memory replays, as it might corrupt your tracker data. Wait for the official patch, which will likely run a retroactive check on your save file and instantly grant the completion status upon logging in.

A Silver Lining: Finding the Crimson Cloak

If you are holding off on story progression to avoid the Kingston bug, now is the perfect time to clear out some open-world exploration and expand your wardrobe. The community has finally pinpointed the exact drop location for the highly coveted Crimson Cloak outfit.

This striking piece of gear features deep red fabrics trimmed with gold, offering a more traditional, flamboyant pirate captain aesthetic compared to the muted leathers of the default assassin robes. Unlocking it requires tracking down a specific, unmarked chest on one of the outer smuggler islands.

If you are looking to revamp your Edward Kenway, make sure to read our comprehensive /news/2026-07-17-how-to-unlock-all-outfits-and-legendary-weapons-in-assassin-s-creed-bl/ tracker, where we have just added the precise map coordinates and required equipment to unearth the Crimson Cloak. Take advantage of the revamped eagle vision mechanics to scan the dense jungle foliage, as this particular chest is hidden incredibly well behind dynamic vegetation.

Stay vigilant out there on the Caribbean waters. Keep your manual saves updated, avoid loitering in Kingston after critical story beats, and hopefully, the development team will have these turbulent technical seas calmed very soon.

Black Flag Resynced: How to Fix the Kingston Main Quest Softlock and Tracker Bugs