Path of Titans Server Requirements and RAM Guide

Short answer: size for peak activity, not just the advertised slots

Alderon gives no official RAM figure for community servers. The numbers most renters work from come from hosts’ published guidance and from practical allowances used for Path of Titans plans. That guidance lines up well enough to build a safe starting point: 4 GB for up to 10 players, 8 GB for up to 20, 8-12 GB for a 20-50 player community, and about 16 GB for a server pushing towards 100 players.

The reason this works better than shopping by slots is simple: Path of Titans load comes from living world state. A server with modest slots but a lot of AI, bodies, footprints and a custom map can work harder than a larger but cleaner setup. If you want the wider hardware context behind thread speed, storage behaviour and memory headroom, our game server hardware guide covers the basics that matter when reading host plans.

Use this as hosts’ guidance rather than a guarantee. It is a starting size, then you tune the settings that actually drive load.

These figures are hosts’ guidance, not an official Alderon table.

What actually uses memory and CPU on a Path of Titans server

If you want to avoid overpaying, focus on the things that create persistent world state or frequent world updates. That is what eats RAM, keeps the main server thread busy and adds replication work for connected players.

Map choice sets the baseline

• ServerMap: Panjura is the default base map. Gondwa and Riparia are the other base choices. Each map is a different world for the server to load and track, with its own spawn points, water sources and AI areas. You can tell the map matters when a server that was comfortable on one map feels tighter on another before player count even peaks.
• Map mods: these add another jump because the server must check and load custom assets on boot. That hits disk and storage performance first, then raises the runtime memory baseline once the map is live. The player trade-off is stronger variety but a longer wait after updates and no access for many mobile players.

Players, AI and leftovers create the moving load

• Players as dinosaurs: every connected player adds replicated movement, status and interaction state. That costs RAM for actor state, main-thread CPU for simulation and bandwidth for updates to nearby clients. You notice this load when performance is fine at quiet times but degrades as concurrency rises.
• Critters: bServerCritters=true by default, with ServerMaxCritters=200 and ServerCritterDensityMultiplier=0.75. Critters are not free flavour; they are AI actors with simulation and replication overhead. Lowering their count or density reduces CPU work and trims memory use, but the world feels less alive and hunting opportunities drop. If stutters mostly happen in busy areas rather than on an empty server, critters are one of the first levers to pull.
• Fish: bServerFish=true by default. Fish are another class of living actor, so they add to the same pool of world simulation and client updates. Turning them off or keeping the rest of the ecosystem restrained can help public servers, but it removes food sources and ambient life.
• Corpses: ServerDeadBodyTime=0 means bodies persist until fully eaten or decayed. That can pile up actor state in hotspot areas, costing RAM and CPU and sending extra state to players nearby. A shorter body time cleans the world faster, but players lose time to scavenge. You know it helped if lag around common kill sites eases without a population drop.
• Respawn pressure: ServerRespawnTime defaults to 45 minutes, and Alderon suggests keeping it high to avoid corpse piles. The reason is not memory on the timer itself; it is behaviour. Fast returns can keep players feeding the same hotspot with more fights and more bodies. If corpse-related stutter is the issue, raising or keeping respawn time high is usually the safer direction.
• Water regeneration: the default WaterRegenerationRate is 60 seconds. Alderon warns that setting it too low makes the server update water more often and can cause lag. This is a pure frequency problem: more frequent world updates mean more main-thread work. The trade-off for players is a more reactive resource system versus extra server overhead. If lag starts after aggressive survival tweaks, this is worth reversing first.
• Footprints: ServerFootprintLifetime=60 by default and 0 disables them. Footprints are short-lived world traces, but on a busy public server there can be a lot of them. Shortening the lifetime or disabling them removes some state from the world at the cost of less tracking gameplay.
• Nests: nesting timers such as NestInactiveDespawnTimeSolo 120 stop abandoned nests from hanging around. Nests are another persistent world object, so longer despawn times keep more state alive. If nesting is central to your community, keep it; if not, avoid stretching nest persistence for no gain.

