Difference between revisions of "ALiVE Data"

From ALiVE Wiki
Jump to: navigation, search
Line 4: Line 4:
 
=ALiVE Data=
 
=ALiVE Data=
 
[[File:wart.png|thumb|right|400px|AliVE War Room]]
 
[[File:wart.png|thumb|right|400px|AliVE War Room]]
ALiVE continually captures data about the state of the current session for all AI units, players and the tactical situation.  There are two main uses for the Data module.  Firstly, it provides a link to the online War Room where mission data is published for review, including statistics, server monitoring and post-mission replays.  Secondly, the module enables multi-session persistence by storing mission data on the local machine or via an easy-to-use cloud service.
+
ALiVE captures data about the state of the current session for all AI units, players and the tactical situation.  There are two main uses for the Data module.  Firstly, it provides a link to the online War Room where mission data is published for review, including statistics, server monitoring and post-mission replays.  Secondly, the module enables multi-session persistence by storing mission data on the local machine or via an easy-to-use cloud service.
  
  
Line 22: Line 22:
 
==Dedicated Servers==
 
==Dedicated Servers==
 
ALiVE was built to run on a dedicated server and will work just as well in single player.  However, hosted multiplayer can sometimes cause unexpected results so we recommend setting up a "local dedicated server" instead.  We have provided some guidance for setting up [[local dedicated servers]] here.
 
ALiVE was built to run on a dedicated server and will work just as well in single player.  However, hosted multiplayer can sometimes cause unexpected results so we recommend setting up a "local dedicated server" instead.  We have provided some guidance for setting up [[local dedicated servers]] here.
 
 
 
==Resetting Stats and Persistence==
 
 
* War Room uses onLoadName (in description.ext) as a unique id for recording stats.
 
* Persistence uses the mission.pbo filename as a unique id for saving persistent states.
 
 
For example:
 
 
# To keep the same Stats and Mission Persistence, keep both onLoadName and Filename the same.
 
# To reset Persistence but keep Stats (for example, to retain stats across a campaign of several ops), change the Filename only.
 
# To reset Stats but keep Mission Persistence (for example, to record separate stats for each session), change the onLoadName only.
 
# To reset both Stats and Persistence, change onLoadName AND Filename.
 
 
None of these effect the mission name that shows in the game browser (which is set in mission.sqm) so you can call it whatever you want.
 
  
  

Revision as of 04:39, 16 June 2017

Onebit note.png Note: The server plugins now support Windows and Linux dedicated servers. There is also an optional PBO to automatically enable Perf Mon for all missions


ALiVE Data

AliVE War Room

ALiVE captures data about the state of the current session for all AI units, players and the tactical situation. There are two main uses for the Data module. Firstly, it provides a link to the online War Room where mission data is published for review, including statistics, server monitoring and post-mission replays. Secondly, the module enables multi-session persistence by storing mission data on the local machine or via an easy-to-use cloud service.


  • ALiVE Data Module This module is required for both mission persistence and for War Room data services.


  • War Room ALIVEmod.com War Room is a free online service for reviewing mission statistics on customised Clan or Group pages.


Mission Persistence

Multi Session Persistence stores the location and status of mission critical elements and reloads them when the mission is next run. Setting up persistence locally or in the cloud is straight forward. There are few things worth noting, especially for mission makers.


  • Persistence See here for how to set up mission, player and data persistence for multi-session operations between rejoins and server restarts for each ALiVE module.


Dedicated Servers

ALiVE was built to run on a dedicated server and will work just as well in single player. However, hosted multiplayer can sometimes cause unexpected results so we recommend setting up a "local dedicated server" instead. We have provided some guidance for setting up local dedicated servers here.


Local Databases

It is possible to set up a local CouchDB for persistence but we cannot provide support for it. A guide is available on our github pages. The War Room is a free of charge Software as a Service for the ArmA community and our limited resources are dedicated to ensuring this is maintained and supported, so it remains our recommended approach.