Expand AirstrikePower
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 17.4k
- Forks
- 3k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 14
Description
(While I'm aware progress is being made on mouse-drag directional air strikes.)
Can I request the following additions:
- There is a non-formation option when more than one aircraft is in the "squad".
- A break-off option, so aircraft change direction after attacking.
While a flying wedge/ side by side formation is suitable for replicating WW2 strategic bombers. (& C&C Generals)
The tactic was adopted so the bombers could protect each other from enemy fighters with concentrated self defence firepower. (AA gun's/Ball Turrets)
In the Jet/AA missile age this tactic is a liability, effectively increasing the chance the planes will be shot down.
Modern ground attack aircraft, strike from multiple directions, to minimise the chance of being shot down by AA .
To that end, I suggest adding something like:
-
SquadFormation: Random (Or Wedge)
If Random is selected the squad aircraft all spawn at different map edges / attack vectors & engage the target. If Wedge is selected the current behaviour is retained. -
SquadBreakOff: True/False
If True, the units change direction after attack run. (perhaps randomly plus or minus 45 degrees?)
If False, current attack run vector is maintained.
I think this would add more realism to the Airstrike power & the TD Airstrike could perform more like the original game. (If desired)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by locating the AirstrikePower implementation and its current squad formation and attack-run behavior; done means the requested non-formation/random and break-off options are supported while preserving the existing wedge behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100