OK, the LAST AND FINAL CALL for SH3Cmdr additions!

[JScones]

Originally Posted by HEMISENT

The "ChooseFrom" is all that changes. The settings pretty much stay the same but the percentages dictated by the "ChooseFrom" line are what changes. eg 1939 setting x=15%, 1940 setting x=18% etc-(Does that make sense?)

Yes, thanks. I need to find a solution that balances flexibility with ease of use. I'll ponder it a bit...

Originally Posted by HEMISENT

Question
using your lateral thinking theme from a few days ago-
Can I do this?
seperate actions using the same file.
*For testing purposes only*

[0_data\Library\Cameras.dat]
;Randomly adjusts blur duration time to simulate periscope seal/lens integrity,
FileType=B
ChooseFrom=8 ;50% chance-if Commander does not pick one will it move to the below files?
RndMidPat=1

0_x2ECD=20 ;Attack Periscope Drops duration[4]
0_x2EE2=20 ;Attack Periscope Blur duration[3]
1_x2ECD=37
1_x2EE2=37
2_x2ECD=60
2_x2EE2=60
3_x2ECD=3600
3_x2EE2=3600
;--------------------------------------------------------------------
[1_data\Library\Cameras.dat]
;Randomly disables attack scope zoom, simulates periscope magnification breakdown.

FileType=B
ChooseFrom=4 ;50% chance-if Commander does not pick one will it move to the below file?
RndMidPat=1

0_x302F=1.5
0_x304E=1.5
1_x302F=6.0
1_x304E=6.0
;--------------------------------------------------------------------
[2_data\Library\Cameras.dat]*this is a combination of the above two files*
;Randomly adjusts blur duration time and disables attack scope zoom to
simulate periscope seal/lens integrity combined with inoperative magnification

FileType=B
ChooseFrom=2
RndMidPat=1

0_x2ECD=20
0_x2EE2=20
0_x302F=1.5 ;Zoom
0_x304E=1.5 ;Zoom
1_x2ECD=20
1_x2EE2=20
1_x302F=6.0
1_x304E=6.0
;--------------------------------------------------------------------

Sabotage files have potential for numerous events all using the same file-mostly it's the NSS_U boatx.sim file. In the Random folder structure it works fine but using Randomized events.CFG I had problems with conflicting files shutting each other out. If the avove example will work then that solves my problem. If it will not work then I have to completely rewrite the Sabotage files in a format that is Randomized events.CFG friendly

Using your above example, [1_data\Library\Cameras.dat] will still run regardless of whether [0_data\Library\Cameras.dat] ran or not. Likewise [2_data\Library\Cameras.dat] to [1_data\Library\Cameras.dat].

But using the above example, the 0_ and 1_ sections are meaningless as the 2_ section will *always* result in a selection which will overwrite a 0_ or 1_ selection anyway.

But yes, you can build layers. It's prolly like building a house. Get the foundation down first, then add the different floors. Prolly not the best analogy, but you get the idea.