The RUST combat log command
The RUST combat log command is used to display a historical log of combat engagement information. The information in the combat log is saved on the server-side and when requested, is served from the respective server a player is actively connected to.
Each RUST server defaults to storing a record of the last 100 events where a player was engaged in combat. Server administrators can control this log size by setting the combatlogsize variable. This log will continue to record data regardless of the player being online or having been asleep on the server.
The combat log itself has 12 columns of information that are displayed in the console once the command has been entered successfully. If there is no prior combat recorded, the columns will display but no information will be listed under them.
| Column Title | Description |
| Time | The recorded server time in which the combat round was initiated. |
| Attacker | The player that initiated the combat round. |
| Attacker ID | The player’s unique server/network ID. |
| Target | The player or object (i.e. wooden door) that was harmed by the Attacker. |
| Target ID | The player or object’s unique ID. |
| Weapon | The weapon type used in the combat round. |
| Ammo | The ammo type used in the combat round. |
| Area | The specific area in which the hit registered. (.i.e. head, neck, arm, generic) |
| Distance | The distance in which the attack was initiated in meters. |
| Old Hp | The total health of the target before the combat round took place. |
| New Hp | The total health of the target after the combat round took place. |
| Info | Additional information, statuses and flags. |
A few practical reasons for using the RUST combat log command:
- Identifying players that engaged in combat
- Testing the effectiveness of a matrix of areas:
- Different weapon’s range
- Different ammo types
- Different armor types
- Different building materials
- Different weapon modifications
- Providing information for reporting potential hackers (i.e. across the world shots)
- Investigating potential hackers as an admin
- Identifying what weapons enemies have used
- Monitoring and reporting player combat statistics over time
Who can enter the RUST combat log command
- The RUST combat log command can be issued by all actively connected players, on all vanilla RUST servers.
- When using the RUST combat log command to view another player’s log, it can be used by RUST admins and moderators only on vanilla RUST servers.
- When using the RUST combat log size variable can be issued by RUST admins and moderators on vanilla RUST servers.
How to use the RUST combat log command
Before initiating the RUST combat log command:
- Ensure that an active connection is established with the server that the combat log is being requested for. There is no label as to what server the log is for, so pay special attention.
- The combat log will not report any information if there is not an active connection.
- If the combat log is requested while an active connection is established, it will remain in the console until the console has been cleared or the game has been closed.
The RUST combat log command can be issued from the in-game console only. Press the F1 key to open the in-game console and type in the specific combat log syntax listed below, then press enter.
The RUST combat log size variable can be issued from both the in-game console and RCON platforms.
RUST combat log command (1 of 4)
- This command is used to print the combat log to the console, of the player who is initiating it.
- The command works only when actively connected to a server.
- This will report as many lines as the respective server’s configurations save and are available.
- Note that this command does NOT work from RCON platforms.
combatlog
On success the console will display:
| time | attacker | id | target | id | weapon | ammo | area | distance | old_hp | new_hp | info |
| 2602.1s | you | 0000000 | chicken | 0 | bow_hunting.entity | N/A | generic | 1.5m | 10.0 | 100.0 | killed |
On success the server chat will display:
N/A
RUST combat log for another player command (2 of 4)
- This command is used to print the combat log of another player to the console.
- It works only when the player initiating the command is actively connected to a server. The person whose combat log is being requested does not have to be online.
- This will report as many lines as the respective server has configured to save. Also, it can only display as many lines as are available.
- Value parameters that may be passed in as parameters are as follows
- Player’s full name
- Player’s partial name
- Player’s SteamID
- Player’s IP address
- Note that this RUST admin command does NOT work from RCON platforms.
combatlog insert_value_parameter_here
On success the console will display:
| time | attacker | id | target | id | weapon | ammo | area | distance | old_hp | new_hp | info |
| 2602.1s | you | 0000000 | chicken | 0 | bow_hunting.entity | N/A | generic | 1.5m | 10.0 | 100.0 | killed |
On success the server chat will display:
N/A
On failure the console will display:
Invalid player
RUST server.combatlogsize variable (3 of 4)
- This variable is used to set the number of entries saved in the server’s combat logs.
- This variable defaults to 30.
- Note that this command does work from RCON platforms and doesn’t require being logged into the game server.
Get the server’s current configuration value
Use the command below to report the current configuration
server.combatlogsize
On success the console will display:
server.combatlogsize: "30"
On success the server chat will display:
N/A
Configure the server.combatlogsize value
Use the command below to configure the combat log size
server.combatlogsize “35”
On success the console will display:
server.combatlogsize: "35"
On success the server chat will display:
N/A
RUST server.combatlogdelay variable (4 of 4)
- This variable is used to set the delay in which the combat log’s data will be available to players after events have occurred.
- This variable now defaults to 10 seconds.
- Note that this command does work from RCON platforms and doesn’t require being logged into the game server.
Get the current value
Use the command below to report the current value
server.combatlogdelay
On success the console will display:
server.combatlogsize: "current_value_here"
On success the server chat will display:
N/A
Configure the value
Use the command below to configure the combat log delay in (seconds):
server.combatlogdelay “10”
On success the console will display:
server.combatlogdelay: "10"
On success the server chat will display:
N/A
