TowerLoop uses standard local input automation through the user's configured environment. You remain responsible for configuring your own device or emulator and for ensuring your use complies with applicable software and game rules.
Download the Windows installer, run it, and open TowerLoop from the Start menu or desktop shortcut. TowerLoop is distributed directly by Lemma 151 LLC as desktop software.
Start the emulator or Android device you want to use before running checks in TowerLoop. The user remains responsible for providing and configuring their own game installation, device, or emulator.
TowerLoop uses standard local ADB input automation for detection, screen information, taps, swipes, key events, and launch controls through the user's configured environment. Most users should only need to enable the emulator's ADB or Android debugging option.
The first release targets 1080x1920 portrait. Unsupported resolutions should be corrected before automation starts so template matching and screen controls line up.
Open the License screen in TowerLoop and paste the key from the purchase email. The desktop client stores the raw key outside webview-accessible data and shows only license status fields afterward.
Launch your supported local session, choose the automation profile you want, and start TowerLoop. Stop automation before changing emulator settings, switching devices, or taking manual control for long stretches.
Use these checks before contacting support. They match the current desktop app behavior and release scope.
Start the emulator first, then run Device Status again. If multiple targets are connected, close extras so TowerLoop can use one clear device.
Accept the device authorization prompt, toggle the emulator ADB setting, or restart the emulator. Offline devices usually need a reconnect before screen checks pass.
Set the emulator display to 1080x1920 portrait and restart the local session. Version 1 intentionally rejects unsupported resolutions instead of guessing.
Check the license key, network access, and backend URL configured in the desktop app. Settings and support remain usable even when automation is locked.
If the license state is in grace, local automation can continue until the offline grace deadline shown in the License screen. Reconnect and refresh before that deadline.
Run Device Status and Screen Info, then retry the viewer. Screen capture failures usually point to a disconnected device, unsupported display, or emulator ADB setting.