BlueStacks
Treat BlueStacks as a discoverable Windows emulator target. Enable Android Debug Bridge in settings, then use TowerLoop's device checks instead of relying on a fixed port.
TowerLoop treats Windows emulators as discoverable local ADB targets. Keep the setup simple: one active target, ADB enabled, and a 1080x1920 portrait screen.
Treat BlueStacks as a discoverable Windows emulator target. Enable Android Debug Bridge in settings, then use TowerLoop's device checks instead of relying on a fixed port.
Start the instance before TowerLoop checks run. If the device appears offline, restart ADB from the emulator or close duplicate instances.
Use one running instance for v1 and keep the display at 1080x1920 portrait. Re-run package detection after installing or updating the compatible game.
Enable the emulator's ADB/debugging option and avoid running another Android target at the same time. Use the screen check before starting automation.
A cable-connected device can work when USB debugging is authorized, but the Windows-first release is optimized around emulator-style setup and 1080x1920 portrait.
Advanced setups can fall back to a manual ADB address when discovery is not enough. Keep that to one target at a time until multi-device support exists.