Green Hell Server Hosting: Complete Guide for Co-op

Green Hell is one of the most realistic survival games available, dropping you into the Amazon rainforest with nothing but a backpack radio and your will to live. The co-op mode lets up to four players share the experience, and running your own dedicated server means the jungle persists around the clock. Shelters stay built, crops keep growing, and your group can log in at different times without losing progress.

This guide covers everything you need to choose the right hosting for a Green Hell server, configure it for your group, manage saves, add mods, and fix the problems that come up most often. If you are looking for a step-by-step installation walkthrough, our Green Hell server setup guide covers that in detail.

Hosting requirements for Green Hell

Green Hell is not as demanding as open-world games with hundreds of players, but it still needs decent hardware. The server handles AI for wildlife, environmental simulation, disease tracking, and physics for every structure your group builds. Here is what each resource needs to handle.

RAM

A Green Hell dedicated server needs between 4 and 6 GB of RAM. The baseline with one or two players exploring a small area sits around 3.5 GB, but it climbs once players spread out and the server loads multiple biomes simultaneously. With all four players in different regions of the map, expect peaks around 5 to 5.5 GB.

What drives memory usage specifically:

• Loaded biomes: each player in a distinct area forces the server to keep that terrain and its AI in memory.
• Built structures: every placed object (shelters, fires, drying racks, walls, traps) stays in memory. A group that builds multiple large camps across the map pushes usage toward the upper range.
• Item tracking: dropped items, harvested resources, and container inventories all count. Keep your camps tidy.

For most groups, 4 GB is enough to start. If you plan on building extensively or if all four players tend to explore independently, go with 6 GB from the start to avoid mid-session stutters.

CPU

Green Hell benefits from a fast single-thread clock speed more than from many cores. The server uses 2 to 3 threads under normal load. Wildlife AI is the single largest CPU consumer: the server calculates patrol routes, aggression triggers, and spawn cycles for jaguars, caimans, snakes, and other animals across every loaded area.

A modern CPU like the AMD Ryzen 9 7950X handles Green Hell without breaking a sweat. The game was designed for small groups, so even during the busiest moments with four players fighting wildlife in separate biomes, CPU usage stays well below what most hosting providers allocate per server.

Storage and network

The Green Hell dedicated server files take about 5 GB of disk space. Save files grow over time as you build and explore, but rarely exceed a few hundred megabytes even after dozens of hours of play. NVMe storage is ideal because autosaves complete instantly without causing a brief freeze.

Network requirements are minimal. With a maximum of four players and no high-speed PvP combat, bandwidth stays low. The server needs UDP port 27015 (game traffic) and UDP port 27016 (Steam query) open. Latency matters more than bandwidth: players closer to the server notice smoother animations and faster item interactions.

How co-op works in Green Hell

Green Hell co-op supports 2 to 4 players. There is no way to raise this cap, and that is intentional. The game is balanced around small-group survival. The jungle is meant to feel dangerous, and a squad of ten would trivialize most of the challenge.

Dedicated server vs host-and-play

Green Hell offers two multiplayer options: one player hosts from their own game client, or you run a dedicated server. The differences matter:

• Persistence: a dedicated server keeps the world running even when nobody is online. Crops grow, time passes, and the world is ready when anyone logs in. With host-and-play, the world only exists while the host is playing.
• Performance: the host machine in a host-and-play setup runs both the server and the game client simultaneously. This leads to lower framerates for the host, especially in areas with dense vegetation and active wildlife. A dedicated server offloads all that processing.
• Availability: your group does not depend on one person being online. Any of the four players can log in at any time.

For a weekend session between friends, host-and-play works fine. For an ongoing survival project that spans weeks or months, a dedicated server is the right choice.

Joining a server

Players connect through the Steam server browser or by adding the server IP directly. The server appears under the community tab if GameVisibility is set to public. For a private server, share the IP and port with your group and they add it manually. No password system exists in the base game, but setting GameVisibility to private hides it from the browser list.

Server settings explained

Green Hell stores server configuration in a file that the server generates on first launch. Here are the settings that matter most and how they affect the co-op experience.

Difficulty levels

The difficulty setting changes how punishing the jungle is. Each level adjusts damage taken, hunger and thirst drain rates, disease frequency, and resource availability.

• Tourist: almost no survival pressure. Health regenerates, hunger drains slowly, diseases are rare. Good for players who want to explore the story without the survival challenge.
• Normal: the intended experience. You need to manage food, water, sleep, and health actively. Diseases happen at a realistic rate. Most groups should start here.
• Hard: everything drains faster, injuries are more severe, and food spoils quickly. Recommended only for experienced players who know the crafting system and food sources well.
• Custom: lets you toggle individual mechanics independently. Want the survival pressure of Hard mode but without parasites? Custom mode makes that possible.

Survival mode vs Spirits of Amazonia

Survival mode is the open sandbox. There are no quest markers, no story progression, just you and the jungle. Your server can run indefinitely with players setting their own goals: build a permanent camp, explore the entire map, or simply survive as long as possible.

Spirits of Amazonia is the narrative campaign spread across multiple chapters. Your group works with indigenous tribes, completes quests, and progresses through a structured story. Running this on a dedicated server works well because progress saves between sessions. The group can tackle one chapter per evening and pick up where they left off.

You choose the mode when creating the server world. Changing modes later requires creating a new world.

Key configuration options

Save management

Green Hell saves the world state to disk during autosaves and when players manually trigger a save at a constructed shelter. Understanding how saves work on a dedicated server prevents the most common frustrations.

Autosave behavior

The server autosaves at regular intervals. The default is every few minutes of real time. During an autosave, the server writes the current state of the entire world to a file. On fast NVMe storage this takes a fraction of a second. On slower disks, players might notice a brief hitch.

