Jump to content

Recommended Posts

Posted

Hiya!

When building multiplayer missions having runway strikes being done and available always adds quite a thrill.
However, when it succeeds it's hard to continue to adapt the balancing.

Currently runways are only repaired after 60 minutes (hardcoded) as far as I can see.

What would be awesome if would for example be something like:

---repair the given runway for operations
---@param runwayName string @the name of the runway, as also specified in Airbase:getRunways()
function Airbase:repairRunway(runwayName) end

---OPTIONALLY
---sets whether or not DCS will automatically repair runways after 60 minutes
---@param autoRepair boolean @true or false
function Airbase:setAutoRepair(autoRepair) end


The idea is that in bigger dynamic missions it would be awesome to balance the runway repairs ourselves.
(eg. faster when the resources/personnel at the base are higher and slower when certain resources are lower).
The second function would be to disable automatic repairs.
This would be in line with the logic of airbase captures, where you can also enable/disable the automatic capture and then force the capturing yourself.

PS. Removing the craters itself doesn't repair the runway it seems via world.removeJunk() as AI doesn't want to take off even when the runway is pristine after that.


PPS. To all those having the itch commenting underneath here that it wouldn't be realistic. Please just don't.
This would just add options, and options are what us mission makers can use.
 

  • Like 7
  • Thanks 1
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...