G GameCraft Hub
Dedicated condo

Tower Unite workshop

Amusement park social party · Social / Party / Minigames

Player tools indexed: 5 Admin consoles: 7

Tower Unite server quick reference: this dedicated server hosts a Condo, not a game mode. The official wording is that a Dedicated Condo lets you host your own or a community condo without keeping the game running, and other players can use their own inventory and contribute to the condo. The condo data has to be exported from the game first: in the condo scoreboard choose Saves then Export Condo, which produces a .map file under Tower Unite/Workshop/Condo Exports, or you can rename a CondoData file from your Steam Cloud folder to add the .map extension. Then copy it into the server Tower/Condos folder, creating one folder per condo, and the file name must match the condo map you load, so the full path looks like Tower/Condos/C_Condo/C_Condo.map. The official list has 12 condo maps, and note that Suite is C_lobbyOne while Resort is C_Lobby1 - the casing differs and Linux file systems are case sensitive, so a wrong case silently loads no condo data. For ports the official table gives two ranges: 27015-27050 TCP/UDP for Steam connection ports and 7777-7778 UDP for Unreal server connection ports, and without them players cannot join your condo. The actual defaults are game port 7777 (the official wording is that -Port changes the port from the default 7777, so 7778 is only the override example and the top of the range) and query port 27016 rather than 27015, because 27015 is used by your own Steam client on the same machine; the official page says that without 27016 you will not be able to play Tower Unite on the same machine as the dedicated condo. To appear on the Condo server list you need two tokens: a Steam Login Token requested at steamcommunity.com/dev/managegameservers using 394690 as the App ID (the base game, not the dedicated server 439660), and a Tower Login Token from moderation.towerunite.com; the official page stresses both are required. The tokens are essentially your server password, so click Regenerate to revoke them if they leak. Without tokens the server still starts, it just is not listed and can only be joined directly. Settings live in TowerServer.ini under a platform subfolder (Tower/Saved/Config/WindowsServer/ on Windows, LinuxServer/ on Linux), and if the file does not exist you have to create it; on Linux both tokens go into that ini, on Windows into the official TowerServerGUI.exe launcher. There is no RCON at all: AMP sets AdminMethod to STDIO and AdminPortRef to 0 and neither official page mentions a remote admin port, so administration is one AdminSteamID line per admin in the ini plus per-player permissions in the in-game scoreboard. The dedicated server appid 439660 runs natively on Windows and Linux with no Wine, needs at least 4.0 GB of disk space, and was only tested on Ubuntu and Debian; on Linux you must also copy linux64/steamclient.so into Tower/Binaries/Linux, a step the official guide calls very important. The official documentation is the three-page dedicated section under towerunite.com/guides.

Player tools (5)

Instant interactive calculations and recipe planners

Connection triage

Four branches: not listed, direct connect fails, empty condo, query tools find nothing

#four branches#why the condo is empty
Open tool →

The two login tokens

The Steam GSLT uses base appid 394690, and a Tower Login Token is also needed

#the GSLT uses the base appid#Regenerate after a leak
Open tool →

Server admin and config generation (7)

Config files, startup scripts and command wizards for running a server

Capacity budget

MaxPlayers has an official closed range of 2 to 64; blank memory means not counted

#the official 2 to 64 range#blank means not counted
Generate config →

Port matrix

Two official ranges alongside two default single ports, zero RCON, and no official step

#ranges beside single values#the step is unofficial
Generate config →

Tower Unite Ports & Protocols

Port Protocol Purpose
7777 UDP The game port, default 7777; 7778 is only the official override example and the top of the range, not a default
27016 TCP/UDP The Steam query port; the official page requires 27016 rather than 27015 because 27015 is used by the Steam client on the same machine, and using it means you cannot play Tower Unite on that machine

Tower Unite Dedicated Server Install (SteamCMD)

SteamCMD appid 439660

sudo useradd -m -s /bin/bash steam
sudo apt update && sudo apt install -y steamcmd lib32gcc-s1
sudo -u steam -i \
  /usr/games/steamcmd +force_install_dir /opt/gameserver \
  +login anonymous +app_update 439660 validate +quit

https://towerunite.com/guides/condo_dedicated.html

