How To Apply Configs In TModLoader: Complete Setup & Troubleshooting Guide

Modifying and applying custom configurations in tModLoader requires adjusting setting parameters through the native in-game Mod Configuration menu or manually editing localized JSON files within the system directory. Server-side gameplay parameters synchronize automatically across all connected clients upon joining a host session, whereas client-side visual and interface options apply immediately upon saving. Validating JSON syntax integrity and maintaining correct file access permissions prevents unexpected configuration overrides during automated mod updates.

Pre-Configuration Checklist & Directory Architecture

Before modifying mod parameters in tModLoader, establish access to the underlying filesystem and verify environment readiness. Configurations in tModLoader operate via structured JSON (JavaScript Object Notation) files. Editing these files outside the game interface requires a stable plain-text editor such as Notepad++, Visual Studio Code, or standard system text tools.

• Essential Operating Tools:

  
  
  
  • Active installation of tModLoader (version 2022.05 or newer matching Terraria 1.4+ standards).
  • Plain-text editor capable of UTF-8 encoding without byte order mark (BOM) corruption.
  • File archive utility for creating pre-modification backup archives.

• Mandatory Technical Benchmarks:

  
  
  
  • Administrative access to the system local user profile directory.
  • Familiarity with standard JSON syntax elements including boolean toggles (true/false), floating-point numbers, integers, and string variables.
  • A minimum of 50 Megabytes of available storage space for log files and local system backups.

• Default Configuration File Paths:

  
  
  
  • Windows Systems: Drive C, Users, YourUsername, Documents, My Games, Terraria, tModLoader, ModConfigs.
  • Linux Systems: Home, Username, Local, Share, Terraria, tModLoader, ModConfigs.
  • macOS Systems: Users, Username, Library, Application Support, Terraria, tModLoader, ModConfigs.
  • Steam Deck / SteamOS: Home, Deck, Local, Share, Terraria, tModLoader, ModConfigs.

• Estimated Duration: 2 to 5 minutes for in-game adjustments; 5 to 10 minutes for manual JSON edits and server configuration deployments.

How to Apply Configs in tModLoader: Complete Workflow

Modifying game behavior in tModLoader can be executed via two distinct methods: the built-in user interface or direct editing of the underlying configuration files. The following systematic workflow covers both approaches to ensure your custom settings persist across single-player and multiplayer gaming sessions.

Step 1: Navigating the In-Game Mod Configuration Interface

The primary and safest method for applying configurations is through the integrated graphical user interface provided by the tModLoader core engine.

1. Launch tModLoader and navigate to the main menu.
2. Select the Mods option from the main menu list.
3. Locate the Mod Configuration button positioned at the bottom left or center of the active mods interface. Alternatively, click the dedicated gear icon located next to an individual enabled mod within your active mod list.
4. Click the target mod's configuration entry to expand its available settings categories.
5. Identify whether the settings belong to a client-side configuration header (affecting graphics, sound, and local UI) or a server-side configuration header (affecting item drop rates, mob health, and world generation mechanics).

Pro-Tip: If a mod does not display a gear icon or appear within the Mod Configuration menu, that specific mod either lacks customizable parameters or forces static variables hardcoded by its author.

Step 2: Modifying Parameters and Executing Soft Reloads

Once inside the graphical configuration menu, adjustments must be formally committed to the runtime environment.

1. Adjust desired sliders, toggle buttons, text entry boxes, or dropdown fields to your target preferences.
2. Review numerical thresholds to ensure values remain within supported bounds (for example, setting spawn rate multipliers within realistic limits like 0.5x to 10.0x rather than extreme values that crash the engine).
3. Click the Save Config button located at the bottom of the interface panel.
4. If prompted by the engine, click Reload Mods. This action forces tModLoader to purge the current memory cache and re-read the newly generated configuration values into active RAM.
5. Launch a local single-player world to confirm that the changes have taken effect in the active session.

Warning: Modifying server-side settings while actively connected to a remote multiplayer server will fail or cause synchronization errors. Always apply server-level configuration changes from the main menu or directly host the world locally to propagate settings.

Step 3: Manually Editing Raw JSON Files

When managing dedicated servers, headless Linux instances, or advanced mod combinations, manual file modification is the most efficient and reliable method.

1. Exit tModLoader completely to unlock file access permissions and prevent active memory overwrites.
2. Open your system file manager and navigate to the local directory path: Documents/My Games/Terraria/tModLoader/ModConfigs.
3. Locate the target configuration file, which typically follows the naming structure ModName_ConfigName.json (for example, CalamityMod_CalamityConfig.json).
4. Right-click the file and open it with your preferred text editor.
5. Locate the targeted key-value pairs within the nested bracket structure. Modify values while strictly adhering to JSON standards:
   
   
   • Maintain double quotation marks around key names and string values.
   • Ensure boolean values remain strictly lowercase (true or false).
   • Confirm floating-point numbers use standard periods as decimal separators rather than commas.
   • Do not place a trailing comma after the final parameter inside a list or object block.
