Tower Unite workshop

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.