View Full Version : Damage control qualification
01-28-2008, 05:24 AM
Just thinking...if you've got two officers with damage control quals and one is already assigned to the control team and dealing with one compartment, would the other have a significant affect on the repair time if he was assigned to another flooding compartment?
01-28-2008, 05:29 AM
Not as significant as the one in the damage control team :nope:
01-28-2008, 05:34 AM
Oh well, obviously no point in giving all my officers the qualification then. Be useful if it did work though!
01-28-2008, 05:39 AM
It would give you the option of rotating the officers during attacks as fatigue levels rise, allowing one to rest.
01-28-2008, 07:11 AM
I usually have two qualified for that very purpose! A well rested, trained mechanic has made the diffrence between a watery grave and limping home a few times...
01-28-2008, 12:02 PM
Sorry mate, but you didn't ask/enquire as to how many you should have :nope:
If you had.....TWO is the obvious recommendation, for fatigue/respite purposes. :up:
02-10-2008, 03:09 AM
It would still be useful to know if giving petty officers repair qualifications has any affect when they are at their stations (not in sleeping quarters). I would presume it might, as machinist/engineer qualifications help with those operations.
Kaptain Hans Wolf
02-10-2008, 06:29 AM
yea, i agree with those who said to keep two men with one skill. at the moment im trying to assemble a first class four man sonar/radar team, as i hate having to put unqualified men on the hydrophone and risk the safety of the crew!
YUp, a strong damage control team will make a huge difference if you take serious damage. My priorities are:
Patrol 1 --harbour cruise (funker for hydrophone)_
Patrol 2 -- " " " " mechanic officer
Patrol 3 -- combat mechanic petty officer
Check out the Strategies for Survival article in my kielman webbie
02-10-2008, 12:08 PM
I still die...
They don't work real good...
Maybe it's that Hot, Passionate Pink boat I have?
vBulletin® v3.8.4, Copyright ©2000-2013, Jelsoft Enterprises Ltd.