Difference between revisions of "ALiVE Data"
From ALiVE Wiki
| (13 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | |||
[[File:wart.png|thumb|right|400px|AliVE War Room]] | [[File:wart.png|thumb|right|400px|AliVE War Room]] | ||
| − | ALiVE | + | 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 After Action Reviews. 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 works on both Windows and Linux servers. There are optional pbo's included for server admins to autostart data in all missions, even if the data module is not placed. | ||
| − | |||
| + | *'''[[Persistence|Mission Persistence]]''' requires the ALiVE Data module to be placed and can store persistence data either locally or in the cloud. To use cloud persistence you require a free [[War Room]] account. | ||
| − | |||
| − | + | *'''[[Database|ALiVE Stats]]''' requires the ALiVE data module to be placed and records player stats and after action reviews to the ALiVE [[War Room]]. This requires a free [[War Room]] account. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | *'''[[ | + | |
==Dedicated Servers== | ==Dedicated Servers== | ||
| − | ALiVE was built to run on a dedicated server | + | ALiVE was built to run on a dedicated server but 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== | ==Local Databases== | ||
| − | + | ALiVE provides the option to store mission data locally using in-built Arma 3 functionality - without the need for a local database. Support for local instances of CloudDB is now deprecated. | |
| − | + | ||
| − | + | ||
[[Category:War Room]] | [[Category:War Room]] | ||
Latest revision as of 06:20, 16 June 2017
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 After Action Reviews. 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 works on both Windows and Linux servers. There are optional pbo's included for server admins to autostart data in all missions, even if the data module is not placed.
- Mission Persistence requires the ALiVE Data module to be placed and can store persistence data either locally or in the cloud. To use cloud persistence you require a free War Room account.
- ALiVE Stats requires the ALiVE data module to be placed and records player stats and after action reviews to the ALiVE War Room. This requires a free War Room account.
Dedicated Servers
ALiVE was built to run on a dedicated server but 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
ALiVE provides the option to store mission data locally using in-built Arma 3 functionality - without the need for a local database. Support for local instances of CloudDB is now deprecated.
