mirror of
https://github.com/dcs-liberation/dcs_liberation.git
synced 2025-11-10 14:22:26 +00:00
5af4e56f30
This PR: - Introduces a new member of UnitType, hit_points, which is an abstract representation of the durability of a unit, and loads it in from the YAML files in the various subclasses (Ship, Ground etc). - Adds scripts for populating/updating the unit YAML files with hit point data from DCS. This script also gets the data for static objects, but I'll leave the plugging in of static object data into Liberation for another PR. - Updates the unit YAML files by running the above scripts. I did toy with the idea of adding this data to the unit definitions in pydcs via an export from DCS, but it would be a more involved change, since the current pydcs export script runs in the Hooks Lua environment in DCS and AFAICT the hit points (via Unit.getLife()) is run in the mission scripting environment.
18 lines
811 B
YAML
18 lines
811 B
YAML
class: AAA
|
|
description: "The M163 had a fairly limited range from the start. Its 20x102mm round\
|
|
\ gave it a low effective range of only 1,200 meters, and its standard air-defense\
|
|
\ load of HEI-T rounds would self-destruct at approximately 1800 meters, a hard\
|
|
\ limit on range. Additionally, the radar was a range-only set incapable of finding\
|
|
\ targets. In US and Israeli service, the VADS has rarely been needed in its intended\
|
|
\ purpose of providing defense against aerial threats\u2014consequently, the Vulcan\
|
|
\ gun system was in use throughout the late 1980s and early 1990s primarily as a\
|
|
\ ground support weapon."
|
|
introduced: 1989
|
|
manufacturer: General Electric
|
|
origin: USA
|
|
price: 10
|
|
role: Self-Propelled Anti-Aircraft Gun
|
|
variants:
|
|
M163 Vulcan Air Defense System: {}
|
|
hit_points: 3
|