exportJIPMessages: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) |
Lou Montana (talk | contribs) m (Text replacement - "\|seealso= *\[\[([^ ]+)\]\], \[\[([^ ]+)\]\]" to "|seealso= $1 ") |
||
| Line 14: | Line 14: | ||
|x1= <code>'''exportJIPMessages''' "myFileNameWithoutExtension";</code> | |x1= <code>'''exportJIPMessages''' "myFileNameWithoutExtension";</code> | ||
|seealso= [[didJIP]] [[didJIPOwner]] [[logEntities]] | |seealso= [[didJIP]] [[didJIPOwner]] [[logEntities]] [[diag_captureFrame]] | ||
}} | }} | ||
Revision as of 15:52, 20 January 2022
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
- See also:
- didJIP didJIPOwner logEntities diag_captureFrame
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.