Manual saves

Players can trigger a manual save by sleeping in a shelter. This creates a save point that the server records. Both autosaves and manual saves write to the same save slot unless you configure multiple save slots.

Backing up saves

Always back up your save files before a Green Hell game update. Creepy Jar has changed save formats between major versions in the past, and an update can occasionally make an old save unreadable. The save directory sits inside the server installation folder. Copy the entire save folder to a separate location before updating. On a HostValues VPS, you can set up a simple cron job that copies the save directory to a backup folder daily:

0 4 * * * cp -r /home/greenhill/saves /home/greenhill/backups/saves-$(date +\%Y\%m\%d)

If an update breaks your save, you restore from the backup and wait for a hotfix from the developers.

Transferring saves

Moving a save from a local game to a dedicated server (or between servers) works by copying the save files over SFTP. Make sure the server is stopped before replacing save files. Start the server after copying, and it loads the transferred world on boot.

Mod support

Green Hell has a growing modding community, though it is smaller than what you find for games like Minecraft or Valheim. Mods are distributed through Nexus Mods and community forums rather than Steam Workshop.

Common mod categories include:

• Quality of life: larger stack sizes, extended crafting recipes, improved inventory management.
• Difficulty adjustments: slower hunger drain, modified disease rates, changed wildlife spawn frequencies.
• Visual mods: texture replacements and lighting changes. These are client-side only and do not need server installation.

To install server-side mods, download the mod files and place them in the appropriate directory within the server installation. Each mod comes with its own instructions. Always test mods on a copy of your save first, because not all mods are compatible with each other or with the latest game version.

Keep in mind that all players connecting to a modded server need to have the same mods installed on their game client. Coordinate with your group before adding mods mid-playthrough.

Troubleshooting common issues

Green Hell servers are relatively stable, but a few problems come up regularly. Here is how to diagnose and fix them.

Server starts but players cannot connect

• Check that UDP ports 27015 and 27016 are open in your firewall. Both are required.
• Verify the server IP. If you are behind NAT, players need your public IP, not the internal one.
• Make sure the game version on the server matches the client version exactly. Green Hell does not allow version mismatches.
• Check GameVisibility. If set to Private, the server does not appear in the browser. Share the IP and port directly.

Lag spikes during gameplay

• All four players in different biomes creates the highest server load. If lag appears only when the group spreads out, this is the cause. The server loads terrain, AI, and environmental data for each active area independently.
• Very large bases with hundreds of placed objects increase memory usage and save time. If a base has grown enormous, consider whether every item is still needed.
• Restart the server once a day. Green Hell accumulates memory over long sessions. A daily restart via cron keeps things clean.
• Check your RAM allocation. If the server consistently uses more than 90% of available memory, upgrade to the next plan.

Save corruption after an update

If the server fails to load a save after a Green Hell update, the save format may have changed. Restore from your most recent backup and wait for the developer hotfix. Creepy Jar typically addresses save compatibility issues within a week of a major update.

Server crashes during autosave

This usually indicates insufficient disk space or a permissions issue. Check available storage with df -h and verify the server process has write access to the save directory. On a VPS, running out of disk space is the most common cause.

Players getting disconnected randomly

• Check the server console for error messages at the time of disconnection.
• Verify that your hosting provider includes DDoS protection. Even small attacks can disrupt a game server.
• Ensure the server has enough RAM. Memory pressure causes the OS to kill processes, which looks like a crash from the player side.
• If disconnections coincide with autosaves on slow storage, move to NVMe-based hosting.

Choosing the right hosting plan

For Green Hell, a VPS with 4 to 6 GB of RAM, 2 to 3 CPU cores, NVMe storage, and DDoS protection covers everything the game needs. The 4-player cap means you will never need the kind of hardware that a 100-player Minecraft network demands.

What matters most for Green Hell specifically:

• Single-thread CPU speed: wildlife AI and environmental simulation run primarily on one or two threads. A high clock speed matters more than core count.
• NVMe storage: prevents autosave hitches that disrupt gameplay.
• Low latency: a server located near your group gives smoother item interactions and combat responsiveness. Use a latency test to find the closest location.
• DDoS protection: even a small volumetric attack knocks a game server offline. Make sure your provider includes this by default.

HostValues VPS plans run on AMD Ryzen 9 7950X processors with NVMe storage and include DDoS protection on every plan. A 4 GB VPS handles Green Hell comfortably for a casual group; go with 6 GB if your group builds extensively or explores independently. Plans are on the VPS hosting page.

Frequently asked questions

Can I run Green Hell and another game server on the same VPS?

Yes, if you have enough RAM. Green Hell uses 4 to 6 GB, so you would need a VPS with at least 10 GB to run a second game alongside it. Make sure the port numbers do not conflict.

Does the world keep running when nobody is online?

Yes. A dedicated server keeps the world loaded at all times. Time-based mechanics like crop growth continue even when all players are offline. This is one of the main advantages over host-and-play multiplayer.

Can I switch between Survival and Spirits of Amazonia?

Not on the same world. Each mode creates its own world with different parameters. You can run both by maintaining two separate server configurations, but only one can be active at a time unless you have the resources for two server instances.

How often should I restart the server?

Once every 24 hours is a good practice. Green Hell accumulates memory over long sessions as players explore new areas and build structures. A daily restart at a low-traffic hour keeps performance consistent.

Is Green Hell cross-platform for co-op?

Green Hell is available on PC, PlayStation, Xbox, and Nintendo Switch, but dedicated servers are PC only. Console players use the built-in host-and-play system. Cross-platform play between PC and consoles is not supported.

For the installation walkthrough, see our Green Hell server setup guide. Need help sizing your plan? The RAM calculator gives a quick recommendation. All VPS plans and specifications are on VPS hosting.