mirror of
https://github.com/dcs-retribution/dcs-retribution.git
synced 2025-11-10 15:41:24 +00:00
bb1a066ff7
This PR allows campaign creators to incorporate map objects (referred to as Scenery in the code) into their Liberation campaign. Map objects are defined using white trigger zones created by right clicking on scenery and clicking `assign as...`. Objective groups are defined by creating a blue TriggerZone surrounding the centers of the white trigger zones. The type of objective is determined by the campaign creator, assigning the value of the first property of the blue TriggerZone with the objective type. Map objects maintain their visually dead state by assigning a `Mission Start` `Scenery Object Dead` trigger to the trigger zone. It is important for the Liberation generated TriggerZone to be as small as possible so that no other scenery is marked dead by DCS. TriggerZones are hidden during gameplay (DCS behavior. I don't know if it's possible to turn that off.) TriggerZones are visible in the mission editor and mission planner however. If a player is using an older plane, it is important for them to remember where the target is. In the mission planner, the trigger zones' will be blue or red depending on which faction the map objects belong to. Inherent Resolve campaign has been modified to integrate scenery objects. ### **Limitations:** - Objective definitions (Any Blue TriggerZones) in campaign definition cannot overlap. - Map object deaths in `state.json` is tracking integers. You won't know what died until debriefing. - No images for the various buildings. In theory it can be done, but an unreasonable amount of work. - Every blue trigger zone must have a unique name. (If you let DCS auto increment the names this is not a concern. - No output to screen when scenery object is dead. You can see the building drawn as dead in the F10 map though. ### **Pictures:** An objective:  How the objective looks once in the mission planner/editor. This objective belongs to the enemy faction: 
57 lines
2.2 KiB
Python
57 lines
2.2 KiB
Python
from pathlib import Path
|
|
|
|
|
|
def _build_version_string() -> str:
|
|
components = ["3.0"]
|
|
build_number_path = Path("resources/buildnumber")
|
|
if build_number_path.exists():
|
|
with build_number_path.open("r") as build_number_file:
|
|
components.append(build_number_file.readline())
|
|
|
|
if not Path("resources/final").exists():
|
|
components.append("preview")
|
|
|
|
return "-".join(components)
|
|
|
|
|
|
#: Current version of Liberation.
|
|
VERSION = _build_version_string()
|
|
|
|
#: The latest version of the campaign format. Increment this version whenever all
|
|
#: existing campaigns should be flagged as incompatible in the UI. We will still attempt
|
|
#: to load old campaigns, but this provides a warning to the user that the campaign may
|
|
#: not work correctly.
|
|
#:
|
|
#: There is no verification that the campaign author updated their campaign correctly
|
|
#: this is just a UI hint.
|
|
#:
|
|
#: Version history:
|
|
#:
|
|
#: Version 0
|
|
#: * Unknown compatibility.
|
|
#:
|
|
#: Version 1
|
|
#: * Compatible with Liberation 2.5.
|
|
#:
|
|
#: Version 2
|
|
#: * Front line endpoints now define convoy origin/destination waypoints. They should be
|
|
#: placed on or near roads.
|
|
#: * Factories (Workshop_A) define factory objectives. Only control points with
|
|
#: factories will be able to recruit ground units, so they should exist in sufficient
|
|
#: number and be protected by IADS.
|
|
#:
|
|
#: Version 3
|
|
#: * Bulker Handy Winds define shipping lanes. They should be placed in port areas that
|
|
#: are navigable by ships and have a route to another port area. DCS ships *will not*
|
|
#: avoid driving into islands, so ensure that their waypoints plot a navigable route.
|
|
#:
|
|
#: Version 4
|
|
#: * TriggerZones define map based building targets. White TriggerZones created by right
|
|
#: clicking an object and using "assign as..." define the buildings within an objective.
|
|
#: Blue circular TriggerZones created normally must surround groups of one or more
|
|
#: white TriggerZones to define an objective. If a white TriggerZone is not surrounded
|
|
#: by a blue circular TriggerZone, campaign creation will fail. Blue circular
|
|
#: TriggerZones must also have their first property's value field define the type of
|
|
#: objective (a valid value for a building TGO category, from `game.db.PRICES`).
|
|
CAMPAIGN_FORMAT_VERSION = 4
|