We have designed the icons and settings in MuBots to be as simple and user-friendly as possible. In this guide, we will walk you through all the available bot and farm settings, ensuring you can easily navigate and customize MuBots to suit your needs.

Bot Settings:

In this section, we will walk you through all the bot settings. For your convenience, we have numbered the settings in the picture below, allowing you to visually follow along as we explain each option.

Sessions: This setting represents the number of emulator instances that MuBots will run simultaneously. By default, it is set to 1, but you can adjust it based on your system's capabilities or the total number of farms you are managing.

As a general recommendation, we suggest running 1 session per 10 accounts to ensure optimal performance and stability. However, you can increase or decrease this value depending on your hardware and needs.
Emulator Load Time: This setting defines the number of seconds the bot should wait after loading the emulator. By default, it is set to 60 seconds, but you can adjust it to be shorter or longer based on your requirements.

For example, if your emulator loads quickly, you can lower the value to save time. Conversely, if your system takes longer to initialize the emulator, increasing this value can help ensure smooth operation.

If you are unsure about the optimal value, it’s best to leave it at the default setting.
Game Load Time: This setting specifies how long the bot should wait after loading the game. By default, it is set to 60 seconds, but you can adjust it based on your system's performance.

MuBots has a built-in mechanism to automatically extend the wait time if it detects a loading screen, ensuring the game loads completely. However, it’s generally recommended to set this value based on how quickly your system loads the game.

If you are unsure about the optimal value, it’s best to leave it at the default setting.
Run Strategy: This setting offers two options for processing farms:
1. Line-wise (Execution Order):
  Farms are processed sequentially, following the order set in the Execution Order.
2. Timeout-wise:
  You can specify a timeout for each farm, such as making Farm 1 run every 2 hours. The bot will schedule the farm to run as soon as a session becomes available after the specified timeout period.
This flexibility allows you to optimize the farm processing based on your specific requirements and system capabilities.
Break After One Cycle: This setting allows you to define the break time, in minutes, that the bot should take after completing one full cycle. A cycle refers to the bot processing all your farms once.

For example, if you set the break time to 30 minutes, the bot will pause for 30 minutes after finishing a full cycle before starting the next one. Adjust this setting based on your needs to ensure efficient and controlled operation.
Force Kill Hanged Emulator: In certain systems or environments, emulators may occasionally get stuck during operation. This setting ensures that the emulator is forcibly stopped when it becomes unresponsive.

This option is generally not needed but can be helpful if you notice that your MEmu instances frequently get stuck on loading. While enabling this setting carries a slight risk of damaging the stuck emulator instance, you can mitigate this risk by backing up your farms.

To learn more about creating backups, click here. Backups ensure you can restore your instances if needed.
Auto Run on Startup: This option enables the bot to automatically log in and start running as soon as it is launched. With this feature, you won’t need to manually click the Run button.
Max Farm Timeout: This setting allows you to define a maximum timeout for each farm. By default, it is set to 40 minutes. If a farm takes longer than the specified time to complete its tasks, the bot will skip any remaining tasks for that farm and close the account. This ensures that all accounts receive a fair amount of time to run, preventing any one farm from monopolizing the bot’s resources.

Farm Settings:

In this section, we will walk you through all the farm settings. For your convenience, we have numbered the settings in the picture below, allowing you to visually follow along as we explain each option.

Enable Farm Switch: You can toggle this switch to enable or disable a farm account. In the picture, the switch is currently off, meaning the farm will not be processed by the bot. To enable the farm, simply click the switch once, and it will be activated. This allows you to control which farms the bot will process at any given time.
Farm Settings Icon: To open the farm settings, click on the settings icon. In the example shown in the picture, clicking the settings icon highlighted will open the settings for Farm 1. This allows you to customize and adjust the specific settings for each farm as needed.
Rename Farm Icon: This icon can be clicked to rename the farm within the bot, making it easier to identify which farm you are configuring. A useful practice is to rename the farms to the email linked to your farm or use your in-game account name. This helps keep your farms organized and easily recognizable within the farm settings.
Batch Settings: Configuring farms individually can be time-consuming, but batch settings simplify this process. Batch settings work the same as farm settings, with the difference being that when you click Save, a pop-up will appear where you can select which farms you want to apply the settings to. This way, you can apply the changes to multiple farms at once, saving you from the need to configure each farm individually.
Edit Settings: This setting opens the farm settings but only updates the specific settings you toggle. The other settings will remain unaffected. For example, if you want Emu ID: 1, 4, 5, 6, 7 to stop performing daily tasks while keeping all their other settings intact, you can follow these steps:
1. Click Edit Settings and disable the daily task option.
2. When you click Save, a pop-up will appear allowing you to select the specific Emu IDs (1, 4, 5, 6, 7).
3. After selecting the Emu IDs, only the daily tasks will be disabled for those instances. All other settings will remain unchanged for each of them.
This allows for targeted adjustments without affecting other configurations.