The Forest supports mods in multiplayer only to a limited extent. For many extensions, you use ModAPI on the client, while real server adjustments mostly run through configuration values. What matters is that all players use the same client mods and that you test server-side changes traceably before continuing a production save.
Requirements
For The Forest mods, you need an installed PC version of The Forest, access to the local game folder, and a server whose configuration you can edit and restart. At game-serverhosting, this approach fits well with a controlled multi-game setup: you keep server files, restarts, and configuration changes separate from players' client mods and can document changes cleanly.
Create a backup of your savegame and server configuration before every change. Mods can affect saves, balancing, and stability. This is especially true if you combine multiple mods or later adjust an existing world.
Install ModAPI for The Forest
ModAPI is the most important tool for The Forest mods:
- Download and install ModAPI
- Select the The Forest path
- Browse and enable mods
- Click "Launch"
Install ModAPI only on the clients that should play with mods. Select the correct The Forest installation folder in the tool and then start the game through ModAPI, not through a normal desktop shortcut. This ensures the enabled mods are loaded when the game starts.
If a player joins without ModAPI or with a different mod list, features may be missing, menus may look different, or connection problems may occur. Therefore, you should give your group a short mod list with name, version, and installation note.
Popular Mods
| Mod | Description |
|---|---|
| Champions of the Forest | RPG elements, leveling |
| Ultimate Cheatmenu | Admin tools |
| Enemy Health Bars | HP display for enemies |
| More Resources | More resource spawns |
| Animal Taming | Tame animals |
These mods mainly change the gameplay experience on the client side. Before using them, check whether the respective mod still matches the installed game version and whether it works sensibly in multiplayer. Admin or cheat menus in particular should only be used in closed groups because they can strongly affect game balance and trust.
Server Mods and Limits
The Forest has limited server mod support:
- Most mods are client-side
- Server-side mods usually through configuration changes
- All players need the same mods
In practice, this means: do not treat ModAPI like a classic server mod system. The server provides the world, slots, saves, and configuration logic; many mod functions, however, run on the clients. For stable operation, you should first test large mod changes on a separate test save.
If you also run other survival servers, a consistent approach for mod lists and rollbacks is worthwhile. You can find similar principles in the guide to Installing Valheim Mods with BepInEx and Installing V Rising Mods, even though the technical frameworks work differently there.
Configuration-Based Adjustments
Instead of mods, you can change many things through the config:
veganMode on # No enemies
vegetarianMode on # Fewer enemies
treeRegrowMode on # Trees regrow
allowBuildingDestruction off # Buildings indestructible
The official The Forest wiki page for Dedicated Servers documents these server options and admin commands at documentation on theforest.fandom.com. Among other things, it describes veganMode, vegetarianMode, treeRegrowMode, and allowBuildingDestruction as configuration values or command options.
Use these values if you want to enforce a change server-wide and traceably for all players. treeRegrowMode on, for example, is suitable for long-term worlds where wood resources should remain available. allowBuildingDestruction off can protect bases from accidental or intentional damage. veganMode and vegetarianMode change enemy behavior and should be chosen deliberately because they significantly shift the difficulty.
Check the Result
Restart the server after a config change and connect with a client. Then check not only whether the server is reachable, but also whether the specific change becomes visible in-game. For example, test whether buildings take damage, whether enemies appear as expected, and whether trees regrow under the appropriate game conditions.
For client mods, also check whether mod menus open, HUD elements are visible, and all players see the same effects. If only one player sees a function, the mod is probably not aligned cleanly across the group or is fundamentally client-side.
Troubleshooting
ModAPI Does Not Find The Forest
Select the installation folder manually. Make sure you enter the actual The Forest game folder, not just the Steam library folder. Then restart ModAPI and check again.
Players Cannot Join
Compare the ModAPI version, mod selection, and game version. Temporarily remove all mods and connect again. If joining works without mods, the cause is probably a mod or an incompatible combination.
Config Changes Do Not Apply
Check whether you edited the active server config and whether the server was fully restarted after saving. Also check spelling and values, for example on or off.
The Save Seems Damaged or Unstable
Stop making further changes and restore a backup. Then test each mod individually before enabling the complete mod list again. For production worlds, you should never adopt new mods directly without a test run.
Sons of the Forest
The sequel already has an active mod community. You can find mods on Nexus Mods. But do not confuse these mods with The Forest mods: the game, mod frameworks, and compatibility must be considered separately.
Verification, Limits, and a Safe Rollback
The guide "Install The Forest Mods - ModAPI Guide" applies to the server type described in the article and the version state visible at the time of review. Menu names, available versions, mod or plugin compatibility, and required resources may differ after updates. Therefore, do not transfer any values unchecked to a different game, loader, or server version.
Before changing a world, savegame, configuration, or extensions, create a backup of the affected files. Then change only one related step and test it with the same client and server version you want to play with later.
| Checkpoint | Expected Result | Abort and Rollback |
|---|---|---|
| Server startup | The server reaches the ready-to-run state without new error messages. | If startup errors occur, revert the change and restore the latest backup. |
| Connection test | A test account can connect using the address shown in the panel. | If version or connection errors occur, compare version, port, and firewall rules again. |
| Function test | The specifically changed function works without damaging existing world or game data. | If side effects occur, stop the server and restore the backed-up files. |
A successful individual test is not a performance or availability guarantee. World size, mods, plugins, player count, network path, and simultaneous load can change the result. Document version, change, and test result so you can understand later deviations.
FAQ
Can I Install The Forest Mods Directly on the Server?
Only to a limited extent. Many The Forest mods run client-side through ModAPI. Server-side adjustments usually happen through supported configuration values.
Do All Players Have to Install the Same Mods?
Yes, with ModAPI setups this is the most reliable approach. Different mod lists can lead to missing features, mismatches, or connection problems.
Are Config Changes Safer Than Mods?
They are usually easier to trace because they are defined by the server and do not require additional client files. Still, you should create a backup beforehand and test the change.
Which Mods Should I Test First?
Start with a single mod that has a clearly visible effect. Then restart the server and client, check the behavior in-game, and only then add more mods.
Can I Remove Mods Again Later?
Often yes, but not every mod leaves a save unchanged. Therefore, remove mods on a test save first and keep a backup ready before changing a live world.