Hallo,
Do anyone know if the Oxide RCON should replicate how Rust's built in WebSocket RCON works?
I'm building my RCON-tool from the ground up as we speak but it seams I get new console entries via the WebSocket but can't send any commands back over the WebSocket connection.
Oxide RCON VS Rust built in WebSocket RCON?
Discussion in 'Rust Development' started by Henrikmeister, Oct 7, 2017.
-
Wulf Community Admin
The Oxide RCON would be like the old Rust RCON, except with WebSockets. The new Rust RCON uses a different protocol. You can use any older (pre-Rust websockets) Rust RCON tool with the Oxide RCON enabled.
-
[DOUBLEPOST=1507339230][/DOUBLEPOST]I see the commands sent from the RCON tool to the server are executed but don't reply back - ref. issue on GitHub RemoteConsole Oxide RCON not executing commands · Issue #1155 · OxideMod/Oxide · GitHubLast edited by a moderator: Oct 7, 2017 -
Wulf Community Admin
It actually replies back just fine, you just need to print and not use arg.replyWith in our commands. -
Okey.. so I found the file which handels the incoming messages, but some useful commands you can use to retrieve information is missing - such as `global.serverinfo`, `chat.tail` and `console.tail` (Oxide/RemoteConsole.cs at develop · OxideMod/Oxide · GitHub)
Is this something that will be added down the road? -
Wulf Community Admin