Websites and applications
SCUM.SK: a web application for a gaming community
A connected platform for players, live server data, events and secure game automation.
- Project: SCUM.SK
- Scope: Product planning, UX and development
- Platform: NODERA, NODERAgent
- Focus: Web application, data and automation
A website players keep using after joining the game
Many gaming websites stop at an IP address, server rules and a Discord link. SCUM.SK needed more. Before joining, players need to check the server. During play, they want to follow their progress. When something goes wrong, they need help. Administrators need to work with the same data, without manually copying it between the game, website and Discord.
The product principle: Technology should stay in the background. Players should not have to work out where a status update came from or who controls RCON. They need current information, a clear answer and features they can rely on.
The game, website, Discord and admin tools each worked differently
Each environment has its own pace, rules and capabilities. Without a shared way to communicate, the result is outdated information, manual intervention and an administrator who has to launch the game to resolve every issue.
Numbers without context
An online count or kill log is just raw data. Players need to know which server is active, what happened and whether it is worth joining.
Administrators tied to the game
Restarts, teleports, packs and events cannot depend on someone logging in as a player and doing everything manually.
Discord as an archive
Channel messages quickly disappear from view. Rules, results and support need a permanent home and a searchable history.
A public website and a sensitive server
The website needs access to server status, not unrestricted access to RCON, logs and local files.
One data flow, clear responsibilities
A player enters a command where they already are: in the game. NODERAgent Communicator captures it, NODERAdmin decides what may run, and the result returns to the game. Each step has a responsible component and an audit trail.
- Game — input: The player enters a supported command in game chat, without opening a website or waiting for an administrator.
- NODERAgent — communication: Communicator recognises the command and forwards it with the player and server identity.
- NODERAdmin — control: The admin system checks the rules, permissions and feature state before preparing a specific server task.
- Game — feedback: The player receives a targeted reply or result in the game. An uncertain operation is never reported as successful.
Game commands, packs, event actions and other automations follow the same path.
Features that do more than appear in an admin menu
Each feature addresses a real situation: choosing a server, competing, progressing, getting support or running the service. The value lies in what players can use, rather than the number of background processes.
Live status and server statistics
Before connecting, players can see availability, online player counts, activity over the last 24 hours, the next restart and historical data. The kill feed and leaderboard add weapons, distances, K/D and the longest confirmed kills.
SCUM Battle Royale
A dedicated server runs repeated rounds with a lobby, random deployment, custom loot and vehicles. SCUM controls the zone and Sudden Death, while the system records results and returns players to the next cycle.
A custom BTC economy
An internal currency rewards verified time online. Players have a personal wallet and a ledger of every movement. BTC can be transferred between players and provides the basis for packs, event wagers and other server services.
Support and NODERAntiraid
Web tickets give bugs, reports and appeals their own history. NODERAntiraid alerts players to supported lockpicking or property damage events; it does not stop an attack or roll changes back.
The main PvPvE world
High Loot zones, custom trader rules, the Black Market and defined raid times give the economy a rhythm. Players know when their base is at risk and why a particular part of the map is worth exploring.
Events that run in the game
Battle Royale, Duel Arena, Squad Wars and Warzones are not manually staged scenarios. Each has its own rules, from a lobby and tournament round to a 1v1 or squad battle, or a rotating PvP zone with transport and loot.
Sensitive commands stay beside the server
The public website has no reason to know the RCON password or access local files. NODERAgent runs alongside the SCUM server, accepts only permitted tasks and returns a confirmed, rejected or uncertain result for each one.
This allows us to read status, process a game command, monitor a log, deliver a pack or carry out an event action. Discord receives the result when appropriate, but it is not the source of truth.
- No direct RCON access from the public website
- Separate permissions and limits for each feature
- Results, history and audit records instead of blind retries
Battle Royale with its own round cycle
This is a dedicated SCUM Battle Royale server, rather than an occasional community event. The system prepares a round, deploys players, hands combat over to the native Tournament Mode and cleans up the world afterwards for the next start.
- Preparation: Vehicles, loot spawners, weather and notifications are prepared before the round. A new round cannot start while the previous one is still running.
- Deployment: Available players are placed into the game. The roster closes around those successfully deployed, with no late entries added.
- Combat: SCUM controls the shrinking zone, respawns and Sudden Death. If several players survive, the round continues without respawns until a winner is determined.
- Result: The winner is recorded once, the leaderboard updates and players return to the lobby. A controlled restart may follow a configured number of rounds.
What we do not promise: Winning means a confirmed result and a place on the leaderboard. Automatic BTC, FAME or item rewards are only advertised when they have been configured and verified for the specific round.
Players, the community and administrators need different views
They still need to work from the same state and know where to go next. Every part of SCUM.SK has a distinct role, connected to the rest.
For players
Servers, rules, profiles, the kill feed, rankings, economy and tickets, without searching old Discord messages for links.
For the community
Events, results, changes and important announcements remain on the website. Discord distributes them, but is not their only archive.
For the admin team
Commands, logs, settings and automation come together in NODERA, with status, permissions and traceable results.
Less manual administration. More reasons to return.
SCUM.SK is now more than a place to find an IP address. Players choose a server based on live data, follow their progress, join events and open tickets when they need help. Administrators do not have to be logged into the game at every step, while sensitive operations remain beside the server.
Players know where they stand
They see server status before joining and find results, progress and support in the same place after playing.
The community keeps its history
The kill feed, leaderboard, events, rules and changelog do not disappear beneath newer Discord messages.
The project can keep growing
A new mode can reuse identities, commands, results and publishing. It builds on shared infrastructure while retaining its own gameplay rules.
See SCUM.SK in action
Explore live server status, the kill feed or the leaderboard. The core of this case study is running on a project that continues to evolve.