Slots, MaxPlayers and peak concurrency

Path of Titans lets you set MaxPlayers=100 in Alderon’s example configuration, and that same example shows ReservedSlots=20. Those numbers control admission policy, not the hardware hidden behind a rented plan. A host can sell the same slot count on very different RAM allocations, which is why slot billing often obscures what you are actually buying.

For planning, ignore the biggest number your config can technically hold and size for peak concurrent players. If your community is mostly a private herd, a high slot ceiling will not matter as much as stable world simulation when everyone is online at once. If you expect public spikes, leave headroom for those spikes rather than buying the smallest plan with a flashy slot count.

Ask one direct question before renting: how much RAM is included? If the answer is vague, you cannot compare that plan properly against another one. In Path of Titans, slots without RAM are not a resource spec.

Mods and map mods: where extra headroom starts to matter

Mods are enabled by Mod ID in GameUserSettings.ini under [PathOfTitans.Mods]. Creature, skin and Creator Mode item mods can stack, and the server checks and updates mods on every boot. That means modded servers hit storage and boot time harder than a clean server even before players join.

The bigger decision is the map. Only one map mod can run at a time, and Alderon notes that it can take 10-15 minutes to load after boot before the first join works properly. That long wait is not just inconvenience; it is a sign the server is validating and loading a large world package. In practice, if your unmodded plan already feels tight, a map mod is the point where moving up one size tier makes sense.

There is also a crossplay trade-off. Many map mods do not run on mobile, so adding one can lock out Android and iOS players even if the server still works well on PC and console. If your community depends on broad crossplay access, a base map plus lighter content mods is often the safer server plan.

How do you tell if you need more headroom rather than just patience? A long first boot after adding a map mod is normal. A server that eventually settles and plays smoothly may only need time. A server that keeps stuttering at ordinary population after the modded map is live is telling you the runtime baseline is now too high for the current tier.

Settings that change the load most

These are the settings worth checking first because they change either actor count or update frequency. Change one lever at a time, then watch the next peak period rather than judging from an empty server.

[/Script/PathOfTitans.IGameSession]
ServerMap=Panjura
MaxPlayers=100
ReservedSlots=20
bServerCritters=true
ServerMaxCritters=200
ServerCritterDensityMultiplier=0.75
bServerFish=true
WaterRegenerationRate=60
ServerDeadBodyTime=0
ServerRespawnTime=45
ServerFootprintLifetime=60
bServerAutoRestart=true
RestartLengthInSeconds=10800

The pattern behind all of these is straightforward. More actors means more RAM and more simulation work. More frequent updates mean more main-thread CPU. If a change helped, you should see one of three things: lower peak-time hitching, less slowdown around common hotspots, or shorter and more predictable boot behaviour after restarts.

Database choice and scheduled restarts

Alderon supports -Database=Local and -Database=Remote. Remote is the managed cloud database and is the recommended choice for most community servers because it lets several servers share character data and protects that data if the server folder is deleted. Local stores data in the DatabaseCache folder on the server, using account and character JSON files.

The important point is reliability, not raw speed. Remote does not replace the need for sensible server sizing, but it does reduce the risk of character loss and makes multi-server communities easier to manage. If you stay on Local, back up DatabaseCache regularly because that folder is the player-data lifeline.

Scheduled restarts are worth using on long-running servers. Alderon’s example shows RestartLengthInSeconds=10800, which is 3 hours. The value of a restart is that it forces a clean world load, re-checks mods on boot and clears out long-lived transient state that has accumulated over time. The trade-off is obvious: a cleaner server at the cost of short planned interruptions. If a server gets worse the longer it stays up, restarts are one of the cheapest fixes available.

Self-hosting basics: dedicated machine, command and ports

