Tacphone - New Component - Create

[SpicyBagpipes]

When merged this pull request will:

• Add tacphone, a cTab/ATAK-similar device for BFT, CAS and similar short-notice planning/coordination

Please refer to thread in ace discord - https://discord.com/channels/976165959041679380/1334235988158845010 (#general-ace3)

Hate the tacphone name, open to suggestions for better names. Preferably banana related.

IMPORTANT

• If the contribution affects the documentation, please include your changes in this pull request so the documentation will appear on the website.
• Development Guidelines are read, understood and applied.
• Title of this PR uses our standard template Component - Add|Fix|Improve|Change|Make|Remove {changes}.

[SpicyBagpipes]

https://discord.com/channels/976165959041679380/1334235988158845010/1334247020512149647

What I was thinking from an end-user POV calling in CAS, more or less:

• bro needs cas, pulls up his handy ace banana phone
• bro places marker where he needs CAS, gets option for marker stuff, and groups to put marker into (not same as group _unit, groups as part of this system)
• bro calls the aircraft, aircraft can cycle to marker with keybinds or w/e
• aircraft can drop jdam or slew tgp/whatever to marker position
• 👍 guys are dead, delete marker/mark as resolved and it goes into some other thing that is hidden by default that you can filter again

[SpicyBagpipes]

For groups/channels, my bullet points are:

• Groups are set up/established by players at mission start/mid-mission/whenever.
• Groups will be able to be locked for joining/invite only.
• Only groups of sides you are allied to will show.
• Individuals can be part of multiple groups at once.
• Markers can be part of multiple groups at once.
• Markers will have some sort of symbology to indicate their channel. See image.

Reasoning for the above: Side channel in regular arma map becomes cluttered easily with often irrelevant information. Doing it this way allows for JTAC/Forward Observer to communicate markers easily, but only to those who need to see them. You could, for example, have the following groups:

• Command
• Fire Control
• CAS
• Alpha 1-1
• Alpha 1-2
• Alpha 1-3

Alpha 1-1->1-3 would not need to see CAS markers, as squad leaders could be part of the command group at the same time as their own groups, and for CAS to only be part of their own groups & fire control in order to mitigate clutter and such.

[SpicyBagpipes]

Applications would be able to be built in this also as per Dedmen request. Current plan for release is:

• BFT/Whatever it gets named
• Messaging system (Potentially a CBA setting to disable - PR for TFAR/ACRE to limit/queue messages according to radio range?)

Open to more ideas.

[LinkIsGrim]

Name

BananATAK.

Open to more ideas.

• Link to Kestrel/Vector 21?
• MicroDAGR integration?
• ATragMX? (Or an ingame version of Strelok using the same code).
• Steal the GPS tracker thing from Dedmen's TacControl

[SpicyBagpipes]

Name

BananATAK.

ATAK is unfortunately a trademarked name

Can do all the rest though

[SpicyBagpipes]

Having an ace wiki app would be pretty useful imo, just requires CT_WEBBROWSER which is (likely) beyond my abilities

[TheCandianVendingMachine]

Having an ace wiki app would be pretty useful imo, just requires CT_WEBBROWSER which is (likely) beyond my abilities

imo keep the scope small with the ability to create different “apps” in mind. we can add PRs to add functionality later

[SpicyBagpipes]

Agreed, was meant as a later thing