How to Tune Your Hytale Server: Quiche Transport, View Distance and Worldgen Threads — the New Update 6 Console Commands

Most patch-note coverage of Update 6 Part 5 stopped at the headline items — the OpenGL requirement, the mage towers, the Point Tool. But buried in the server section of the official Part 5 patch notes is something that matters far more if you actually run a box: a proper set of runtime tuning controls. For the first time, self-hosters can dial view distance, worldgen threads, network transport and camera behavior from the console instead of guessing. This is a hands-on hytale server tuning guide — what each new control does, when to reach for it, and where to start based on your hardware and player count. One caveat up front, and it is important: everything here lives on the pre-release branch (Launcher → Settings → Pre-Release), not stable. There is no announced Update 6 stable date, so treat these controls as the live edge to test against rather than production-locked. The cadence is weekly pre-release Thursdays, and features can still shift. Spin up a test server, try each lever, and keep notes — that is the only honest way to tune, because the right number depends on your machine and your players, not on a blog telling you a magic value. maxviewradius — The Single Biggest Lever You Have If you only learn one new command, make it this one. maxviewradius sets the server's global maximum view radius, and it is the most direct control you have over the tradeoff between visual reach and load. Run maxviewradius with no argument and it reports the current cap. Run maxviewradius <n> to set it, where n is between 1 and 512 chunks. Run maxviewradius reset to return it to the default of 32 chunks. The logic is simple: lower view distance means less CPU and bandwidth spent per player, which in practice means you can host more players, or the same players with less hytale server lag. A higher radius shows off more visible terrain — great for a screenshot-friendly build server or a small survival group — but every extra chunk multiplies the work your box does for each connected player. This is the core knob behind almost all hytale server performance tuning, so treat 32 as a starting point, not a law. Choosing a maxviewradius by Player Count There are no official recommended numbers, so treat what follows as general server-admin guidance, not benchmarks. For a busy public server chasing high concurrency, you will usually want to sit below the default — try dropping maxviewradius to something like 12 to 20 and watch your frame time and bandwidth as the player count climbs. For a small friends-and-family survival world on decent hardware, the default of 32 is comfortable, and you can push higher if the vista matters more than headcount. For a curated build or showcase server with only a handful of connections, a large radius pays off visually at a cost you can afford. The method matters more than any single number: change maxviewradius, load the server up under realistic conditions, and measure. If tick times climb or players report rubber-banding, come down. If everything is smooth and you have headroom, you can afford more hytale view distance. Because it takes effect from the console at runtime, you can tune it live without a restart. /worldgen2 concurrency — Matching Worldgen to Your CPU The second big lever is /worldgen2 concurrency <level>, which overrides the world-gen V2 worker thread count at runtime. World generation is one of the spikiest workloads a Hytale server does — every time a player crosses into fresh terrain, the generator has to build it, and on a busy server those requests stack up. Being able to set the worker count lets you match that work to the machine you are actually running on. As a rule of thumb from general server administration, you want worldgen concurrency to fit within your available CPU cores rather than fight the rest of the server for them. On a dedicated box with plenty of cores, a higher level can smooth out terrain generation for players exploring new areas. On a shared or core-limited host, cranking it too high just causes contention — the generator and the main server loop end up competing, and everything feels worse. Start conservative, raise it while watching for smoother chunk loading without a hit to tick stability, and back off if you see the opposite. Modders working close to the generator should keep the modding API and server plugin development guide handy, since worldgen behavior and plugin code often interact. Host With Quiche Transport — Experimental, Opt-In, Keep a Fallback New in Part 5 is a Settings toggle labelled "Host With Quiche Transport (Experimental)". When it is on, any world you host runs on an experimental QUIC-based network transport, which brings faster connect times for players joining your server. This is where Hytale's netcode appears to be heading, and it is genuinely worth testing. But read the label literally: it is experimental and opt-in. That means you should not flip it on for your only production instance and hope. The right move with hytale quiche transport is to test it on a staging server, or to keep a fallback ready so you can switch back the moment you see connection problems, dropped players, or anything odd. If you like living on the edge and want the faster joins, enable it deliberately, tell your community it is experimental, and monitor closely. If you need rock-solid stability right now, leave it off until it matures. FovOverride — Locking Field of View for Custom Cameras The server-side FovOverride field forces a player's field of view, from 1 to 180 degrees, while a custom server camera is active. This is a niche but genuinely useful control for anyone building cinematic sequences, spectator modes, minigame cameras, or any experience where you take the camera away from the player. The point of FovOverride is consistency: without it, every player sees your custom camera through their own personal FOV setting, which quietly breaks framing for cinematics and can hand a competitive edge to whoever cranked their FOV widest. By forcing a value while your camera is active, you guarantee everyone sees the shot the way you designed it. Reach for it whenever a set piece depends on precise framing, and leave it alone during normal play so players keep their preferred view. Console Tab-Completion and a Real /help Part 5 also gave the server console a productivity pass that makes every command above easier to live with. The console now supports tab-completion for commands, subcommands, arguments and flags — so you can start typing maxviewradius or /worldgen2 and let the console finish it, and discover valid arguments without memorizing them. Alongside that, /help now prints a formatted command list with per-command usage, which is the fastest way to learn the full set of hytale server console commands available in your build. There is a small quality-of-life win for non-English operators too: /update status and /update check now output in the server's configured language instead of always defaulting to English. If you run a server in a non-English community, that is one less thing to translate for your team. Set a Custom Server Discovery Image Not strictly a performance control, but a tuning task worth doing the same week: Server Discovery now supports custom server images. If you do not set one (or it is not yet approved), a default image is shown instead. That means your server can display its own art on the in-game browser rather than a generic placeholder — free branding on the exact screen where players decide where to play. Upload your art, get it approved, and you have claimed that space. It pairs naturally with keeping your public listing sharp, which we come back to below. Your Update 6 Server Tuning Checklist Here is the practical order of operations for turning these hytale dedicated server settings into a well-tuned box. Do it on a pre-release test server first. 1. Learn the console. Get onto the pre-release branch, run /help, and lean on tab-completion. Confirm the new commands are present in your build before you rely on them. 2. Set your baseline view distance. Check the current value with maxviewradius, then set a target with maxviewradius <n> based on your goal — lower for high player counts, higher for small showcase servers. Keep maxviewradius reset in your back pocket to return to 32. 3. Match worldgen threads to your CPU. Use /worldgen2 concurrency <level> to fit worldgen work inside your available cores. Start conservative and raise it while watching tick stability. 4. Load-test and measure. Put realistic player load on the server, watch tick times and bandwidth, and adjust maxviewradius and worldgen concurrency together. The right numbers are the ones that stay smooth under your load. 5. Decide on Quiche transport deliberately. If you want faster connect times and can tolerate experimental behavior, enable Host With Quiche Transport on a test instance with a fallback ready. Otherwise leave it off for now. 6. Configure FovOverride only where needed. Set it for custom-camera set pieces and cinematics; leave normal play untouched. 7. Brand your Discovery image and your listing. Upload a custom Server Discovery image, then make sure your HytaleCharts server listing is just as sharp — banner current, heartbeat reporting live player counts, votifier wired up, and a clear description. Pre-release weeks are exactly when curious players go hunting for well-run servers to try the new build on, so a tuned server plus a strong listing is how they find and choose you. If you are still weighing where to run your box in the first place, the self-hosted vs managed hosting guide is the right companion read. Update 6 Part 5 turned Hytale server operation from a black box into something you can actually tune: maxviewradius for the view-distance-versus-load tradeoff, /worldgen2 concurrency to fit generation to your CPU, experimental Quiche transport for faster joins, FovOverride for camera control, and a console that finally helps you find its own commands. None of these have official magic numbers, so test on pre-release, measure under real load, and tune to your hardware and your players. Get it right and your server will feel faster and hold more people — and a fast, full server is exactly the kind that climbs the rankings on hytale charts.