[JScones]

Nah, just follow the example above. SH3Cmdr will pick up via the "|<Offset> OR <Section>^<Key|" value whether the file is binary or text.

For example:

[DieselMaxSpeed]
Probability=193909_20|194001_15|194406_30
IIA=data\Submarine\NSS_Uboat2A\NSS_Uboat2A.sim|x048C|.9
IID=etc

will adjust the Diesel Propulsion max_speed value for the IIA to somewhere between 90% and 100% of the game value (ie 13 with GW).

One note, I had a look at your mod and I don't think changing the crush depth via the .cfg file works - I think it needs to be changed via the .zon file.

[HEMISENT]

[JScones]

Oh, crAsh depth, not crUsh depth...I understand... :doh:

[HEMISENT]

Just an update on the status of the Sabotage/Malfunctions mod.
As of now pretty much all the Malfunction files have been written and are
being tested using Jscones' SH3 Commander. There is no longer a need for the Random folder structure using the new built in randomization capabilities of Commander itself.

Files Affected are:
Ahead Standard, Full & Flank have all been reduced to gradually build up
speed as normal but the max speed attainable is reduced by around 20%
depending on the boat

Diesel Range is reduced between 20 & 60% indicating a fuel bunker leak,
malfunctioning fuel injection system or excessively worn engine.

E Motor Speed reduced similiar to diesel

E Motor Range reduced between 20 & 80% indicative of worn out batteries, electrical system malfunctions or worn E motors excessive draw.

Dive Time increased to simulate worn out manifolds, valves and other
mechanical components needed to flood the tanks and rid the boat of
bouyancy.

Crash Depth randomized to simulate boat taking on too much water or even stuck dive planes and unable to level at proscribed depth.

Periscope view is blurred-time to clear is randomized indicating worn seals or battle damage.

Attack Periscope zoom inoperative simulates mechanical switching
mechanism stuck in position-may require using observation scope.

Schnorkel extend and retract times randomized to simulate
malfunctioning/binding components.

So far this is what has been completed. I've got a few ideas for some additional areas but for the most part it's done. I have not touched the
Type II's or XXI's yet-those will be in an update.

I believe Jscones is working on an updated Commander version that will
allow date specific randomization to occur but for right now these malfunction occurances will have the same odds throughout the war.

Testing is starting probably tomorrow to get a feel for percentages but right now I'm thinking of somewhere around 20-30%.

I'm open to any ideas of additional systems that can be affected.

Cheers!

[Salvadoreno]

[gouldjg]

Really looking forward to it Hemisent

[HEMISENT]

[JScones]

In the meantime, you could build a workaround to get year specific percentages.

Build a file for each year of the war, and just ask that SH3Cmdr users rename the relevant year file to the default file name. That is, if their career is in 1941, they can rename your "Randomised events_1941.cfg" file to "Randomised events.cfg" and SH3Cmdr will pick it up until they replace it with the 1942 file and so on.

Just a suggestion.

BTW, I won't start building the U-boat malfunctions feature until I see your file - so that I can get a good feel for how I should set it up.

[Sailor Steve]

I had a chance to look them over yesterday, and I would rather see smaller percentages over more years, with more specific results:

Instead of 'Max spd 11 knts' I would rather see 'Port Diesel broken down' or 'Radar broken', with a chance at repair.

[HEMISENT]

[HEMISENT]

[JScones]

I don't think that you can damage any component in a way which can be repaired from within the game.

If you change the equipment settings prior to loading SH3, then SH3 will treat them as the stock settings - it doesn't know that the VIIC max diesel speed should be x, not y which you have subsequently set it to. The value y becomes the "base" value that SH3 uses. Any adjustment to that value from *within* the game (ie caused by DD damage) results in damaged equipment which can be repaired, because the new value is different than the base value, ie y. Is this explanation clear?

Conversely, you can "destroy" the equipment prior to loading SH3, but then it's destroyed and can't be fixed at all.

[raymond6751]

Great ideas. Here is my take on the concept.

A programmer can easily use a random number generator to choose which lines in any file to alter and by how much.

Instead of having different folders, why not let the player launch the mod (like the random weather mod) before setting out on a mission.

He will then have altered files and won't know the true limits nor problems that he will encounter on that patrol.

The difficult thing will be how to notify him when one of the modified lines of a .cfg file is used. For instance, max depth change would be a bad discovery under attack. That might show up in test dives en route to patrol area - as leaking reported.

I personally would not use any mod that requires multiple sets of folders on my system. Modify one or two files, with backup of originals - OK. There are just too many ways things can go bad and ruin the whole install.

[raymond6751]

Big thank you for working on this idea. I have felt that having systems 100 percent until enemy action damaged it was totally unrealistic.

I have a problem with the multiple folders idea though.

What if, using SH Commander to launch, a date check were made to determine the date in the scenario loading? Another file, generated by your mod via Commander when the mission started, contains details of when certain lines in certain files get altered.

Commander has the ability to launch messages to the player before loading the game, so the captain can get notified. I am thinking in terms of reducing or increasing the crew recovery rate in certain compartments to simulate illness. Systems can be damaged and the message indicating breakdown. For instance, I got a message from Commander that my starboard engine was destroyed. (in port!)

Obviously something works in that Commander mod already to do what I suggested, but I think the message should have been 'engine malfunction needing shore based assistance'.

If such things could be date related, maybe number of days on patrol, the event could happen at sea instead of port.

How would it look? My stbd engine was totally damaged on the repair screen. Other systems, like torpedo tubes, flooding, radios, and radar/sonar could be affected.

Non-equipment problems like sickness can be reflected in lowering the morale or effeciency.

My main point is the timed effect handled by Commander.

[JScones]