zoneCommander

KO | EN

gitlite — search

#hacktoberfest #react #typescript #llm #golang #go #linux #docker #windows #vue #pytorch #ios #openai #open-source

(★ 26)

DCS mission script for management of capturable zones, and AI logic.

zoneCommander 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# BattleCommander

## Constructor

### BattleCommander:new(saveFileName)

The BattleCommander object is the base object that monitors and runs the whole mission. You only need a single instance of this.
The parameter should be the filename under which to save the persistence data.

Example:

`bc = BattleCommander:new('mymission.lua')`

## Add Zone

### BattleCommander:addZone(zone)
Registers a ZoneCommander object, and enables state tracking and updates for said zone.

Example:

`bc:addZone(exampleZone)`

## Connections

### BattleCommander:addConnection(from, to)

Draws a line between two zones. Does not have any functional value, only visual. Use to help players see where supplies and attacks might be coming from, and to guide player progression.

Example:

`bc:addConnection('zonename1', 'zonename2')`

## Credits and Support items

### BattleCommander:addFunds(coalition, ammount)

Adds the specified ammount of credits to the specified coalition.

Coalition parameters must be set to 1 for Red coalition and 2 for Blue coalition.

Ammount can be any number. If negative, it will substract the credits from the account.

Example:

`bc:addFunds(coalition, ammount)`

### BattleCommander:registerShopItem(id, displayname, cost, action)

Defines an item for the support shop. Note this does not make it available yet only defines the properties of the support item.

First parameter should be a unique string id that identifies the item within the system.

Second parameter should be a string that is displayed in the Support shop menu to players.

Third parameter should be a number specifying the price of the item. When bought this price will be substracted from the coalition account. Will prevent buying if not enough funds.

Fourth parameter is a function to execute whenever the item is succesfully bought. First parameter of the function will always be an object describing the shop item in the format { name='examplename', cost=100, action = functionobject }. You can return a string specifying an error, or just *true* in order to prevent item from being bought in case some conditions are required. This will prevent the cost and stock being deducted.

Example:

```
bc:registerShopItem('exampleid', 'display name', cost, function(sender) 
  --your code here 
end)
```

### BattleCommander:addShopItem(coalition, id, ammount)

Will make an item available for the specified coalition.

First parameter is coalition to add item to. 1 for Red, 2 for Blue.

Second parameter is the string that identifies a previously registered item.

Third parameter is a number specifying the available stock for this item. Once the item has been bought the specified ammount of times it will be removed from the shop menu. A value of -1 will make this available indefinitely.

Example:

`bc:addShopItem(coalition, 'exampleitemid', ammount)`

### BattleCommander:removeShopItem(coalition, id)

Removes an item from the specified coalition shop menu, regardless of remaining stock.

First parameter is coalition to remove from. 1 for Red, 2 for Blue.

Second parameter is the string that identified a previously registered item.

Example:

`bc:removeShopItem(coalition, 'exampleitemid)`

### BattleCommander:startRewardPlayerContribution(basereward, overrides)

Will start rewarding credits for player actions.

First parameter is the base ammount of credits to reward for each kill

Second parameter is used to override the base reward for specific situations, and is a table of the following format:

```
{
  ground = 15, -- base pay for any unit classified as ground and not belonging to any other category
  infantry = 5, --ammount to pay for ground units classified as Infantry
  sam = 30, --ammount to pay for any ground unit having the attributes of ir sam, search radar or track radar
  airplane = 30, -- ammount to pay for any airplanes
  helicopter = 40, -- ammount to pay for helicopters
  ship = 200, -- ammount to pay for ships
  crate = 100 -- ammount to pay for crates delivered to zones
}
```

All of the rewards except the crate deliveries will only be added to the coalition account once players land at a friendly zone.

Respawning or changing slots will reset the ammount of unclaimed credits a player has.

Ejecting will instantly redeem 25% of the unclaimed credits.

Example:

`bc:startRewardPlayerContribution(15,{infantry = 5, ground = 15, sam = 30, airplane = 30, ship = 200, helicopter=40, crate=100})`

## Starting everything

### BattleCommander:init()

Starts the whole monitoring and tracking of every zone and group.
Should be called after everything all the groups and zones have been set up.

Example:

`bc:init()`

# ZoneCommander

## Constructor

### ZoneCommander:new(parameters)

Handles everything related to a single Zone. You will need to create one of these for each Zone you want in your mission.

The parameters table should have the following format:

