• New Horizons on Maelstrom
    Maelstrom New Horizons


    Visit our website www.piratehorizons.com to quickly find download links for the newest versions of our New Horizons mods Beyond New Horizons and Maelstrom New Horizons!

Fixed Claire Larousse Sidequest: Stuck After Reloading to Sea

Hotshot

Freebooter
Storm Modder
Hi,

and another quest error...

I'm at the end of this quest but it doesn't matter what I do (spare her or take all gold for my self), when I try to sail away I get this error message:
"Reload: Continue despite locked locator. Please post your compile.log file at piratesahoy.net!"​
I've included the logs and the save.

Thanks,
Hotshot
 

Attachments

  • logs-and-save.zip
    1 MB · Views: 113
You are absolutely right! This is quite bizarre.

That log message was added to help us figure out if a certain bug has been fixed yet.
Specifically this very, very annoying one: Low Priority - Stuck At Sea When Assaulted During Mooring | PiratesAhoy!

But that is when going from 3D Sailing Mode to shore. This is quite literally the exact opposite happening.
Instead of the game continuing properly despite a potential problem going one way, going the other way apparently you get the problem instead.

It is too late for me today to investigate, but I'll definitely check it out.
Don't like this one.... :shock
 
I had hoped executing this through console prior to reloading to sea might help:
Code:
DeleteAttribute(PChar, "ForceReload");
Doesn't seem to though. Which is VERY strange, because that only gets set when anchoring.
So if I remove it while reloading from shore to sea, I shouldn't trigger that at all. :shock

EDIT: Turns out that this here does help:
Code:
DeleteAttribute(PChar, "Anchoring");

Do you remember exactly how you were reloaded to shore?
If I recall, this quest has an automatic reload when you enter 3D Sailing Mode, right?
But did you by any chance manually already drop anchor before the quest reloaded you to shore?
Just trying to figure out how you can still have that attribute when you're ashore, if it is removed as soon as the anchoring process completes. o_O
 
You mean how I got onto the shore?
Yes, that was automatic. As soon as I came into the bay (can't recall which one, but I can maybe figure it out if you need to know) I exited the map (-sailing) and I think before even getting into the 3d sailing mode, I was beamed onto the shore and she spoke to me.
Then the quest commenced up until that fateful ending...

DeleteAttribute(PChar, "Anchoring");
Thanks, I'll try this as soon as I'm home!
 
You mean how I got onto the shore?
Yes, that was automatic. As soon as I came into the bay (can't recall which one, but I can maybe figure it out if you need to know) I exited the map (-sailing) and I think before even getting into the 3d sailing mode, I was beamed onto the shore and she spoke to me.
Then the quest commenced up until that fateful ending...
The main thing that has me confused is that your save gives the appearance that somehow you managed to get ashore, with the anchoring process being started and aborted.
Normally if that process is aborted, you get proper stuck, but this shouldn't happen. A quest reload from sea completely bypasses the entire anchoring process.
So I'm not sure how your error can possibly have triggered.

I might be able to add some "just in case code" to prevent this happening again, but that isn't a proper fix as that does not address the root cause.
The only way to find out though is either based on your memory or if you can consistently replicate it from a savegame before the quest reload to shore.

Just for the sake of it, do you still have a save at sea just prior to that quest reload to shore?
I could at least check if you already have the "Anchoring" attribute there too.
 
Well, "unfortunately" after loading an older save and trying again, it worked :-\
Sorry I guess.
 
Well, "unfortunately" after loading an older save and trying again, it worked :-\
"Older" meaning a savegame from before you were auto-reloaded to shore on Barbados?
That would suggest perhaps something accidentally broke in the process of that reload.
Could be a very inconsistent bug. But I think with my suggested console command above, I could put a "fail-safe" in place to prevent that in the future.
 
Yep, I found it!
I sailed directly to Barbados and as soon as I exited 3D-Sailing mode near it, I was transported to the beach.
 

Attachments

  • -=Player=- QuickSave 30.zip
    1 MB · Views: 119
Thanks for that second save, @Hotshot. That confirmed my earlier suspicions. :yes

In PROGRAM\SEA_AI\sea.c find:
Code:
   DeleteAttribute(rPlayer, "scrollchars");         // PB: For Cheatmode
Replace with:
Code:
   DeleteAttribute(rPlayer, "scrollchars");         // PB: For Cheatmode
   DeleteAttribute(rPlayer, "Anchoring");           // PB: Just to make sure this is gone
   DeleteAttribute(rPlayer, "ForceReload");         // PB: Just to make sure this is gone

That allows you to continue play from the savegame you originally posted and should also prevent similar errors in the future.
 
Back
Top