kerboul/perun
1
0
Fork 0
mirror of https://github.com/DaKerboul/perun.git synced 2026-08-09 14:45:39 +02:00
Code Issues Packages Projects Releases Wiki Activity

Changed frames ids , updated readme

Browse Source
This commit is contained in:
VladMordock
2021-02-18 18:39:55 +01:00
parent 9d63cb5905
commit ac029e1d30
2 changed files with 32 additions and 43 deletions
Download Patch File Download Diff File Expand all files Collapse all files

38
README.md
View File

@@ -95,28 +95,26 @@ DCS API does not track carrier or FARP operations natively, so there is a trick
![Database Scheme](https://i.imgur.com/zJsFxV0.png "MIT")
## Data packets - send from lua to TCP port
* ```ID: 1```, contains version/diagnostic information
* perun version - for server administration usage
* player count - actual number of connected players
* ```ID: 2```, contains status data in the following sections
* mission name - name of the mission file
* model time - simulation time
* real time - real time
* pause - information if server is paused
* multiplayer - information if this is multiplayer game (always true for dedicated server usage)
* theather - information about area of operation
* weather - basic weather information
* players - connected players
* ```ID: 3```, available slots list and coalitions
* ```ID: 1```, stats update [periodic update]
* server - various information for server administration usage
* mission - short information about runing mission
* mission name - name of the mission file
* model time - simulation time
* real time - real time
* pause - information if server is paused
* multiplayer - information if this is multiplayer game (always true for dedicated server usage)
* theather - information about area of operation
* clients - list of connected players
* ```ID: 2```, available slots list and coalitions [updated on mision start or Perun reconnection]
* coalitions - available coalitions
* slots - available slots
* ```ID: 4```, stores mission data ; idea is to have whole DCS.getCurrentMission() result - currenlty commented out due to performance issues
* ```ID: 50```, chat event
* ```ID: 51```, game event
* ```ID: 52```, player stats ; note that as DSC native stats are not reliable, seperate stats couting methods are used
* ```ID: 53```, player login to DCS server
* ```ID: 100```, DCS SRS's client-list.json
* ```ID: 101```, LotATC's stats.json
* ```ID: 3```, stores mission data [updated on mision start or Perun reconnection]
* ```ID: 50```, chat event [event triggered]
* ```ID: 51```, game event [event triggered]
* ```ID: 52```, player stats ; note that as DSC native stats are not reliable, seperate stats couting methods are used [event triggered]
* ```ID: 53```, player login to DCS server [event triggered]
* ```ID: 100```, DCS SRS's client-list.json [updated every 60s, only between Perun and database]
* ```ID: 101```, LotATC's stats.json [updated every 60s,only between Perun and database]
# Project information
## Built With