exportJIPMessages: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
(updated description and added log example)
m (Fix file name format)
Line 10: Line 10:
The file is created in the same directory as [[Crash_Files|.rpt file]].
The file is created in the same directory as [[Crash_Files|.rpt file]].
{{Feature|informative|[[BattlEye]]'s RCON variant of this command is {{hl|#exportJIPqueue}} (see also [[Multiplayer Server Commands]]).}}
{{Feature|informative|[[BattlEye]]'s RCON variant of this command is {{hl|#exportJIPqueue}} (see also [[Multiplayer Server Commands]]).}}
File name example: {{hl|jipqueue_12024_25-10-2024_11-31-11.log}}<br>
File name examples:
* {{hl|jipqueue_12024_2024-10-25_11-31-11.log}} (using {{hl|#exportJIPqueue}})
* {{hl|jipqueue-12024-2024-10-25_11-31-11.fileNameParameter.log}} (using [[exportJIPMessages]])
File content example: <spoiler text="Show example">
File content example: <spoiler text="Show example">
<pre>
<pre>

Revision as of 15:53, 6 November 2024

Arma 3 logo black.png1.56
Hover & click on the images for description

Description

Description:
Creates a log file containing an overview on all JIP (network) messages currently in the JIP queue. The file is created in the same directory as .rpt file.
ⓘ
BattlEye's RCON variant of this command is #exportJIPqueue (see also Multiplayer Server Commands).

File name examples:

  • jipqueue_12024_2024-10-25_11-31-11.log (using #exportJIPqueue)
  • jipqueue-12024-2024-10-25_11-31-11.fileNameParameter.log (using exportJIPMessages)
File content example: 
time = 78814.063

==================================================================================================
Objects: 
---------------------------------------------------------------------------------------------
	Type_96 creator:2 networkId:ID - owner __SERVER__ (2)
---------------------------------------------------------------------------------------------
	Type_107 creator:2 networkId:ID - owner __SERVER__ (2)
---------------------------------------------------------------------------------------------
	Type_109 creator:2 networkId:ID - owner __SERVER__ (2)
---------------------------------------------------------------------------------------------
	Type_113 creator:2 networkId:ID - owner __SERVER__ (2)
---------------------------------------------------------------------------------------------
	Type_118 creator:2 networkId:ID - owner __SERVER__ (2)
---------------------------------------------------------------------------------------------
	Type_99 creator:2 networkId:ID - owner __SERVER__ (2)
---------------------------------------------------------------------------------------------
	Unknown creator:2 networkId:ID - owner __SERVER__ (2)
---------------------------------------------------------------------------------------------
	Type_332 creator:2 networkId:ID - owner __SERVER__ (2)
---------------------------------------------------------------------------------------------
	Type_334 creator:2 networkId:ID - owner __SERVER__ (2)
---------------------------------------------------------------------------------------------
	Type_198 creator:2 networkId:ID - owner __SERVER__ (2)
---------------------------------------------------------------------------------------------
	Unknown creator:4 networkId:0 - owner NAME (1c7f3773)
---------------------------------------------------------------------------------------------
	Type_332 creator:4 networkId:1 - owner NAME (1c7f3773)
---------------------------------------------------------------------------------------------
	Type_334 creator:4 networkId:2 - owner NAME (1c7f3773)
---------------------------------------------------------------------------------------------
	Type_96 creator:2 networkId:ID - owner NAME (1c7f3773)
---------------------------------------------------------------------------------------------
	Type_109 creator:2 networkId:ID - owner NAME (1c7f3773)
---------------------------------------------------------------------------------------------
	Type_113 creator:2 networkId:ID - owner NAME (1c7f3773)
---------------------------------------------------------------------------------------------
	Type_118 creator:2 networkId:ID - owner NAME (1c7f3773)
---------------------------------------------------------------------------------------------
	Type_195 creator:2 networkId:ID - owner __SERVER__ (2)
---------------------------------------------------------------------------------------------
	Type_99 creator:4 networkId:3 - owner NAME (1c7f3773)
---------------------------------------------------------------------------------------------
	Type_99 creator:4 networkId:4 - owner NAME (1c7f3773)
---------------------------------------------------------------------------------------------
	Type_99 creator:4 networkId:5 - owner NAME (1c7f3773)
---------------------------------------------------------------------------------------------
	Type_99 creator:4 networkId:6 - owner NAME (1c7f3773)
---------------------------------------------------------------------------------------------
	Type_99 creator:4 networkId:7 - owner NAME (1c7f3773)
---------------------------------------------------------------------------------------------
	Type_99 creator:4 networkId:8 - owner NAME (1c7f3773)
---------------------------------------------------------------------------------------------
	Type_96 creator:4 networkId:12 - owner NAME (1c7f3773)
---------------------------------------------------------------------------------------------
	Type_96 creator:4 networkId:13 - owner NAME (1c7f3773)
---------------------------------------------------------------------------------------------
	Type_96 creator:4 networkId:15 - owner NAME (1c7f3773)
---------------------------------------------------------------------------------------------
	Type_96 creator:4 networkId:49 - owner NAME (1c7f3773)

==================================================================================================
_initMessages - Total: 7601
	            Type_330 :     4
	             Type_60 :     6
	            Type_272 :    31
	            Type_273 :    31
	            Type_274 :  4481
	             Type_64 :   435
	            Type_291 :   147
	            Type_292 :     1
	            Type_187 :    50
	            Type_248 :  1846
	             Type_53 :    70
	             Type_54 :   341
	            Type_294 :     3
	             Type_10 :    69
	            Type_385 :     1
	            Type_295 :     1
	            Type_296 :    16
	            Type_328 :     4
	            Type_329 :     4
	             Type_59 :    60

==================================================================================================
_initMessagesRE - Total: 0

==================================================================================================
_jipMarkerInfos - Total: 0
↑ Back to spoiler's top
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
Demellion - c
Posted on Oct 16, 2019 - 19:31 (UTC)
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.
Retrieved from "https://community.bistudio.com/wiki?title=exportJIPMessages&oldid=370201"