Harass: Bugfix: double harassment of FOBs. #7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See here for explanation: #5
A FOB can have half the AI of a 'capture' phase AO assigned to harass it because the harass subsystem assigns multiple AI objectives to bother players at the FOB
It doesn't make sense to 'pursue' players at a FOB when they are mostly stationary, and it's probably better tohave those AI tasked somewhere else (tracking players out in the field or on other 'defend'/ambush' objectives).
There's a risk of FOBs feeling under-harrased after the change, but we can tweak the harassment period and/or the attack intensity here if desired: https://github.com/Savage-Game-Design/Paradigm/blob/development/server/functions/harass/fn_harass_create_squads.sqf#L80-L89