Revision as of 07:51, 28 July 2015

Note: The server plugin changes regularly. You will need to unpack and run both @ALiVE and @ALiVEServer on your dedicated server after each release

ALiVE War Room

ALiVE War Room is a central service provided completely free by the ALiVE team for the ArmA community. It includes mission statistics, map based After Action Reviews, server performance monitoring and multi session mission persistence.

• 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

• ALiVE Data Module 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 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.

Local Dedicated Servers

The War Room is designed with dedicated servers in mind. However, you can set up a local dedicated server using arma3server.exe in your ArmA3 root folder. The BI Community Wiki has full details and there are great tools made by the community such as ArmA3Sync and TADST to make it easier. You need to run the exact same mod line as your client but include @aliveserver. Then you can join it from your server browser in game. Add the details to your War Room setup page, following the instructions carefully. Be sure to check the IP address every time you start the server, in case it has changed.

Single Player Save Game

While it is technically possibly to use the regular BIS save game feature, due to the huge amount of data in a typical ALiVE scenario the client will likely crash to desktop with an out of memory error. It is highly recommended you use the War Room for mission persistence. If you want to try regular single player save games, you can re-enable the option in the ALiVE (Required) module

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:

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.

Local Databases=

We currently have no plans to support local databases. 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. Re-coding ALiVE to allow for local databases (and providing the support for people running them), is not on our roadmap currently.