Difference between revisions of "Persistence"

Revision as of 11:28, 2 May 2014

ALiVE Data

ALIVE Persistence stores mission and player data on the central ALiVE database, allowing players to retain the state of the mission across multiple sessions. This works both for players disconnecting and rejoining in progress as well as between server restarts.

Persistence is configurable on different modules, allowing mission makers and server admins to choose the level of mission data to be stored and recalled. To turn on persistence, choose the option in the relevant module. Persistence is OFF by default.

Persistence requires an account on the ALiVEmod.com War Room.

Stores the state of virtual AI profiles including current location and combat effectiveness.

Stores the current OPCOM orders relating to each Objective. If OPCOM persistence is off when a server starts, the AI Comd will review the current state of assigned objectives based on the location of Profiles and issue fresh orders as normal.

Ambient CQB Sectors are stored to DB, not individual CQB units. Players should take care clear a sector fully before a server restart. If not, the sector may still be considered occupied and fresh CQB units will spawn in that sector.

A large amount of player data can be saved to the database via the Player Persistence module, including location, medical state and equipment.

Editor Notes

Note that when editing missions that are persistent, units placed on the map in the editor may be moved to their stored location when the server restarts!

Persistence is predicated on the mission.pbo name. You can can change the displayed mission name in mission.sqm no problems, but the pbo must remain the same. To reset the Persistence state of a mission (start a fresh one) simply rename the pbo file.

Developer Notes

Object persistence including empty vehicles is not yet developed. This will form part of the Player Logistics module in release 0.7