exportJIPMessages: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "\| *(arg|eff|mp|serverExec|gr[0-9]) *= *(.*) * *\|([^=0-9]{12})" to "|$1=$2 |descr=$3") |
Lou Montana (talk | contribs) m (Text replacement - "\| *arma3 * * *\| *([0-2]\.[0-9]{2}) * " to "|game1= arma3 |version1= $1 ") |
||
Line 1: | Line 1: | ||
{{RV|type=command | {{RV|type=command | ||
|arma3 | |game1= arma3 | ||
|1.56 | |version1= 1.56 | ||
|gr1= Diagnostic | |gr1= Diagnostic |
Revision as of 23:16, 13 June 2021
Description
- Description:
- Export list of JIP to a file.
Special: BattlEye's RCON variant of this command is #exportJIPqueue (see also Multiplayer_Server_Commands) - Groups:
- DiagnosticMultiplayer
Syntax
- Syntax:
- exportJIPMessages fileName
- Parameters:
- fileName: String - File where to store the list
- Return Value:
- Nothing
Examples
- Example 1:
exportJIPMessages "myFileNameWithoutExtension";
Additional Information
Notes
-
Report bugs on the Feedback Tracker and/or discuss them on the Arma Discord or on the Forums.
Only post proven facts here! Add Note
- Posted on October 16, 2019 - 19:31 (UTC)
- demellion
- WARNING: Exporting JIP might crash a populated server. This doesn't seem to be exactly related to amount of data to export, since results don't vary much against unpopulated server.