SH3 Commander Random Sabatage Question

[Samwolf]

Originally Posted by HEMISENT

WRONG!
Sorry Samwolf, SH3 Commander re-rolls the dice each and every time you save/exit/relaunch thru Commander. Every malfunction is capable of being issued either in port or at sea. The difference is there a few files that are set to stay with the boat the ENTIRE patrol. Most malfunctions are "repairable" by reloading commander. You have a remote chance of getting issued a different malfunction file but that's how it works.

A 1 setting in RndMidPat makes possible malfunctions occur mid patrol and a 0 setting doesn't allow mid patrol possibility of a malfunction, so I read that as, with a 0 setting a malfunction can only occur at the beginning of a patrol. Am I understanding that wrong?

The way you explain it if I do get a type 0 malfunction mid patrol, it's set so randomization will not take place again for that malfunction, right?

[HEMISENT]

Originally Posted by Samwolf

The way you explain it if I do get a type 0 malfunction mid patrol, it's set so randomization will not take place again for that malfunction, right?

Hi Samwolf
Had to go into Commander to make sure I get this right:
; Set RndMidPat to 1 if you want randomisation to occur mid-patrol, 0 if not

The RndMidPat=1 means if you get a loaded file upon startup it is deemed "repairable" should you save/exit/relaunch. Commander will roll the dice again you may get nothing, you may get something else.

A RndMidPat=0 means that should you get a file, that "particular" malfunction is good for the duration of the patrol. NO matter when it is issued

Now, lets say you launch commander upon beginning a patrol. You draw a Mal file with RndMidPat=1, you play awhile then save/exit/relaunch. Upon relaunching, commander rolls the dice fresh-you may get nothing, you may get a different Mal file or there's a "hugely remote" possibility that you may get the same one back again.

On the second re-launch If Commander deals you a Mal file with RndMidPat=1
that also is repairable. However, if commander issues you a Mal file with RndMidPat=0 you are stuck with it for the length of the patrol.

A "0" file can be issued at any time commander launches, same as a "1" file.

Hope this clarifies things a bit.

[Samwolf]

Originally Posted by HEMISENT

Hi Samwolf
Had to go into Commander to make sure I get this right:
; Set RndMidPat to 1 if you want randomisation to occur mid-patrol, 0 if not

The RndMidPat=1 means if you get a loaded file upon startup it is deemed "repairable" should you save/exit/relaunch. Commander will roll the dice again you may get nothing, you may get something else.

A RndMidPat=0 means that should you get a file, that "particular" malfunction is good for the duration of the patrol. NO matter when it is issued

Now, lets say you launch commander upon beginning a patrol. You draw a Mal file with RndMidPat=1, you play awhile then save/exit/relaunch. Upon relaunching, commander rolls the dice fresh-you may get nothing, you may get a different Mal file or there's a "hugely remote" possibility that you may get the same one back again.

On the second re-launch If Commander deals you a Mal file with RndMidPat=1
that also is repairable. However, if commander issues you a Mal file with RndMidPat=0 you are stuck with it for the length of the patrol.

A "0" file can be issued at any time commander launches, same as a "1" file.

Hope this clarifies things a bit.

Thanks HEMISENT. I was misreading how it worked the 0 and 1 settings worked. Good thing to know.

I always breathed a sigh of relief when no 0 value malfunction showed up during my pre-patrol shakedown cruise. Now I have something else to worry about during my patrol.

[Werewolf]

There is something that I have always wondered about....these randomised events, are they built into the SH3 Cmdr. so that they happen if SH3 Cmdr is installed or do I have to chose this feature? Personally I like some of them, but I don't want the sabotage feature

[Jimbuna]

You can switch between any of the 3 following option:
1) Everthing off
2) Malfunctions only
3) Malfunctions and Sabotage

[Werewolf]

@Jimbuna:

:hmm: okay.....funny, I have never noticed that, I have the 2.6 version, I haven't run it yet since I'm afraid that it will mess up my graphics and uboat availability dates, last time I had it installed the sky went black....not a criticism of SH3 Cmdr., I just don't know how to hmm control it yet

[Jimbuna]

I was refering to SH3Commander v2.7