Chunk Survival · Stoxello

Chunk Survival – Documentation | Stoxello

Stoxello | Chunk Survival

Chunk Survival is a block-building survival game for Windows. Players explore chunk-based worlds, gather resources, build, fight mobs and wildlife, and join multiplayer servers running hub worlds, persistent survival maps with land claims, and fast round-based minigames such as BedWars and SkyWars.

The product ships as ready-to-run software: a Windows game client (ChunkSurvival.exe) kept current by the bundled launcher, a headless dedicated server for self-hosting or hosting providers, a public gateway that safely routes players to server roles, an account website with skins and a cosmetics store, and a collection of official gameplay plugins. Resource packs and sound packs install by dropping them into folders.

Product: Chunk Survival (game client, dedicated server, launcher, account website)
Platforms: Windows (client & server); Linux/Docker (server deployment)
Distribution: Launcher-managed client releases + dedicated-server packages / Docker images from your Stoxello distribution
Type: Desktop game + dedicated-server multiplayer platform

Key Features

Voxel survival gameplay – chunk-based worlds with saves, mobs/wildlife entities, item drops, and a point economy.
Launcher with versioned releases – the launcher downloads the newest client release compatible with your server's protocol line automatically.
Dedicated servers with roles – run a persistent hub, survival worlds (with or without chunk claims), or minigame backends; each backend runs its own role configuration.
Gateway security model – players connect only to a single public gateway port (25599) that routes authenticated sessions to backends; backends are never exposed directly.
Official minigames – BedWars, SkyWars, Spleef, DeathRun, HideAndSeek, SkyBlock, PlotMe, Citizens (NPCs), and more, installed as plugin packages.
Account website – registration/login, skin upload, email verification, admin console, safety-report triage, and a PayPal-powered cosmetics store.
Drop-in customization – resource packs, sound packs, and music load from simple folders; no repacking required.

System Requirements

Requirement	Details
Game client	Windows PC with GPU supporting OpenGL; installed via the Chunk Survival launcher
Dedicated server	Windows or Linux x64 host, or Docker with Compose for container deployments
Account site	Runs alongside the server (port 5000); required for player login
Ports	TCP 25599 (gateway/public game port), TCP 5000 (account site), TCP 5001 (marketing site)
Email / payments	SMTP credentials for verification emails; PayPal credentials to enable the store (optional)

Installation

Playing

Install the Chunk Survival launcher from your Stoxello distribution.
Start the launcher — it downloads the correct client release automatically.
Create your account at the account website, then log in through the launcher and connect to a server (e.g., play.chunksurvival.com:25599).

Self-hosting a server

Extract the dedicated-server package on your host, or use the provided Compose file to deploy the full stack as containers pulled from the registry.
Start the account website (port 5000), then start one or more server backends with their role configurations.
Point the gateway at your backends and open port 25599 to players.
Install plugins into each server's Plugins/ directory and restart the server.

# Container deployment of the full stack
# (.env supplies image owner/tag and secrets)
docker compose pull
docker compose up -d
# Gateway :25599 | Account site :5000 | Marketing site :5001

Usage

Playing – launch through the launcher, log in with your account-site credentials, and pick a role/server. Customization is drop-in: resource packs into ResourcePacks/, sound packs into SoundPacks/, gameplay music into Music/.
Servers – assign each backend a role via its config file (hub resets each restart; survival roles persist their world save in their data volume). After installing or updating plugins, restart the server — runtime reload is intentionally unsupported.
Administration – grant admin rights via the ADMIN_USERS setting (accounts must already exist), then manage accounts and safety reports from the account site's /admin console.

Configuration

server.cfg, servers.cfg, permissions.cfg and per-role files under config/ define roles, ports, world behavior, and permissions (selected via SERVER_CONFIG / GATEWAY_CONFIG).
The .env file beside the Compose file holds deployment settings: registry owner/tag, server identity keys, authorization URL, SMTP settings for verification email, optional AI key for report prioritization, and PayPal credentials for the store (the store disables itself when empty). An example file ships with the distribution.
Client-side preferences and server lists live under the user profile and are managed by the game and launcher automatically.