Alderon’s official hardware statement for self-hosting is short: use a dedicated Windows or Linux machine. That matters because the Path of Titans client on PC already wants 16 GB minimum and 32 GB recommended, with recommended CPUs at 6 cores or more and no support below 4 cores. If you host on the same PC you play on, the game and server are competing for the same RAM, CPU time and storage access.

If you are weighing rental against home hosting, our guide to self-hosting a game server covers the broader network and uptime trade-offs. Alderon also warns about the usual home-hosting problems: weaker upload speed than download on many home lines, extra CPU and storage load on the PC, downtime risk and ISP restrictions.

Server files are downloaded and updated with AlderonGamesCmd. Alderon provides the tool for Windows, Mac x64, Linux x64 and Linux arm64, but Linux arm64 server support is experimental. Alderon’s Linux guide was tested on Ubuntu 22.04, and it specifically says not to run the server as root.

AlderonGamesCmd --game path-of-titans --server true --beta-branch production --auth-token <token> --install-dir <dir>

You also need a hosting token, a unique ServerGUID and a database mode. One auth token can host up to 100 servers, which is useful if you split game modes or run a test server beside the live one.

Reading the signs before you pay for a bigger plan

Not every problem is a RAM problem. Path of Titans has a few failure patterns that point to configuration, ports or mods long before you should spend more money.

If the cause is still unclear after the obvious fixes, Alderon documents how to capture a Superluminal performance profile of the server on Windows and Linux. That is the right tool when you need to identify whether the bottleneck is a busy main thread, a modded world package or something more specific than “the server feels slow”.

What it costs: RAM size is not priced in a straight line

The awkward part of Path of Titans shopping is that many hosts sell by slot count and do not state the RAM. Our comparison data shows why that matters: price does not rise neatly with RAM, and the cheapest price per GB is not always attached to the smallest advertised package.

Conversion used: £1 = $1.33

The practical lesson is simple. A 10-slot plan can come with 10 GB RAM or 4 GB RAM, and the 10 GB option can still cost less. Buy the resource level that matches your server’s peak world load, not the smallest slot label in the store.

Tune it first or upgrade now?

Do the cheap fixes before you pay for a bigger server, but do not spend weeks micro-tuning a plan that is clearly undersized. This table is the quickest way to separate a settings problem from a hardware problem.

Path of Titans server FAQ

How much RAM does a Path of Titans server need?

There is no official Alderon RAM table for dedicated servers. A sensible starting point from hosts’ guidance is 4 GB for up to 10 players, 8 GB for up to 20, around 8-12 GB for 20-50 players, and about 16 GB for a server heading towards 100 players. Add headroom if you plan higher AI counts, a map mod or a busier public community.

How many players can a Path of Titans server hold?

Alderon’s example configuration shows MaxPlayers=100 and ReservedSlots=20. That does not mean every 100-slot plan is equally capable, because actual performance depends on RAM, CPU threads, map choice, AI settings and mods. Size the server for peak concurrent players rather than the highest slot number you can set.

Do mods need more RAM on a Path of Titans server?

Usually, yes. Ordinary content mods increase what the server has to check and load on boot, while a map mod raises the world baseline more sharply because it changes the whole map package. If you are adding a map mod to a plan that is already close to full load, moving up one size tier is the safer choice.

Can I host a Path of Titans server on my gaming PC?

You can, but Alderon says self-hosting requires a dedicated Windows or Linux machine, and that advice is sensible. The PC client already asks for 16 GB minimum and 32 GB recommended on PC, so the game and server can compete for the same memory and CPU time. It is workable for light use, but not the best base for a public crossplay community.

What ports does a Path of Titans server use?

The default game port is 7777 over UDP. Alderon also reserves 7778, uses 7779 for RCON, 7780 for stats and 7781 for Source Query when enabled. If the server is not appearing properly, check the whole 7777-7781 range rather than only the main game port.

More Path of Titans server guides

Compare hosts for your herd, or read up on server hardware.