Fix in Progress Locked icon not clearing for door from cabin to ship deck

[Tingyun]

In certain starts the door leading from your captain's cabin to the ship deck remains a "locked" graphic rather than the normal ship deck graphic. Persists even as you buy or swamp ships. You can enter and exit normally, but it always shows the locked graphic.

Checked with castaway after buying a ship, normal stormy start by fast traveling to ship, and agent by turning around and reentering ship.

I think what is happening is that if the start doesn't involve the normal tutorial behavior of malcolm or his replacement going through and unlocking the door, it always retains the locked graphic.

About to post a saved game for other bug that can confirm, but easiest confirmation is to begin any stormy start, or the agent start, and immediately board the ship and go to the cabin.

 

[pedrwyth]

Attached files Malcolm Hatcher dialogue (from dialogues) and Robert Fletcher dialogue (from storyline\freeplay\dialogues which have an added line in stormystart to clear the lock icon.

 

[Pieter Boelen]

Was this just a Tutorial bug then?

 

[Levis]

Was this just a Tutorial bug then?

it also happens in other cases I believe. but in tutorial it was an extra problem..

 

[Pieter Boelen]

@pedrwyth about this line in the Malcolm Hatcher/Robert Fletcher dialog files:

TutDeck.reload.l1.disable = 0;   //PW remove locked cabin icon

Do you think it makes sense to move that to case "TavernSitWaiting" instead?
That one gets called on Stormy Start, but also in many other cases where the tutorial is skipped/completed.
So then perhaps it might fix things in more additional situations?

 

[pedrwyth]

@pedrwyth about this line in the Malcolm Hatcher/Robert Fletcher dialog files:

TutDeck.reload.l1.disable = 0;   //PW remove locked cabin icon

Do you think it makes sense to move that to case "TavernSitWaiting" instead?
That one gets called on Stormy Start, but also in many other cases where the tutorial is skipped/completed.
So then perhaps it might fix things in more additional situations?

I'm easy I'm sure you know the code well enough - I only looked at the reported Stormy Start instance - not what other skip cases might leave the same problem. [In other words I didn't read the first post properly (always read the question) which also mentioned the agent and possibly others ]. So yes indeed

 

[Pieter Boelen]

In that case, I hope you're right and I DO indeed know the code well enough so that my change actually works as it is meant to.
You may want to check after the next update....