The game runs on your Android phone or emulator. TowerLoop runs on your Windows PC. Connect the two, activate your trial or paid access, and choose what to automate.
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 7-day free trial on either plan through Paddle checkout. Open License in TowerLoop and activate the supplied key. If you already have a subscription, use your existing key. The desktop client stores the raw key outside webview-accessible data and shows only license status fields afterward.
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 time ADB runs, Windows Firewall usually asks for permission; choose Allow so TowerLoop can reach your device.
Open Controls and start the viewer. Confirm that the selected game appears and that a click reaches the correct place. TowerLoop adapts recognition to the observed screen size; test your own layout before leaving automation running.
Start a run in The Tower. Enable Static Gem or Moving Gem under Automations, then select Start Engine. Watch a collection and its activity entry before adding more helpers. Stop automation before changing devices or connection settings.
Use these checks before contacting support. They match the current desktop app behavior and release scope.
Start the emulator, enable its ADB/debugging option, and refresh devices in Settings. Select the intended instance. A USB phone must authorize the computer for debugging.
Accept the device authorization prompt, toggle the emulator ADB setting, or restart the emulator. Offline devices usually need a reconnect before screen checks pass.
Check the license key and your internet connection, then try again. Settings and support remain usable even when automation is locked.
Run Device Status and Screen Info, then retry the viewer. Screen capture failures usually point to a disconnected device or the emulator's ADB setting.