Adding Devices to OriginsBot
Learn how to connect your BlueStacks instances to OriginsBot for automation
Video Tutorial
Video Tutorial: Adding Devices
(Video will be added soon)
Video Overview: This tutorial walks you through the complete process of adding BlueStacks instances to OriginsBot, from opening the device manager to verifying the connection.
Before You Begin
Prerequisites:
- BlueStacks Air is installed and configured (see BlueStacks setup guide)
- Android Debug Bridge (ADB) is enabled in BlueStacks settings
- Age of Origins is installed and logged in on each BlueStacks instance
- Each game account is at the main city screen (not in tutorial or loading)
- OriginsBot is installed and running
Step-by-Step Instructions
Launch OriginsBot and Navigate to Device Manager
Open OriginsBot and click the "Device Management" button located in the toolbar at the top of the window.
Ensure BlueStacks Instance is Running
Make sure your BlueStacks instance is running. It is not critical that the game be running at this point, but it will be beneficial in future steps.
Tip: Check that your BlueStacks instances are named clearly in the BlueStacks Multi-Instance Manager to easily identify them later.
Click "Scan for Devices"
Click the "Scan for Devices" button. This will typically take less than 5 seconds. Once the loading symbol has disappeared, click "Add Device". There should now be a prepopulated list of devices found.
Note: If no devices appear, make sure BlueStacks is fully booted and that ADB is enabled in BlueStacks Settings → Advanced.
Select 'Use' to Prepopulate Fields
In the "Discovered Devices" list, click "Use" next to the device you want to add. This will prepopulate the required fields:
- Display Name: Anything you like. Defaults to "BlueStacks (Port number)"
- ADB Identifier: Critical this is correct (e.g., 127.0.0.1:5555)
Important: If you are unsure which instance corresponds to which port number, check in the BlueStacks Settings → Advanced → ADB Bridge.
Configure BlueStacks Instance Name
To enable AppleScript automation for the auto-relaunch feature, the device must be associated with its corresponding BlueStacks instance name. Navigate to the "BlueStacks Instance Names" section and enter the instance name that matches your BlueStacks configuration.
Important: The instance name must match exactly as it appears in the BlueStacks Multi-Instance Manager. This field is case-sensitive and any discrepancy will prevent the auto-relaunch functionality from operating correctly.
Associate Instance and Configure Auto-Relaunch
Complete the device configuration by associating it with the BlueStacks instance defined in the previous step. In the "Connected Devices" section, locate the "Instance" dropdown menu and select the corresponding instance name.
- Select the appropriate instance from the dropdown menu
- Enable Auto-Relaunch if you wish to allow OriginsBot to automatically restart BlueStacks instances (Pro tier feature)
Note: The Auto-Relaunch feature is available exclusively to Pro tier subscribers and enables OriginsBot to manage BlueStacks instances automatically based on task schedules.
Verify Device Connection
Press ESC to exit the Device Management view, and confirm your device is showing on the main screen with "Connected" visible and a green status indicator.
Success! Your device is now connected and ready to run automation tasks.
Repeat for Additional Devices
If you have multiple BlueStacks instances, repeat the process for each one. You can add unlimited devices with a paid subscription. Each device can run independently with its own tasks.
Common Issues & Solutions
Device Not Found
If OriginsBot can't find your BlueStacks instance:
- • Make sure ADB is enabled in BlueStacks Settings → Advanced
- • Restart BlueStacks and try scanning again
- • Ensure BlueStacks is fully booted (wait 30 seconds after startup)
- • Check that no firewall is blocking ADB connections
Connection Failed
If the connection fails during verification:
- • Verify Age of Origins is running and at the main city screen
- • Check that your display settings match the recommended 540x960 resolution
- • Restart both BlueStacks and OriginsBot
- • Try disconnecting and reconnecting the device
Device Shows as Offline
If a previously connected device shows as offline:
- • The BlueStacks instance may have been closed - restart it
- • Age of Origins may have closed - reopen the game
- • Click the "Reconnect" button in the Device Manager
- • Remove and re-add the device if reconnection fails
Wrong Screen Resolution Detected
If OriginsBot reports incorrect resolution:
- • Open BlueStacks Settings → Display
- • Set resolution to Portrait 540x960 with 240 DPI
- • Save changes and restart BlueStacks
- • Remove and re-add the device in OriginsBot
Tips & Best Practices
Use Descriptive Names
Name devices based on their purpose or account type to quickly identify them when managing tasks.
Connect One at a Time
For better reliability, add devices one at a time rather than trying to connect multiple simultaneously.
Wait for Full Boot
Give BlueStacks at least 30 seconds to fully boot before attempting to connect it to OriginsBot.
Test After Adding
Create a simple test task (like collecting resources) to verify the device is working correctly.
Devices Connected Successfully!
Now that your devices are connected, you're ready to create automation tasks and start farming resources 24/7.