Connect your Astroneer dedicated server to Takaro using native RCON. No mods required!
kick <name> support. You can now kick players by name instead of GUID.
Released: March 1, 2026 | View All Releases
Astroneer RCON only supports KickPlayerGuid. Typing kick Crash would send an invalid command, causing a 15-second timeout and RCON reconnect. The bridge now intercepts kick <name>, looks up the player's GUID automatically, and sends the correct KickPlayerGuid command.
Example: kick Crash now works correctly.
The v1.19.0 plain-text fix caused JSON responses (ListPlayers, ListGames, ServerStatistics) to be returned as raw compact strings. The bridge now re-parses and pretty-prints any JSON response automatically.
Astroneer does not send a response after SaveGame or NewGame. The bridge was waiting 15 seconds then returning an error. These commands now resolve immediately.
Commands like kick, ban, and unban return plain text from Astroneer. The bridge was trying to JSON-parse those responses, causing errors that triggered RCON reconnects and ghost clients firing duplicate events. Fixed by passing notJson=true to sendRaw for all direct commands.
Every RCON error was creating a new client without disconnecting the old one. Multiple clients polling simultaneously doubled every player event. Fixed by calling removeAllListeners() and disconnect() on the old client before creating a new one.
When a player's game crashed instead of cleanly disconnecting, the bridge was silently blocking their next connect event. This is now fixed â all connect and disconnect events fire correctly regardless of how a player leaves.
Removed the initial player scan on RCON connect that was causing duplicate connected events every time the bridge restarted.
Fixed listEntities error from Takaro. Removed redundant newplayer handler that was duplicating connect events.
Added log rotation (20-day retention), cleaned up server deployment scripts.
Player data validation, error tracking with metrics, max reconnect attempts, improved logging throughout.
Added debug logging and confirmed all features working. Superseded by v1.11.9's reliability improvements.
Bridge now responds immediately to getPlayerLocation requests, allowing events to be created in the database.
The Problem: Events were being sent correctly, but Takaro's request for getPlayerLocation was being queued instead of answered immediately. This caused event processing to hang indefinitely, preventing events from being created in the database.
The Fix:
getPlayerLocation requests{ x: 0, y: 0, z: 0 } to allow event processing to completeResult: Full real-time player event support is now working!
Events now use type: 'gameEvent' as expected by Takaro instead of incorrect type: 'request' format.
The Problem: Events were being sent with the wrong format (type: 'request') instead of the correct type: 'gameEvent' format. This caused Takaro to ignore all events, breaking Discord notifications and event-triggered hooks.
The Fix:
type: 'gameEvent' as expected by TakaroCombined with v1.11.4: Shutdown commands work reliably AND events trigger properly!
Server shutdown commands no longer break the bridge. Shutdown executes asynchronously and RCON auto-reconnects.
The Problem: In v1.11.2-v1.11.3, server shutdown commands would wait for RCON response, but the server would disconnect before responding. This caused errors that broke all subsequent bridge operations including player events.
The Fix:
Recommendation: If you're on v1.11.2 or v1.11.3, update immediately to restore full functionality.
Player connect/disconnect events now work instantly via WebSocket! Critical bugs fixed for real-time event delivery.
The Problem: Events were being sent but silently dropped by Takaro due to two critical bugs:
Bug Fix #1 - Null Values in Optional Fields:
The bridge was sending null for optional fields like epicOnlineServicesId and ip. Takaro's strict validation rejects null values - optional fields must be completely omitted instead.
Bug Fix #2 - getPlayerLocation Hanging:
During event processing, Takaro requests player location. The bridge was queuing this request without responding, causing event processing to hang indefinitely.
The Result:
gameEvent messages (no module needed!)winget install OpenJS.NodeJS.LTS\astroneer\Astro\Saved\Config\WindowsServer\AstroServerSettings.ini in NotepadConsolePort=8778
ConsolePassword=your-password-hereTakaroConfig.txt in Notepad and edit these settings:
IDENTITY_TOKEN=your-server-name
REGISTRATION_TOKEN=get-from-takaro-dashboard
HTTP_PORT=3535
RCON_HOST=127.0.0.1
RCON_PORT=8778
RCON_PASSWORD=same-password-as-step-3start.batUses Astroneer's native RCON protocol - no game modifications needed!
Real-time player join/leave notifications forwarded to Takaro
Execute server commands through Takaro (kick, player list, etc.)
NEW! Direct RCON console for manual server administration and testing
Built-in health endpoint with connection status and metrics
The bridge uses a simple TakaroConfig.txt file for configuration. Get your tokens from the Takaro Dashboard.
The bridge now includes an interactive RCON console for direct server administration!
To use: Double-click rcon-console.bat to open an interactive terminal.
Example commands: (Note: Commands are typed WITHOUT the "DS" prefix - it's added automatically)
RCON> help # Show all available commands
RCON> ListPlayers # List all players
RCON> ServerStatistics # Get detailed server stats
RCON> SaveGame MyBackup # Save the game
RCON> exit # Close consoleThe console connects directly to your Astroneer server via RCON, allowing you to:
Made with â¤ī¸ for the Astroneer community
Š 2025 | GitHub