Terraria Journey Mode Server Setup: What Makes It Different

Journey Mode is not easy mode. It is a separate character and world type with a completely different permission model. The configurable powers (God Mode, time control, weather, the difficulty slider, spawn rate) are there if you want them, locked away if you don’t, set per-power for every player on the server. Journey’s research and item duplication come with the mode itself and are not gated by these flags, so plan around that if you need to limit them.

That distinction matters immediately when you are setting up a dedicated server, because the character and world restrictions are hard constraints. For the broader picture of how multiplayer works in Terraria, see the broader multiplayer options breakdown.

What Makes a Journey Server Different

Classic, Expert, and Master worlds differ only in enemy stats and loot. Journey is a fundamentally different world type: Journey characters exist in their own character class, Journey worlds require Journey characters, and the server exposes a set of permission flags that control which powers players can use.

The permission system is what most guides miss. Each of the 15 powers has its own flag you set to locked, host-only, or open-to-everyone, and what an unset flag does is not consistent enough to count on. Set every flag you care about explicitly so powers are not accidentally left open, or locked, for the whole server. Getting that configuration right is the difference between a useful sandbox and a tug-of-war.

The Character and World Type Lock

If someone’s character won’t connect to your server, check this first. The error is usually silent or presents as a generic disconnect. The fix is always the same: the player needs a Journey character, or you are running the wrong world type.

The world type is locked at creation. You cannot convert an existing Classic, Expert, or Master world to Journey after the fact through vanilla means. Third-party tools like TEdit can modify world files, but that is outside vanilla support and introduces corruption risk.

Journey characters also cannot play in Classic, Expert, or Master worlds. If your group is mid-playthrough on a Classic world and wants Journey powers, you are starting a new world. There is no migration path in vanilla.

For more troubleshooting once character type is confirmed, see connection troubleshooting.

Configuring serverconfig.txt for a Journey World

The critical setting is difficulty=3. This tells the server to generate a Journey world when autocreate is used. Here is a working config block:

world=worlds/JourneyWorld.wld
worldname=JourneyWorld
autocreate=2
maxplayers=8
port=7777
password=yourpassword
difficulty=3
secure=1
language=en-US

Difficulty values: 0 = Classic, 1 = Expert, 2 = Master, 3 = Journey.

For a complete walkthrough of the rest of the server configuration, see the full dedicated-server walkthrough.

If the World Already Exists at the Wrong Difficulty

If you already have a world file and it is not a Journey world, you have two options:

• Delete or rename the existing world file and let the server generate a fresh one with difficulty=3.
• Change the world path to point to a new file name, so the server creates a new Journey world alongside the old one.

Changing difficulty=3 in the config while pointing to an existing non-Journey world file does nothing. The server loads the existing file as-is.

tModLoader: World Creation and Journey Difficulty

tModLoader uses the same serverconfig.txt format. Set difficulty=3 the same way. If you are creating the world through the tModLoader server menu rather than via autocreate, select Journey difficulty at the world creation screen.

One thing to watch: tModLoader server versions need to match what your players are running. If someone is connecting with a tModLoader client version that differs from the server, they will be rejected before the Journey character check even matters. See the tModLoader server setup guide for version management.

Per-Power Permissions: The Part Nobody Documents

This is where a Journey server diverges most from a vanilla setup. Every Journey power has its own permission flag in serverconfig.txt, each accepting one of three values:

• 0 - Locked for everyone, including the host
• 1 - Host only (the player designated as host on the dedicated server)
• 2 - All players can use it

Here are all 15 flags:

Don’t rely on what an unset flag does. Set every journeypermission_* flag you care about explicitly in serverconfig.txt (0 to lock it, 1 for host only, 2 for everyone) so each power is exactly as locked or open as you intend.

Recommended Permission Profiles

Three setups that work well for different group types.

Trust everyone - open sandbox

Every player controls everything. Best for a small, coordinated group where everyone is on the same page.

journeypermission_time_setfrozen=2
journeypermission_time_setdawn=2
journeypermission_time_setnoon=2
journeypermission_time_setdusk=2
journeypermission_time_setmidnight=2
journeypermission_time_setspeed=2
journeypermission_wind_setstrength=2
journeypermission_wind_setfrozen=2
journeypermission_rain_setstrength=2
journeypermission_rain_setfrozen=2
journeypermission_godmode=2
journeypermission_setdifficulty=2
journeypermission_setspawnrate=2
journeypermission_biomespread_setfrozen=2
journeypermission_increaseplacementrange=2

Host-controlled - shared world, admin powers

World-affecting powers stay with the host. Each player manages their own God Mode. Prevents one person from freezing time mid-boss fight without agreement.

journeypermission_time_setfrozen=1
journeypermission_time_setdawn=1
journeypermission_time_setnoon=1
journeypermission_time_setdusk=1
journeypermission_time_setmidnight=1
journeypermission_time_setspeed=1
journeypermission_wind_setstrength=1
journeypermission_wind_setfrozen=1
journeypermission_rain_setstrength=1
journeypermission_rain_setfrozen=1
journeypermission_godmode=2
journeypermission_setdifficulty=1
journeypermission_setspawnrate=1
journeypermission_biomespread_setfrozen=1
journeypermission_increaseplacementrange=2

