[WAD] Lua error and maybe wrong winning conditions in Lone Wolf [998.7]

[Puciek]

So when playing lone wolf and after receiving a message that I am to sink the K 44 at any cost and making Seawolf expendable i fired up a lot of torpedos at the k 44 and then got sunk while they were underway and eventually hit the target to trigger an LUA error.

The error I got (different from tm.asp?m=4447538):

05:05:55 - 05:05:55 - Contact K 44 Ryazan has been lost.


05:05:55 - 05:05:55 - Lua script execution error: [string "RU_SSBN_Destroyed"]:27: attempt to index local 'submarine' (a nil value)


05:05:55 - 05:05:55 - Sonar Supervisor Captain, we can hear breaking-up noises coming from the Ryazan.


05:05:55 - 05:05:55 - Weapon: Mk48 Mod 5 ADCAP #2035 has impacted K 44 Ryazan.


05:05:55 - 05:05:55 - Torpedo Mk48 Mod 5 ADCAP #2035 is attacking K 44 Ryazan with a base PH of 80%. Final PH: 80%. Result: 43 - HIT


05:05:55 - 05:05:55 - Decoy (MG-44 Korund; Tech: Late 1970s) from K 44 Ryazan is attempting to seduce sensor: Torpedo Seeker (Tech: Early 1990s)(Guiding weapon: Mk48 Mod 5 ADCAP #2035). Final probability: 15%. Result: 80 - FAILURE


05:03:42 - 05:03:42 - Contact Torpedo #26 has been lost.


05:03:42 - 05:03:42 - SSN 21 Seawolf has been destroyed!

Also when seawolf was sunk, but the torps were underway I got a message that the scenario is finished and I've lost. And yet when I continued anyway, and the K 44 was sunk I would expect to have a passing score, since my sub was expandable by the orders. And yet the score log shows:

14/10/1998 05:03: Score changed from 0 to -500. Reason: SSN 21 Seawolf was destroyed.

14/10/1998 05:05: Score changed from -500 to -50. Reason: K-44 Ryazan was destroyed

14/10/1998 05:05: Score changed from -50 to 0. Reason: Russian submarine K 44 Ryazan was discreetly sunk.

And 250 points are required to pass the scenario, which makes it a bit odd to first get orders like that and then fail for obeying them.

Save attached, hopefully the right one.

[Rory Noonan]

Hmm, this is not really a bug. The Lua error occurs because the Seawolf is destroyed; and then only once you play beyond mission end.

Once the Seawolf is dead, the mission is over. You're commanding the Seawolf, so the idea of Seawolf being destroyed and then moving on to the next mission doesn't make much sense to me.

The wording of the message is reasonable because ***SPOILERS*** a nuclear attack on the US is imminent. It would be reasonable to expect that naval command would direct the Seawolf to destroy that threat at any cost. Note that this message is only triggered when the SSBN is in the final stages of readying for attack, so you have by this point either not found them in an inordinately long amount of time or found them but not yet gotten very close.

I understand your point, but I don't think any substantial changes need to be made here.

[Puciek]

Ah okay, fair point. In my case, I was already gaining on the K 44, and when I got the immediate warning I simply turned speed to flank, switched on all sonars and made the kill in time.

Though there is still the issue of Lua error as in the log, probably should've made two separate topics - my bad!

[Rory Noonan]

The Lua error occurs because the scenario is over; the scenario is not intended to be played past the ending conditions.

In any event adding error handling for the Seawolf being dead wont change the outcome.