SH3 Commander Random Sabatage Question

[Lanzfeld]

I dont go over 16X when on patrol so it is obvious that I save alot during the same patrol because I take so long. When I want to play again I always start SH-3 Commander and "Launch" SH-3 through Commander. Is this the correct way to do it? If I had a random failure in my last game would launching again through Commander reset the malfunction? Should I only start the game through Commander when I am in port and going to start a new patrol?

You see my question is do I "reroll the dice" on malfunctions and sabatage EVERYTIME I start the game through Commander even when at sea or does it only "roll the dice" at the start of a patrol?

[Samwolf]

Originally Posted by Lanzfeld

I dont go over 16X when on patrol so it is obvious that I save alot during the same patrol because I take so long. When I want to play again I always start SH-3 Commander and "Launch" SH-3 through Commander. Is this the correct way to do it? If I had a random failure in my last game would launching again through Commander reset the malfunction? Should I only start the game through Commander when I am in port and going to start a new patrol?

You see my question is do I "reroll the dice" on malfunctions and sabatage EVERYTIME I start the game through Commander even when at sea or does it only "roll the dice" at the start of a patrol?

Some of the malfucntions will only occur when starting a patrol, others are a "roll of the die" on each load through Sh3Commander. I'm pretty sure that the following can only occur at the beginning of a patrol:

Periscope Malfunction
Snorkel raise/lower time Malfunction
Radar/Sonar Range Malfunction
Flak Gun Reload time Malfunction

[_Seth_]

Maybe a stupid question: Is it possible to launch SHIII from commander, and then start a MP game with sabotage activated? Will commander affect MP games?

[azn_132]

Originally Posted by _Seth_

Maybe a stupid question: Is it possible to launch SHIII from commander, and then start a MP game with sabotage activated? Will commander affect MP games?

Never use SH3C when u play MP GWX games.

[Paajtor]

Yes, I think SH3Commander randomizes to many things...so when players go mp through it, all of them will end up with slightly different SH3-configurations, with the evident result.

[Jimbuna]

To the best of my knowledge SH£Commander is a 'no no' on MP....at least the former testers of GWX certainly don't use it (but only where MP is concerned)

[_Seth_]

Thanx mates! Wont do that then!

[azn_132]

Originally Posted by _Seth_

Thanx mates! Wont do that then!

Remember SH3C is meant to use only in Career.

[HEMISENT]

Originally Posted by Samwolf

Some of the malfucntions will only occur when starting a patrol, others are a "roll of the die" on each load through Sh3Commander. I'm pretty sure that the following can only occur at the beginning of a patrol:

Periscope Malfunction
Snorkel raise/lower time Malfunction
Radar/Sonar Range Malfunction
Flak Gun Reload time Malfunction

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.

Originally Posted by Lanzfeld

Should I only start the game through Commander when I am in port and going to start a new patrol?

Hi Lanzfield, Long time no see. Yes, you can start the game with SH3 Commander then save/exit/restart game(no Commander) and all the files will be there as they were before. By starting a game without commander you won't screw anything up. Make sure you DO NOT rollback commander as this returns everything to the default(pre commander) mode. For further info on this post Jscones in his thread I'm sure he can elaborate.

[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