Locked - world settings fixed, survival intact

Lock the world-altering powers and God Mode so the run stays a real survival challenge. Journey’s research and duplication still work (they are not gated by these flags). Useful for groups that want a casual playthrough without powers changing the game mid-session.

journeypermission_time_setfrozen=0
journeypermission_time_setdawn=0
journeypermission_time_setnoon=0
journeypermission_time_setdusk=0
journeypermission_time_setmidnight=0
journeypermission_time_setspeed=0
journeypermission_wind_setstrength=0
journeypermission_wind_setfrozen=0
journeypermission_rain_setstrength=0
journeypermission_rain_setfrozen=0
journeypermission_godmode=0
journeypermission_setdifficulty=0
journeypermission_setspawnrate=0
journeypermission_biomespread_setfrozen=0
journeypermission_increaseplacementrange=2

How Powers Behave in Multiplayer

Not all Journey powers operate the same way when multiple players are involved.

World-shared powers affect everyone on the server when used:

• Time freeze, time skip, and time speed
• Weather controls (wind strength, wind freeze, rain strength, rain freeze)
• Difficulty slider
• Enemy spawn rate
• Biome spread toggle

If someone has journeypermission_setdifficulty=2 and changes the slider mid-session, that change applies to the whole world immediately. This is the main reason the host-controlled profile above locks those flags to 1.

Per-character powers are individual:

• God Mode is per-character. One player in God Mode has no effect on anyone else.
• Extended placement range is per-character.

Research and Duplication on a Server

Research progress is character-bound, not world-bound. Each player maintains their own research library tied to their character file.

In multiplayer, players on the same in-game team share research in real time: if you sacrifice enough of an item to complete its research while teammates are in the world, they receive that unlock too. This sharing is not retroactive. A player who was offline when you completed an item’s research does not receive that unlock when they log in later. They need to research it themselves.

The team that matters here is the in-game team system (the color-coded teams in the social menu), not simply being in the same world. Players in the same world but on different teams do not share research.

If your group plays asynchronously, expect some research desync over time. A mod like Tome of Research Sharing can address this on a tModLoader server.

Common Pitfalls

Mismatched character type. The most common issue by far. Journey world plus a non-Journey character means immediate rejection. Confirm the character type before anything else.

Overwriting an existing world by reusing the same worldname. If you previously ran a Classic world with worldname=MyWorld and add difficulty=3 to the config, the server loads the existing Classic world file. The difficulty flag does not apply retroactively. Change the worldname or world path to force new world generation.

Journey powers not behaving as expected because flags were not set. The behavior of an unset journeypermission_* flag is not consistent to rely on, so set every flag you care about explicitly in serverconfig.txt (0 locked, 1 host only, 2 everyone). That way each power is exactly as locked or open as you intend.

Mod version mismatches downgrading saves. On tModLoader, a player connecting with an older mod version than the server can cause issues with mod-added character or world data. Keep everyone on matching mod versions. For Terraria server RAM sizing on modded setups, that guide covers what to expect from heavier mod loads.

Journey Mode with tModLoader

Journey Mode works fully with tModLoader. The difficulty=3 configuration is identical to vanilla. Journey powers function alongside mod content without special configuration.

Journey-specific mods (mods that extend the research list or add research mechanics) vary in compatibility and are worth checking individually on the Steam Workshop. Broad content mods like Calamity and Thorium function with Journey worlds.

Running a Calamity server on a Journey world is a valid setup. The main consideration is that God Mode, difficulty sliders, and spawn rate controls can trivialize Calamity’s progression if left open to all players. That is a deliberate choice, not a bug, but it is worth agreeing on before setting journeypermission_setdifficulty=2 and finding out someone’s definition of “sandbox mode” differs from yours.

For the full tModLoader server setup process, that guide covers mod installation, 32-bit vs 64-bit builds, and the most common connection issues.

When Journey Is the Right Server Choice

Journey Mode servers work well for:

• Friend-group sandboxes where people want to build or explore without the grind
• Casual replays with players who have already completed the progression once and want to focus on a different part of the game
• New player onboarding - dialing down spawn rates and difficulty while someone finds their footing is genuinely useful
• Screenshot and photography worlds where you need specific lighting or weather conditions on demand

It is a worse fit for:

• Hardcore progression runs where the challenge is the point
• Calamity or difficulty-mod playthroughs where the design assumes standard survival mechanics
• Groups with mixed expectations about whether powers will be used - that conversation should happen before world creation, not after

Getting Your Journey Server Running

A managed Terraria server hosting setup at WinterNode handles the infrastructure side: instant setup, automatic backups, no port forwarding, and no CPU throttling during boss fights. The Journey Mode configuration above works exactly the same on a managed server as it does self-hosted, and plans start at $1.99/GB per month.

Get your Terraria server →