NextClient
Connect NextClient for in-game server lists, player statistics and release management.
About this module
NextClient connects your monitoring site to the Counter-Strike 1.6 game client. The module builds lists for the server browser, game menu and favorites, and collects player activity and connection data.
The admin panel provides statistics, list-source settings, and client branch and release management. Each channel can include all servers, paid placements only, or paid servers followed by free servers that are online.
Latest changes
Full history →Stable release of the NextClient 1.1 integration.
Changed
- Includes server lists, player statistics, build management, and delivery of updates through CDNs.
Game Coordinator requests now run in a dedicated Go service designed for high volumes of concurrent NextClient traffic.
Changed
- Moved /nextclient/gc request handling to Go while preserving the endpoint and client protocol.
- The existing Monitoring agent starts the service automatically, checks readiness, and brings it back up if it stops.
- Telemetry enters a bounded Redis buffer. With TimescaleDB, the Go service writes events in background batches.
Added
- Added 180/365-day and All-time periods.
- Added NextClient Cloud integration.
- Added JSON output for server lists.
Changed
- Sessions are retained indefinitely; raw events for 24 hours.
- Dates use the viewer’s timezone.
Fixed
- Fixed unique and returning player counts.
Frequently asked questions
What is the NextClient integration for?
It connects the NextClient client to your Counter-Strike 1.6 monitoring site, providing server lists, activity statistics and client-version delivery management.
Can I configure different server lists?
Yes. The server browser, game menu and favorites have separate settings. Each channel supports all servers, paid servers only, or paid servers followed by free servers that are online.
Which statistics are available?
Player activity, sessions, connections, server visits and favorites. Public statistics can be enabled separately from the administrative view.
How do I manage client versions?
Create branches, upload release archives and select the active version in the admin panel. After the first published release, subsequent versions must be selected explicitly, so uploading alone does not switch the active release.