```
  {
    zone = 'ZoneName', --string, name of the trigger zone in the mission editor(only circular zones work currently)
    side = 1, -- number, 0 for neutral, 1 for red and 2 for blue
    level = 1, -- number, number of upgrades to be spawned from the upgrade list
    upgrades = {'group1','group2','group3'}, -- table, contains strings, names of groups to spawn for each upgrade, they will be spawned in the specified order
    crates = {'c1','c2','c3'}, -- table, constains strings, names of cargo staticobjects, zone will check if any of this is within its borders, triggering a capture/upgrade event if it is, do not add cargo names to the same zone that spawns them as it will trigger instant upgrades
    flavorText = 'description', -- string to display in the F10 radio menu when viewing zone status
    income = 2 --number, credits per tick that the zone will add to the controling coalitions accounts (1 tick = 10 seconds)
  }
```

Example:

`exampleZone = ZoneCommander:new(parameters)`

## Critical objects

### ZoneCommander:addCriticalObject(staticobjectname)

Adds the name of a StaticObject to monitor within the mission. If all of these objects get destroyed, the zone will enter a disabled state, meaning it will no longer be capturable or upgradeable, and will not provide any benefits. Any groups that exist at the moment of distruction will remain, but will no longer be repaireable by resupply events.

Example:

`exampleZone:addCriticalObject('staticobjectname')`

## Triggers

### ZoneCommander:registerTrigger(eventtype, action, id, *runcount*)

Registers a function to run when a zone changes state.

First parameter specifies the event. It should be set to one of the following string values:
- 'captured' - occurs when any side captures the zone, also triggers an upgrade immediatly after the capture
- 'upgraded' - occurs whenever a friendly zone is upgraded, and spawns its next group, 1st upgrade is triggered immediatly after capture
- 'repaired' - occurs whenever a resuply event happens at a zone and there is any group alive with missing members, this group will be restored instead of the next group being spawned
- 'lost' - occurs whenever a zone goes back to neutral state, when all groups are destroyed
- 'destroyed' - occurs when all of the critical objects of a zone have been destroyed, zone will turn black and be effectively useless for the remainder of the campaign

Second parameter is a function that will be called whenever the event is triggered. It will provide the string eventname in the first parameter, and the ZoneCommander object in the second parameter

Third parameter is a string id that is used to keep track of how many times the trigger has run. Used by the persistance code to keep track even after restarts.

Fourth parameter is a number that specifies how many times this trigger can run. Once it has run the specified number of times, the trigger will stop executing. Leave out this parameter to let the event run unlimited number of times.

Example:

`exampleZone:registerTrigger('eventname', function(event, sender) trigger.action.outText('event triggered',5) end, 'triggerid', 4)`

## Groups

### ZoneCommander:addGroup(groupcommander)

Adds a GroupCommander object to the zone

Example:

`exampleZone:addGroup(examplegroup)`

### ZoneCommander:addGroups(listofgroups)

Adds several groups to the zone at once.

Example:

`exampleZone:addGroups({group1, group2, group3})`

# GroupCommander

## Constructor

### GroupCommander:new(parameters)

Creates a new group commander. Parameter should be a single table in the following format:

```
{
  name = 'groupname', -- name of group as defined in mission editor
  mission = 'supply', -- type of mission the group should execute, available mission types defined below
  targetzone = 'zonename', --zonename that should be tracked as the target for this group
}
```

Mission types:

- 'supply' - will spawn if target zone is neutral or friendly
- 'patrol' - will spawn if target zone is friendly
- 'attack' - will spawn if target zone is hostile

Groups only spawn if the zone they were added to is friendly to them.

Example:

`group1 = GroupCommander:new({name='group1', mission='attack', targetzone='FARP1'})`

# BugetCommander

Spends the credits of a coalition on available support items.

## Constructor

### BudgetCommander:new(parameters)

Creates a new buget commander. Parameter should be a single table in the following format:

```
{
  battleCommander = bc, -- reference to the battle commander whos account it should manage
  side = 1, -- coalition whos accounts to manage, 1=Red and 2=Blue
  decissionFrequency = 40, -- how often it should attempt buying an item, in seconds
  decissionVariance = 30, -- will make decissions be delayed up to this many seconds, decided randomly from the range 1 to *decissionVariance*
  skipChance = 5 -- percent chance that the decission will be skipped entirely
}
```

Example:

`budgetAI = BudgetCommander:new({battleCommander = bc, side=1, decissionFrequency=30*60, decissionVariance=15*60, skipChance=5}) `

This will take control of the red coalition buget, and every 30 minutes (decissionFrequency) it will schedule an item to be bought after a random ammount of seconds between 1 second and 15 minutes (decissionVariance). When this time ellapses it will roll a 100 sided dice and if it lands on a number higher then 5 (skipChance), it will make a list of all items it can afford, and attempt buying a random item from that list. Buying an item can fail due to condition specified in the item action. In this case it will attempt buying another random item. This will be repeated up to 10 times or until an item is succesfully bought.

### BudgetCommander:init()

Will start the buget commander monitoring and decission process

Example:

`budgetAI:init()`

zoneCommander

zoneCommander 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

zoneCommander

zoneCommander 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README