Malfunctions/Sabotage in SH3Cmdr???
 

As you would have read here, Hemisent has done some great work on developing randomised u-boat equipment malfunctions and simulated damage caused by sabotage. These creations utilise SH3Cmdr's recently added "randomised events" feature.

I'm keen to gain your feedback, as SH3Cmdr users, on whether any or all of his creation should be included as "stock" in SH3Cmdr R2.6. As the changes share the generic "Randomised events.cfg" file, it is not feasible to add a specific selectable option to SH3Cmdr. Hence any additions will automatically execute unless manually removed.

If after reading teh above thread you need further clarification of content, I'll have to defer to Hemisent. I'm sure he'll be happy to answer any specific questions.

Malfunctions with sabotage overlayed. :rock:

everything!! combined!!!

"Malfunctions with sabotage overlayed" sounds good, but only as an option, not as default.

The tougher it gets, the better! Overlayed! :up:

I dont like sabotage but certainly defects.

I vote for both combined. If possible effects (especially sabotage) should only change from patrol to patrol and not every time the user starts SH3 Commander.

Cheers
Mr. Fleck

Good point about sabotage events not randomising mid-patrol. Hemisent, something to consider, if haven't already?

I voted for malfunctions only.

I think the "sabotage" angle, that seems to be very prominent in some U-boat histories, is way overdone. I have no stats to back up this feeling but if you read mid to late war histories I rarely read of a breakdown or malfunction...the word "sabotage" is always used.

Its difficult for me to imagine that the U-Boat arm could be so sloppy as to allow (seemingly) constant tampering of their boats by foreign dock-workers.
I would guess that poor quality parts, overworked or tired techs, lack of proper parts, increasingly inexperienced crews, and the rush to get returning boats back to sea, are the main cause of problems not "sabotage."

Again, that is my opinion based on years of reading and study.

On a more practical note did I read correctly, in the other thread, that any malfunctions generated will not be repairable at sea (in-game)? i.e., through the standard SH3 repair process?

EDIT: Could this feature be made a "check-box" selectable option in SH3 Commander? Perhaps selectable like the Fatigue models..."Malfunctions Only" or "Malfunctions and Sabotage."

Thx

SH3CMDR 2.6
 

The BEST of all would be a check box to use or not use one or both mods. I for one would like them both. As for not repairing in mid patrol, any good sabotager would pick something that couldn't be fixed easily or at all.
This is a game and should be fun. It should invoke a response from the player, and nothing gets a response better than when something you can't do anything about goes wrong.
I had a great career going once and CMDR retired me. I was really pissed off, but that's life; and that is realism.
DTB states that the lack of uncertainty is a draw back to realism. I fully agree and enjoy it in a game where things I can't control screw up my plans.
This is the only game I have ever played more than a few times and the reason is the uncertainty, and the wonderful variability supplied by its great modelers. Increasing them will only make it better.
I don't have the computer skills to implement these changes myself, so I rely upon you (all) to make them available for me.
irish1958

Fantastic Idea! :up: All accounts of U-boat operations mention the "odd" malfunction of systems.

:rock:

If neither is repairable, neither should occur on more than 1% or 2% of patrols. What I would really like is breakdowns that are repairable on all patrols, and sabotage, again, on maybe 1 or 2% or patrols.

I would say not make them a part of SH3 Commander, but have them as seperate JGSME.

Install separately
 

:ahoy: I'd like the flexability of adding the features myself

My vote goes to malfunctions.

malfuntions, some repairable at sea others not.