[WIP] Recommend altitude values for aircraft YAML files

[Copilot]

• Research cruise/combat altitudes for all ~210 aircraft missing altitudes section using web searches
• Add altitudes.cruise and altitudes.combat (feet) to every aircraft YAML missing them, each with a comment containing a source URL
• Skip fictional/Star Wars aircraft (AWING, XWING, YWING, TIE, TIE_INTER, CORVETTE, FAUCON, HUNTER, naboo_starfighter, tie_bomber_2) — no historical data exists
• Validate YAML syntax is correct

Original prompt

i have created a new branch called fix-aircraft-altitudes.
i want you to read each aircraft yaml, and where
altitudes.cruise / altitudes.combat
is not set
reocommend values based on accurate historical data

you may edit the files
each added line must have a comment after it ( like # this), with one URL that gives the best supporting evidence to the number you decided

[Chronological Review: The conversation began with the user asking about weapon introduction dates and where settings for modded weapons should go. The user expressed a desire to explore without making changes. They then requested to read YAML files in a specific directory to identify weapons missing certain fields, followed by creating a feature request ticket for those weapons. The user confirmed that GitHub (gh) was installed and requested to check the markdown format. They inquired about the weapons of the SU-15 that do not exist in the specified directory and requested historical introduction years for specific weapons. The user asked about the source of historical dates and suggested using Google for accurate information. They continued to request checks for AIM-54s and AIM-7s, and inquired about IOC entries for aircraft. The user asked for explanations of fields in aircraft YAMLs, requested raw markdown responses, and questioned the purpose of the patrol field. They sought recommendations for altitudes for the F-14B based on historical data and finally instructed to read each aircraft YAML to recommend values for altitudes where not set, allowing edits with supporting evidence.]

[Intent Mapping: The user explicitly requested to explore weapon introduction dates, check YAML files for missing fields, create a feature request ticket, confirm GitHub installation, check markdown formatting, identify weapons for the SU-15, gather historical data for weapon introduction years, and understand the purpose of certain fields in YAML files. They also sought recommendations for altitude settings for the F-14B and instructed to edit YAML files with comments and sources.]

[Technical Inventory: Technologies mentioned include YAML for configuration files, GitHub for version control, and historical data sources for weapon introduction years. The user is working within a DCS (Digital Combat Simulator) modding context, specifically focusing on aircraft and weapon configurations.]

[Code Archaeology: The user is working with the file YWING.yaml located at z:\code\dcs-retribution\resources\units\aircraft\. They have discussed various fields within YAML files, including altitudes.cruise and altitudes.combat, and the need for historical accuracy in these configurations.]

[Progress Assessment: The user has made progress in creating a new branch for fixing aircraft altitudes but has not yet completed the task of reading and editing the YAML files. They have outlined specific actions to take regarding missing altitude settings.]

[Context Validation: All critical information for continuation is captured, including the user's requests for exploration, data gathering, and YAML file modifications.]

[Recent Commands Analysis: The last agent commands involved reading aircraft YAML files to recommend altitude values where not set. The user specified that each added line must include a comment with a URL for supporting evidence. The immediate pre-summarization state involved preparing to execute these commands and gather historical data for accurate recommendations.]

1. Conversation Overview: - Primary Objectives: The user requested to explore weapon introduction dates, check YAML files for missing fields, create a feature request ticket, confirm GitHub installation, check markdown formatting, identify weapons for the SU-15, gather historical data for weapon introduction years, and understand the purpose of certain fields in YAML files. They also sought recommendations for altitude settings for the F-14B and instructed to edit YAML files with comments and sources. - Session Context: The conversation flowed from initial inquiries about weapon data to specific requests for YAML file modifications and historical accuracy in aircraft configurations. - User Intent Evolution: The user's needs evolved from general exploration to specific data gathering and editing tasks, culminating in a detailed request for altitude recommendations based on historical data.

2. Technical Foundation:

• YAML: Used for configuration files related to aircraft and weapons in the DCS modding context.
• GitHub: Version control system confirmed to be installed for managing code changes.

3. Codebase Status:

• File Name: YWING.yaml
• Purpose: Configuration file for the Y-Wing aircraft in the DCS mod.
• Current State: The user is exploring and preparing to edit the file based on historical data for altitude settings.
• Key Code Segments: Fields related to altitudes.cruise and altitudes.combat are of particular interest.
• Dependencies: The...

Created from VS Code.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.