Difference between revisions of "ALiVE Data"

From ALiVE Wiki
Jump to: navigation, search
Line 17: Line 17:
 
For example:
 
For example:
  
1.  To keep the same Stats and Mission Persistence, keep both onLoadName and Filename the same.
+
# To keep the same Stats and Mission Persistence, keep both onLoadName and Filename the same.
2.  To reset Persistence but keep Stats (for example, to retain stats across a campaign of several ops), change the Filename only.
+
# To reset Persistence but keep Stats (for example, to retain stats across a campaign of several ops), change the Filename only.
3.  To reset Stats but keep Mission Persistence (for example, to record separate stats for each session), change the onLoadName only.
+
# To reset Stats but keep Mission Persistence (for example, to record separate stats for each session), change the onLoadName only.
4.  To reset both Stats and Persistence, change onLoadName AND Filename.
+
# 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.
 
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 11:52, 2 May 2014

ALiVE War Room.png
Onebit note.png Note: Server Admins must update the ALiVE Plugins in @ArmA2net. Copy the files from @ALIVE/Addins into your @ArmA2net/addins folder
  • War Room Integrated ALIVEmod.com War Room for registered users. The website records in game statistics in real time and publishes them on the customised Clan or Group pages
  • Database Establishes a link to the central database for recording stats and mission persistence. You need an account on Alivemod.com for this to work.
  • Persistence Mission, Player and Data persistence for multi-session operations between rejoins and server restarts.


Onebit note.png Note: Editor Notes

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:

  1. To keep the same Stats and Mission Persistence, keep both onLoadName and Filename the same.
  2. To reset Persistence but keep Stats (for example, to retain stats across a campaign of several ops), change the Filename only.
  3. To reset Stats but keep Mission Persistence (for example, to record separate stats for each session), change the onLoadName only.
  4. 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.