Your Path of Titans server says running in the panel, you've searched the in-game community list for its name three times, and it isn't there. That's the auth token, almost every time: it's comfortably the thing we field most tickets about on this game. Path of Titans is unusual among the games we host in that the server won't register with Alderon at all until you hand it a token from your own Alderon Games account, and a green "running" status tells you nothing about whether that handshake succeeded.

So that's where this starts. What follows is the whole first hour on a new Path of Titans server: the token, picking a map, getting yourself and your players connected, promoting yourself to admin, and where the config files actually live. If you're moving an existing community server across from somewhere else, do the token first, then read Path of Titans Save Location & How to Upload Your World for the file-shuffling half of the job.

Start with the Alderon auth token

Go to https://alderongames.com/oauth/hosting-token and sign in with an Alderon Games account that owns the game. Whichever account you use becomes the auth host account behind the server, so pick one you actually control and keep it secure. Not the spare you made to test something in 2023. If your community is going to outlive your interest in running it, I'd use an account that can be handed on.

Generate the token, then copy it straight away. It's a JSON Web Token, so it's a long, ugly string of characters, and the page won't show you that same token a second time once you refresh or leave. There's no "view my token" screen to come back to, which surprises people.

Here's the part that bites people. Generating a new token revokes every previous token on that account. If you're already running Path of Titans somewhere else under the same account, minting a fresh one for your LOW.MS server will quietly kill the old server's authentication at the same time. Reuse the token you already have if you can find it, or accept that you'll be updating both servers in the same sitting.

Now put it in the panel. Log into the LOW.MS Control Panel, open your Path of Titans service, and go to Service Settings. There's an Auth Token field there, and it's a required one: it's the same field the panel prompts you for when the service is first created, so if you pasted the token during setup it'll already be sat there. Paste it in, save, and restart the server.

Behind the scenes we rebuild the server's launch script every single time it starts, writing your current token into it as the AG_AUTH_TOKEN environment variable before the server binary is launched. Alderon added that environment variable specifically because Windows caps command-line arguments at 1024 characters and the token is far too long to pass that way reliably. The practical upshot for you is a good one: changing the token in Service Settings and restarting is genuinely all there is to it. You never need to touch a startup file yourself, and you can't end up with a stale token baked into a script somewhere.

Map, branch and database

Three more Service Settings fields decide what your server actually is, and it's worth setting all three before anyone joins rather than after.

Map is a dropdown, and it offers Panjura, CeruleanIsland, Island and StoneclawHighlands. Island is Gondwa: the internal level name and the name players know it by are different, which is confusing exactly once. Panjura is the default and it's the right call for a first server.

There's a wrinkle here worth knowing about. Commandline Manager also carries a set of ready-made command lines, one per map, and those have the map name baked into them rather than reading it from the dropdown. So if you pick a predefined command line labelled Gondwa or Riparia, that's what you get regardless of what the Map dropdown says. Riparia is only available that way at the moment, it isn't in the dropdown at all. Pick one lever or the other and stick with it, and if the map you booted isn't the map you chose, that mismatch is the first thing I'd check.

Database is a two-option dropdown, Local or Remote, and it defaults to Local. Local keeps every player account and dinosaur on your own server as JSON files, which is what you want for a single server. Remote hands storage to Alderon and exists so that a cluster of servers can share character progression. I wouldn't switch an established server from one to the other on a whim: the character data doesn't follow you across, and your players will notice within about ten seconds.

Branch defaults to production and that's the live public build. There's a Branch Password field beside it for the occasions when Alderon runs a password-protected test branch. Leave both alone unless Alderon have specifically handed you a branch name and key.

One thing you won't find a setting for: player slots. That comes from your plan and it's already wired into the server's launch arguments, so there's nothing to configure.

Getting yourself and your players in

Launch Path of Titans, sign in, and find the community server list. Search for your server by the name you gave it in Service Settings: that name gets written into the server config for you, so whatever you typed in the panel is exactly what players are searching for. If you set a private password in there too, the game prompts for it when you click join.

Give a freshly started server a few minutes before you decide it's broken. It has to finish loading the map and complete its handshake with Alderon before it turns up in anyone's list, and the list itself isn't instant. We'd honestly rather you waited five minutes than opened a ticket at ninety seconds, because plenty of the "my server is missing" reports we get sort themselves out before we've finished reading them.

