Lair of LeChuck missing key not fixed

@theonlyaxxe Just for the record, I’ve now tried every known workaround including cannon express re-entry. Geometry loads fine, all other objects present — but the key flag is still dead. If anyone on QA wants a bulletproof repro case, my checkpoint’s your gold standard. 7,000 hours, Year 1 player, 29-week Insider. Do better.”

And to everyone else — if your Stockade Key isn’t there, don’t waste hours chasing it. It’s broken, not you.

So what if, some of us were able to complete this TT with no problem. Even gone as far to Quit, Respawn, Redo TT and...no problem.

What is the cause?

Also,

If anyone from Rare is reading this

You might as well Send...Support a Ticket

@ghutar Appreciate the backup, mate. I’ve been around since Year 1 myself — just tired of hitting the same brick wall on something they claimed was fixed. Glad to know I’m not the only one seeing it for what it is.”

@ghutar Update – Root Cause Discovered (Confirmed by Testing)

After re-tracing my steps in The Lair of LeChuck Tall Tale, I’ve found what actually breaks the Stockade Key spawn.

If you find the Stronghold Key before talking to Guybrush, everything looks fine at first. But when you later trigger the Guybrush dialogue, the game displays the message “Stronghold Key was lost.”
That message sets a hidden flag (StrongholdKey = Lost) in your checkpoint.

Once that flag is active, the Stockade Key never spawns—no matter how many times you reload, scuttle, or restart. The script assumes the Stronghold Key was legitimately discarded and never re-enables any later key spawns tied to that variable.

I reproduced this twice with consistent results.

👉 Trigger order matters:

Talk to Guybrush first → Stronghold Key and Stockade Key work normally.

Pick up Stronghold Key before Guybrush → “Stronghold Key was lost” appears, and the Stockade Key will never appear later.

So this isn’t a geometry or instance bug—it’s a flag-ordering issue in the quest logic.
@Deckhand @SoT_Support tagging you so QA can log this with proper reproduction steps.

@d3adst1ck Appreciate the suggestion — I’ll file a ticket to make sure QA gets the repro steps.
My intent here was to document the logic flaw publicly so others don’t waste hours chasing a missing key.
Hopefully this thread helps both players and Rare track down the trigger order issue faster.

@theonlyaxxe Update:
Did another run last night and had different results. This time I went straight to the Stockade, opened it, and immediately talked to Guybrush — no problem at all.
My first run had me wandering around triggering several notes and sit-down cues before I reached Guybrush, and that’s when the “Stronghold Key was lost” message led to a missing Stockade Key later.
This may indicate a timing or trigger-order issue in the Tall Tale script rather than a simple pickup bug.

So what I got. You tried to skip steps? And caused it to break?

Ive completed this about 10 times and the game wont merge from the completed quest to a new server, so this quest could not be finished. Sent support a ticket and no unlock. I dont play SoT anymore, too many bugs and this is a reminder why I left

@burnbacon, no. I simply explored the new content and came across the key before working the dialog . are you implying that you must follow every clue in order and if not then the user is at fault ? Are you suggesting that players should not explore before focusing on the TT ?