the possibility of "sabotage" or a random breakdown is a great addition. How it can be effectively incorporated and how each player chooses to deal with it remains to be seen. The randomization through SH3 commander enables the effect. As has been suggested for TL, save and reload after each battle to simulate changing sea conditions could also work here. You may discover a random breakdown/sabotage but it wouldn't neccesarily mean you would have to abort your patrol. Saving and reloading would again shuffle the files and possibly remove the problem but engage another. The time you as a player decided to live with the breakdown depends on your level of realism. Perhaps a guide would need to be written so that if a problem were repairable at sea you would be told how long that repair would take so that you would need to play out that period of game time before the save/reload.
This is a great idea, making it work within the limits of SH3 will be the challenge.
Perhaps a combination of the ability of SH3Gen and SH3 Cmndr could be combined. One program could organize and shuffle the random files as well as write to the patrol logs what damage has occured and how long it will take to fix. SH3 Gen recommends getting clear of home port before using its function(stationary ships sink other waypoint issues) it wold also work here in a sense that if you did reciecve a critical damage problem you would not be to far away to return to base. Writing the damage report to the patrol log would remove the surprise factor but you could also do that by running through your systems at the start of each patrol.
|