-
-
Notifications
You must be signed in to change notification settings - Fork 79
Example Siege Config
Once configured to the user's needs/specifications, put this file in: '(server-root)/plugins/Movecraft'
This is an example 'siege.yml' file, which works with Movecraft Versions 5 and up. All siege configurations go in here. Siege is basically KOTH (King of the Hill), except, the hill is a predefined World Guard region, and the king is a craft or group of allied crafts that hold off in the area.
The base-block. There is only one 'sieges:' block in this config.
sieges:
The name of the regions configuration. Mainly meant for the user of the config to help identify which region-config they are working with. (Has no real impact on the gameplay.)
'<Region-Config ID>':
The actual World Guard Region name/ID, that people fight in.
SiegeRegion: '<worldgurd region name>'
The actual world Guard Region name/ID, which is gained from the siege.
RegionToControl: '<worldgurd region name>'
The PILOTED crafts in the region required to win. Unpiloted vehicles wont count towards a victory/region control.
CraftsToWin:
Same as what you would put on a vehicle-control sign.
- '<Movecraft vehicle name 1>'
- '<Movecraft vehicle name 2>'
The price to begin fighting over territory.
CostToSiege: <some number of vault-money>
This means, that per region captured, the 'CostToSiege' value is doubled for this particular region, per region owned/controlled
DoubleCostPerOwnedSiegeRegion: <true/false>
This is earned Per-Day (Ingame or IRL; I, cannot remember...)
DailyIncome: <some number of vault-money>
These times are in seconds 0 seconds = 0 hour(s); 3600 seconds = 1 hour(s);
The delay for people to get ready, repair stuff, and/or just get to the contested region/territory before it starts. (In seconds)
DelayBeforeStart: 1200
How long a siege can occur before ending. (In seconds)
SiegeDuration: 2400
This is the lower range. Best left at 0. (In seconds)
ScheduleStart: 0
This is the Upper range, best to configure this value to be the sum of 'DelayBeforeStart:' and 'SiegeDuration:' values. (In seconds)
ScheduleEnd: 3600