#Update RCON payload + logs
2 messages Ā· Page 1 of 1 (latest)
The current RCON and server log payloads in Rust Console Edition make it really difficult for developers to build automation or moderation tools because a lot of the events are incomplete or ambiguous. A good example is player join messages the log just prints something like ā[SCARLETT] entered gameā, which looks almost identical to when a player teleports, respawns, or gets moved by an admin. Thereās no unique event type, no user ID, no platform identifier, no coordinates, nothing that cleanly marks it wether its a real server join or a teleport. On top of that, thereās no log or RCON event for when a player disconnects at all, so thereās no reliable way to track who is currently online or how long a player was in the game without falling back on guesswork and bot logic.
Zone events have a similar problem. When a player enters a custom zone, the payload sent over RCON just looks like this: ( image below )
A lot of RCON output follows this same pattern: missing information, critical fields left out, and JSON objects wrapped inside strings instead of being proper structured messages. Adding proper event types like that have more in depth information like PlayerJoin, PlayerLeave, ZoneEnter, ZoneExit, Teleport, etc., and including basic identifiers such as, Gamertag, and platform ( maybe coords and more in depth ) would completely fix these issues.
- some additions to logging in general would be nice this including when people go godmode, vanish, spawn custom items or run custom commands, for in more in depth admin logging for more strict community servers ect.
ā¤ļø