Quote:
|
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.