Today’s improvements focus on speeding up how game server logs are delivered to the central log-parsing server and introducing two new API endpoints for scoreboard data.

⚡ Faster Log Delivery System

Previously, the log delivery process relied on a CRONJOB running once per minute. The CRONJOB checked if the logfile wasn’t empty, sent it to the central log-parsing server, and then cleared the logfile on the gameserver.

The downside was clear:

• A fixed 60-second delay in data parsing, which didn’t feel real-time enough.

This has now been improved with a dedicated system-service that starts on server boot. It runs on a timer and can trigger the log-delivery script more frequently than once per minute, resulting in faster and more responsive data parsing.

📊 New Scoreboard API Endpoints

Thanks to the new built-in dataparsing, two fresh API endpoints are now available:

• Current scoreboard endpoint – Fetches the scoreboard of the current ongoing round from a specific server.
• Previous scoreboard endpoint – Retrieves the scoreboard of the last round played before the current one.

These endpoints make it easier for developers, tools, and the community to access accurate round-by-round server data instantly.

With faster log handling and round-based scoreboards now exposed through the API, the backend is becoming more reliable and flexible than ever.