Logistics Support

From ALiVE Wiki
Revision as of 05:23, 10 August 2014 by Friznit (Talk | contribs)

Jump to: navigation, search

Template:Partof Support

Onebit note.png Note: Module is part of 0.7 Release

How It Works

ALiVE logistics support for players comes in two parts. The first is a simple lift & shift system for moving objects and crates around. The second part is a resupply module that allows players to replenish weapons and materiel.

Player Logistics

The Player Logistics module is a simple lift and shift system that allows player to move and place objects, load crates into cargo and tow vehicles. All objects and player vehicles are fully persisted in the ALiVE database when the Database Module is placed.


Usage: Logistics Support is ON by default. Use the ALiVE Action Menu to Activate Actions for the player logistics system, then simply walk up to an object and you will get a context sensitive Player Action to move, load or tow the object.


Logistics Support can be temporarily enabled or disabled via the ALiVE menu. This will remove ALiVE Logistics from the action menu and is useful if you want to use an alternative Player Logistics mod whilst still benefiting from the ALiVE object and vehicles persistence. It can also help client performance slightly as the log routines are not running.

Mission editors can disable all or part of the Player Logistics System by placing the Disable Logistics module in the editor (under ALiVE Systems)

Player Resupply

Player Resupply Dialogue

The Player Resupply module provides a dialogue for players to request new vehicles, weapons, defence stores and AI teams from the logistics Force Pool.


Usage: Place the Player Resupply module in the editor. Do not sync it to anything. Players require an ALiVE support tablet in their inventory to access the resupply dialogue from the ALiVE Action Menu (classname alive_tablet or can be found in a standard support crate). Choose the desired replen demand and select the Drop Off point on the map display.


The resupply options are context sensitive pick lists, so for example you will not be able to air drop a tank!

  • Air Drop: simulates a parachute drop of stores or troops. Air drops have a limited capacity but are tactically the safest means for delivering equipment. Be aware that para drops are subject to wind!
  • Heli Insertion: transport helicopters will move from the current Military Logistics Insertion Point to the requested drop off point. Helicopters have very limited capacity but are a fast and accurate means of insertion. This is also the only method of delivering new rotary wing aircraft.
  • Convoy: road convoys have a huge capacity to move equipment and are the only way to deliver the heaviest vehicles. However, they are vulnerable to interdiction and supply lines must kept clear.


Reinforcements: select an AI reinforcement group or individual in the current payload to set the behaviour on arrival. Options are

  1. Join Player Group - the units will move to the group leader.
  2. Static Defence - units will take up positions in buildings or nearby static defences.
  3. Reinforce - units will be assigned to OPCOM and await tasking.


Onebit note.png Note: Player Resupply Requests use the same Military Logistics Force Pool as OPCOM! If players hog all the limited resources for your side OPCOM may run out, severely impacting your ability to win the war!


Editor Notes

  1. Objects do not need to be named for logistics or persistence. ALiVE will detect any object spawned into the game at any point (it may take a few seconds to register). Objects are persisted when they are picked up or dropped, the inventory is closed or when the player disembarks.
  2. Objects placed in the editor are unique and once moved (and saved to the database) they will always be regenerated in their last saved location, even if you delete the original editor placed object. If you move or replace the an object in the editor, it will be treated as a new unique object.
  3. ALiVE Player Logistics uses DisableSimulationGlobal and HideObjectGlobal to simulate objects in cargo. Note that you cannot setpos on an object until simulation has been enabled again. Any Init lines will remain (e.g. for a custom ammo crate).