Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

intel system #32

Open
jtoppins opened this issue Jan 15, 2020 · 1 comment
Open

intel system #32

jtoppins opened this issue Jan 15, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@jtoppins
Copy link
Owner

jtoppins commented Jan 15, 2020

Intel System

Request

As described in the player UI documentation[1] implement the needed functions to affect the described Intel maps.

[1] https://github.com/jtoppins/dct/blob/master/doc/01-playerui.md#intel-menu

Goal

Provide a way for players to participate in the gathering of intel and
refinement of coordinates that result in more detailed and accurate
briefings in follow-on missions.

Execution

Provide ways of improving situational awareness of a given coalition;

  1. allow players fly reconnaissance flights
    • These recon flights will automatically "reveal" various assets with the
      level on intel gained proportional to the level of risk (distance) the
      recon flight must get to an asset
    • recon flights as part of their mission criteria must return to base
      before the intel they have gathered is revealed to the rest of the
      team
  2. allow players to provide 'pireps' via use placed F10 marks to identify
    location and type of enemy assets
    • use a syntax to identify the type of asset and what kind of type
      • Example: "PIREP SAM SA2"

Questions

  • how/can the player generated intel feed into the AI system? This being
    mission assignment and target list generation
  • What kind of intel needs to be reported?
    • The fact someone was "mud spiked" or launched on?
    • that a player sees a factory/ammo dump previously not known?
      • how does the player communicate the efficacy of the location and
        the self reported accuracy of the report?
  • does this intel influence how missions are assigned?
  • does this intel, specifically recon missions, inform BDA instead of the
    perfect information system that is currently in effect for reporting
    when a strike mission is complete?
  • how can players 'cheeze' the system?
    • for the PIREPS they could be abused by exposing or hiding information,
      some examples; Assume the following abuse prevention critera are in place
      1. Marks must be within 5NM radius of the asset type claimed or the pirep
        is considered invalid
      2. Marks identifying the same type of asset cannot be within 10NM
        of another pirep, otherwise it replaces the previous report
    • Example of Abuse/Exploit
      • Example 1: information leakage
        • An abusive player can place marks on the map until until the ones
          that fall within 5NM are accepted thus exposing locations without
          having done any real work
      • Example 2: information loss
        • A trolling player could intentionally degrade the accuracy of a
          previous mark by placing a mark next to it, thereby loosing
          coordinate accuracy
    • Mitigations?
      • if the player is not in the air and within X miles of the report
        it is considered not valid?
      • instead of overriding a previous report incorporate with the previous
        intel and take the centroid thereby increasing the accuracy over time
        To provide a confidence level to the intel track how many times
        different units reported the similar location for the same type of
        asset. This also implies using the scratchpad so it moderates how
        quickly a player can enter data to influence the reporting.
@jtoppins jtoppins added the enhancement New feature or request label Jan 15, 2020
@Moguy164
Copy link

Moguy164 commented Jan 9, 2021

i've seen players mark targets they find on missions, what you could do is save that mark, and then it's kept on next restart, maybe assigning it to the target's mission could also improve it, i don't know if it's possible, but could you not make it that if a mark is set within a set distance of unit/area, then it can assign that mark to a mission and remove it once complete

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants