exportJIPMessages: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "\[\[Category:[ _]?Scripting[ _]Commands[ _]Arma[ _]3(\|.*)]]" to "{{GameCategory|arma3|Scripting Commands}}") |
Lou Montana (talk | contribs) m (Text replacement - "\{\{GameCategory\|(arma[0123])\|New[ _]Scripting[ _]Commands[ _]List\}\}" to "{{GameCategory|$1|New Scripting Commands}}") |
||
| Line 28: | Line 28: | ||
<h3 style="display:none">Bottom Section</h3> | <h3 style="display:none">Bottom Section</h3> | ||
{{GameCategory|arma3| | {{GameCategory|arma3|New Scripting Commands}} | ||
{{GameCategory|arma3|Scripting Commands}} | {{GameCategory|arma3|Scripting Commands}} | ||
Revision as of 23:04, 12 January 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:
- DiagnosisMultiplayer
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
Bottom Section
Notes
Bottom Section
- 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.