Tower Unite Config file paths

  • Tower/Saved/Config/WindowsServer/TowerServer.ini
  • Tower/Saved/Config/LinuxServer/TowerServer.ini
  • Tower/Saved/Config/WindowsServer/TowerBans.ini
  • Tower/Binaries/Win64/CustomTowerServer.ini
  • Tower/Condos/<MapName>/<MapName>.map
  • Tower/TowerServer_Chat.txt

Server notes

This dedicated server has a different shape from every other game: it hosts your own Condo rather than a game mode, so the content has to be exported from the game as a .map and placed at Tower/Condos/<map name>/<map name>.map. The file name must match the map name, Suite is C_lobbyOne while Resort is C_Lobby1, and on Linux a wrong case silently loads no condo data. For ports the official table gives two ranges: 27015-27050 TCP/UDP for Steam connection ports and 7777-7778 UDP for Unreal server connection ports, and the official page says players cannot join your condo without them; the actual defaults are game port 7777 and query port 27016. Remember the query port: the official wording is that -QueryPort=27016 is required to be 27016 because 27015 is used by your own Steam client on the same machine, and without 27016 you cannot play Tower Unite on that machine; another passage recommends not using 27015 at all. So this game does not offset every port by one - the default game port really is 7777. Appearing on the Condo server list needs two tokens and the official page stresses both are required: a Steam Login Token from steamcommunity.com/dev/managegameservers with 394690 as the App ID (the base game, not the dedicated server 439660), and a Tower Login Token from moderation.towerunite.com/manage_game_servers.php. The official page calls the tokens essentially your server password, forbids sharing them, and says to click Regenerate immediately after a leak; on Windows they go into the official TowerServerGUI.exe launcher, on Linux into TowerServer.ini. Without tokens the server still starts, it is simply not listed and can only be joined directly. The config file is Tower/Saved/Config/WindowsServer/TowerServer.ini or LinuxServer/TowerServer.ini and the official page says you must create it if it does not exist; it has three sections and eight keys, where MaxPlayers has an official closed range of 2 to 64 with a default of 32, CondoAutoSave and CondoBackupsEnabled take True/False rather than 1/0, CondoFile is a commented line in the official example (an optional override), and AdminSteamID is a repeated key with one admin per line. There is no RCON at all: AMP sets AdminMethod to STDIO and AdminPortRef to 0, and neither official page mentions a remote admin port. Admins come from AdminSteamID in the ini (the official page stresses you must add your own Steam ID first), and after that you adjust per-player rights in the in-game scoreboard under Settings then Player Permissions, which the official page says is automatically saved to a file without naming it. Bans can be done in the scoreboard or by writing SteamIDs into TowerBans.ini (create it if absent; the format is one SteamID=<id>,0 line under a [Bans] section, and the official page does not explain the trailing 0). Dedicated condos also connect to PixelTail own moderation API. Chat and permission changes are logged to Tower/TowerServer_Chat.txt with a timestamp, the player name at the time, the SteamID and the message or action. The dedicated server appid 439660 runs natively on Windows and Linux with no Wine and needs at least 4.0 GB of disk; the official guide tested only Ubuntu and Debian, and on Linux you must copy linux64/steamclient.so into Tower/Binaries/Linux (a step the guide calls very important, while AMP solves the same problem with LD_LIBRARY_PATH). Multiple instances can use -TowerServerINI=CustomTowerServer.ini, but note that file loads from Tower/Binaries/Win64/, a different folder from the default ini, and the official pages publish no port step for instances. In the launch parameters -nosteamclient is required (official wording: required to run the server without Steam, and required when the game client runs on the same machine). Two content rules to finish: Workshop collision is currently incompatible with dedicated condos and the guide advises blocking volumes around such items, and hosting mature content requires the keyword 18+ in the condo title or, per the official page, your condo will be delisted. On querying: node-gamedig has no entry for this game as of this round, so third-party query tools built on it may find nothing, which says nothing about server health.

FAQ

Which Tower Unite tools can I use online?
We list 5 tools for Tower Unite: Joining a dedicated condo, Connection triage, Hardware and resources, Loading condo data, The two login tokens. All of them run straight in your browser.
Do these tools cost anything or need installing?
No. Everything runs in the page: no install, no sign-up, no cost. Enter your values and the result appears instantly, and you can copy the generated configs and commands with one click.