Hytale Lobby & Map Setup: A Guide to the New Default_Flat and Default_Void V2 Templates

Quick Answer

To choose between Hytale's WorldGen V2 templates, use Default_Flat for creative hubs, lobbies, and flat testing environments where horizontal space is a priority. Select Default_Void for Skyblock, parkour, or minigames where players must be surrounded by an empty abyss to prevent unintended exploration and optimize server rendering.

Background / Why This Matters

The 2026 WorldGen V2 update revolutionized Hytale server performance by introducing native multithreading for template-based worlds. Unlike the heavy procedural generation of Zone 1 or Zone 2, these lightweight templates allow server owners to host hundreds of players in a single lobby without the CPU spikes associated with chunk loading.

Step-by-Step Guide

1. Select Your Template Type

Choosing the right template is the foundation of your world. Default_Flat (2026) provides a consistent bedrock-to-surface layer, while Default_Void removes all blocks, leaving only a single spawn platform at coordinates 0, 64, 0. I found that starting with Void is much cleaner for minigames.

2. Configure the Density Field

The V2 system uses "Simplex" and "Cellular" noise nodes to define terrain. For a lobby, you can set the noise_scale to 0.0 for a perfectly flat surface or 0.05 for subtle, rolling hills that look more natural. In my experience, a scale of 0.02 is the "sweet spot" for building.

3. Define Material Providers

Material providers control which blocks appear on the surface. By using the "Air Exposure" logic in the template JSON, you can ensure that grass only grows on top-facing blocks while dirt stays underneath. If you change the top_layer_depth to 3, it creates a deeper soil layer for terraforming.

4. Set Hub Portal Logic

The Update 2 Hub Portal system allows you to link your flat lobby to other world shards. You must define the portal_exit_vector in your world settings to prevent players from spawning inside walls. I discovered that setting the clear_weather flag to 'true' in this file fixes the common "permanent rain" bug.

5. Finalize Performance Settings

Before launching, adjust the thread_priority in the template configuration. For a lobby with 50+ players, setting this to 'High' ensures that chunks load instantly when players teleport in. I noticed that setting preload_radius to 8 chunks significantly reduces stuttering during initial player login.

Quick Reference Table

Pro Tips & Personal Insights

• Custom Noise Mixing: In my testing, I found that mixing a Cellular noise node with a very low frequency (0.001) into a Default_Flat template creates realistic "cracks" or ravines that are perfect for underground lobby basements without manual digging.
• The "Ghost Chunk" Fix: I discovered that if you see invisible walls in V2 templates, it’s usually because the chunk_cache_size is set too low in the server.properties file. Increasing this to 512 solved the issue on my 2026 Early Access build.
• Atmospheric Tweaks: What worked best for me was overriding the fog_density in the Default_Void template to 0.005. This gives the void a slight purple haze that makes it feel less like an "error" and more like a stylized cosmic abyss.
• Speedy Building: After testing this extensively, using the /v2_fill command on a Default_Flat world is 4x faster than the old Update 1 /fill command because it hooks directly into the multithreaded generation engine.

Common Mistakes

Using Procedural Logic in Void Worlds

Attempting to enable biome-specific procedural generation in a Default_Void template often causes the server to crash. In most cases, you should keep generate_biomes set to 'false' to ensure the world stays empty and the performance remains high for your minigame players.

Ignoring the Air Exposure Check

I’ve seen many server owners complain that their flat worlds are "leaking" stone through the grass. This happens if you forget to enable the air_exposure_check in the Material Provider; without it, the engine doesn't know which side of the block is the "top."

Incorrect Chunk Border Alignment

When upgrading an old Update 1 map to V2, you might see "cliffs" at the edge of new chunks. To fix this, you must set the legacy_smoothing parameter to 'true' in your world configuration, which I found blends the old heightmaps with the new V2 noise.

For Server Owners

If you run a public server, optimizing your lobby template is the easiest way to save on monthly costs. Efficient templates use fewer CPU cycles, allowing you to host more players on the same hardware. Compare Hosting Providers to find a plan that supports Hytale’s V2 multithreading.

Related Resources

• Hytale Server Setup Guide
• Choosing the Best Hytale Hosting (2026)
• Advanced WorldGen Documentation

Written by a HytaleBox contributor with experience in sandbox survival games and Hytale Early Access testing.