6. Save the document with UTF-8 encoding and close the text editor.

Step 4: Validating and Forcing Configuration Sync

After applying manual edits to the JSON files, verify that tModLoader accepts the updated parameters without reverting to default values.

1. Launch tModLoader and allow the mod initialization phase to complete fully.
2. Check the lower-left area of the screen for red error notifications indicating JSON parse exceptions.
3. If hosting a multiplayer server, start the server executable (start-tModLoaderServer.bat or the Linux binary equivalent).
4. Ensure the server console reads the configuration file during initialization without outputting syntax warning lines.
5. Connect a client player to the host server. The client automatically downloads and applies the host server's world rules for the duration of the connected session, overriding local client files for server-scoped variables.

Configuration Architecture & Compatibility Matrix

Understanding how tModLoader categorizes configuration variables prevents editing conflicts and unexpected gameplay behavior. The table below outlines structural specifications across various configuration types.

Mod Configuration Failures & Conflict Remedies

When applying configurations in tModLoader, technical errors can cause settings to revert, crash the client, or fail to sync across multiplayer networks. Use these diagnostic workflows to resolve issues.

Configs Revert to Default Upon Game Launch

• Root Cause: The tModLoader JSON parser encountered a syntax error (such as a missing bracket, trailing comma, or invalid data type) during launch. To protect stability, the engine overwrites the corrupted file with default values.
• Actionable Fix: Close tModLoader. Delete the corrupted JSON file inside the ModConfigs directory. Relaunch the game to generate a fresh, uncorrupted configuration template. When editing manually, use an online JSON validator to verify syntax before launching the game engine. Alternatively, make adjustments exclusively through the in-game Mod Configuration menu to eliminate human formatting errors.

Server-Side Settings Fail to Apply to Joining Players

• Root Cause: The host applied changes to local client files rather than updating the active server instance config, or joining clients are running locally conflicting client-side mod overrides.
• Actionable Fix: If hosting via Steam Host & Play, edit the server configs from the main menu before opening the world to players. If running a standalone dedicated server, modify the JSON files located in the dedicated server's specific ModConfigs folder. Ensure the host restarts the dedicated server executable after saving file changes.

Mod Configuration Button Missing or Grayed Out

• Root Cause: The specific mod developer did not write a ModConfig class inside the mod C# source code, or the mod configuration relies on world state data accessible only after loading into a live map.
• Actionable Fix: Enter a single-player world with your character and open the pause menu. Select Settings, then access the Mod Configurations sub-menu directly from inside the active world session. If the option remains missing, inspect the mod's official documentation to confirm whether external configuration is supported.

Game Freezes or Engine Crashes During Soft Reload

• Root Cause: A numerical configuration value exceeded the allowable minimum or maximum boundary set within the mod developer's code (for example, setting item stack sizes to a negative number or extremely high value).
• Actionable Fix: Navigate directly to the ModConfigs system directory. Open the corresponding .json file in a text editor and locate the problematic numerical parameter. Reset the parameter to a standard, conservative integer value. Save the file, launch tModLoader, and trigger a mod reload.

Frequently Asked Questions

How do I find the ModConfigs folder in tModLoader?

You can quickly open the folder directly through tModLoader by navigating to Mods on the main menu, selecting Mod Configuration, and clicking the Open Config Folder button located at the bottom of the screen. Alternatively, paste the directory path %UserProfile%\Documents\My Games\Terraria\tModLoader\ModConfigs into your Windows File Explorer address bar.

Do tModLoader server configs apply to all players automatically?

Yes. Whenever a player connects to a host or dedicated server, tModLoader automatically synchronizes all server-side settings to the joining client. Local player settings are temporarily overridden by the host server's configuration for the duration of that multiplayer session.

Why do my custom mod config changes get overwritten after a mod update?

Mod updates typically retain existing JSON configurations unless the mod author restructures the configuration code, adds mandatory new parameters, or changes key variable names. When structural changes occur, the configuration parser cannot map old keys to new definitions, causing the engine to regenerate a clean default file.

Can I edit tModLoader configs while the game is running?

You can edit configuration files while the game is running, but you must trigger a manual reload for changes to take effect. Navigate to the Mods menu inside tModLoader and click Reload Mods to force the engine to purge cached RAM data and read the updated JSON files from disk.

What is the difference between a Client Config and a Server Config?

A Client Config controls options that only affect your local screen, audio, or user interface preferences, such as custom health bar placements or visual lighting effects. A Server Config controls gameplay mechanics that affect all players in a world, such as boss health scaling, enemy spawn caps, and item drop rates.

Master Your Modded Terraria Experience

Fine-tuning your configuration settings unlocks the full potential of tModLoader, allowing you to tailor performance parameters, rebalance difficult gameplay mechanics, and eliminate mod conflicts effortlessly. Apply these setup steps and directory rules today to build a stable, fully optimized modded environment for your single-player worlds and dedicated multiplayer servers.