"Hold Fire on Sighted" Setting for LWCs

[tepid basin]

Premature release is a problem for CRAM cannons everywhere. They spawn, they see an enemy, they get too excited, and they fire off wildly into the night. One of the single most impactful and single lowest-effort things that you can do to make CRAM better is to breadboard it up to keep it from firing for a second or three on spawn. It's gotten to the point where the DWG Crossbones will be getting breadboard pretty soon for that exact purpose--because if you aren't doing it, you're throwing away your shot. But then that means that players roll into the campaign, see their CRAM zip off into nowhere while the enemy's doesn't, and since in campaign mode you can't exactly check out enemy breadboard they're stuck.

I propose adding a setting to LWCs that allows players to set a duration, from say 0 to 5 seconds, during which all weapons on that LWC will hold their fire after a new enemy is sighted. Easy to use and set, cuts out the need for that pesky breadboard to solve an age-old problem.

[lilac creek]

I think this applies to every single weapon not just crams. "First shot delay" setting sounds good, could probably go up to 10 or 30 seconds, but just have default value at 3s or 5s.

[tepid basin]

Yeah, I ran into it all the time in my very early paccoping phase. These days I just care about it because I know that every OW godly could be improved by like five bb components, but... bb on every craft of an easy faction? Really? And just for that one thing?

[hallow cargo]

you can partially do this with the detection error minimum but it doesn't wait long enough usually

[tepid basin]

Yeah, even with it cranked down it seems pretty frequent. Depends some on craft load order, I think, but I saw it a decent amount replaying the campaign.

[thorn jewel]

There used to be a setting to make weapons wait before firing before we introduced weapon sync
We should bring that back

[hallow cargo]

that added a delay to every single shot which reduced your rpm

[gusty acorn]

3 seconds would be plenty, and anything more than 5 would be pointless.
But yeah, a customizable delay for preventing certain weapons from firing within a short period of the target changing (not just initial sighting) would be great for any of the slower firing weapons (CRAM, PAC, pierce laser, plasma, large gauge/DIF APS)

Would likely mean that mainframes would be recording how long the target has been locked, and LWCs are configured by players for how long they want the target to be have locked by the controlling mainframe before the LWC is allowed to fire.
This stat (time since target has been locked) should be available for breadboard too.