If it isn't listed but you're impatient, direct connect works: use your server's IP and its game port, both shown on the service page in the panel. The port layout is worth committing to memory because it's arithmetic, not a fixed set of numbers. Your query port is the game port plus one, and the RCON port is the game port plus two. Players only ever need the game port. On a server with the default allocation that's 7777 for the game, 7778 for queries and 7779 for RCON, but yours will differ if you're on a shared IP, so read them off the panel rather than assuming.

Making yourself an admin

Admin rights in Path of Titans key off your Alderon Games ID, the nine-digit number formatted as 123-456-789 on your Alderon account. Everybody you want to promote needs to give you theirs.

The good news is that the roles themselves are already built for you. Commands.ini on a LOW.MS server ships with four roles defined and ready to use:

Owner: everything, including restart, server mute and the whitelist commands
Admin: nearly everything the owner has, minus restart and the reload commands
Moderator: the day-to-day set: kick, ban, teleport, heal, godmode, announce
Creator: a light role for content creators, with teleport and announce but no moderation powers

Each one comes with its own chat colour and a reserved slot, so a full server won't lock your staff out. All you need to do is assign people to them. Open PathOfTitans\Saved\Config\WindowsServer\Commands.ini in File Manager, find the empty [PlayerRoles] section at the bottom of the file, and add a line per person:

[PlayerRoles]
123-456-789=Owner
987-654-321=Moderator

Save it and restart the server. Path of Titans only reads that file at startup, so a live edit does nothing until the process comes back around.

If you'd rather not restart, promote people from inside the game instead. Once you hold a role with the promote permission you can use /promote <player> <role> in chat, and /demote <player> to take it away again. I'd still write the important people into Commands.ini afterwards so that a fresh install doesn't lose them.

Where the rest of the config lives

Everything sits under PathOfTitans\Saved\ and you can reach all of it through File Manager. If you're pushing anything large, SFTP is on port 8822 and the credentials are on your service page.

Config\WindowsServer\Game.ini holds the server rules: day length, starting time of day, group size caps, fall damage, fishing, the water quality system and BattlEye. Server name and password are also in here, but they're written from your Service Settings values, so change those in the panel rather than typing them into the file.
Config\WindowsServer\GameUserSettings.ini is the mod list. There's no Mod Manager for Path of Titans because mods aren't Workshop items, they're mod.io packages. You add each one as an EnabledMods="UGC_M_XXXXXXXXXX_SK" line under [PathOfTitans.Mods], one line per mod, and the server downloads them itself on the next boot. Expect that first start to run long. Community maps are distributed the same way, so a modded map needs its ID in here as well as the right map selected. Get one of those two right and not the other and you'll boot to the wrong world.
MOTD.txt and Rules.txt are the message-of-the-day and rules panels players see in game. Both support the game's little markup tags, so <title>, <red> and <large> all work.
Bans.txt, Mutes.txt and Whitelist.txt take Alderon IDs, one per line. Bans and mutes accept an optional expiry and reason on the same line, colon separated, like 525-053-709:0:reason for admins:reason shown to the player. A 0 in the timestamp field means forever.

Web Console gives you a live view of the server log while it runs, which is where you'll see the map load and the Alderon handshake happen. It isn't a command prompt though: Path of Titans admin commands are chat commands, typed in game. For digging back through a session that already ended, Log Viewer is the better tool, and it's the one I reach for first when a server came up wrong overnight.

Before you start changing any of this, take a Cloud Backup. Path of Titans stores each player account and each dinosaur as its own JSON file, so a directory full of them is easy to damage and miserable to rebuild by hand. Cloud Restore will put you back in a couple of minutes, and it costs you nothing to have one sitting there.

If the server still won't show up

Work down this list before you open a ticket, because it'll usually be one of them:

Re-paste the auth token in Service Settings, save, and restart. If you generated a new token at any point, an older one may still be in there.
Check whether you generated a fresh token for a different server on the same Alderon account, which would have revoked this one.
Watch Web Console through a full startup and read what it says about authentication. A rejected token shows up there rather than as a failed start.
Try a direct connect on the game port. If you can get in that way, the server is fine and it's a listing problem, which is a different conversation.
If you've just added mods, take them out and start clean. A mod that fails to resolve on mod.io can hang the boot before the server ever registers.

If you're still stuck after that, open a ticket from the panel and tell us the map you're on, whether you're on Local or Remote database, when you last regenerated the token, and roughly what Web Console printed while it was starting. Support is 24/7 and that handful of details usually gets it solved on the first reply.

Getting Started With Your Path of Titans Server