Admins and bans · Tower Unite

Tower Unite Ports & Protocols

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.