-
-
Notifications
You must be signed in to change notification settings - Fork 32
Home
Please take a couple of minutes to review all the required steps before you perform them.
These are the reccomended settings for the majority of the users
-
Be sure to download and install all the required software
- Chromium v69 (For other platforms search this link for build number 576753)
- Adobe Flash
-
Create a folder in which you want to run BHBot, for this tutorial we are going to use
C:\BHBot
. You can choose whatever folder you like. If you are running on Windows, do not extract the bot the in Downloads folder. -
Download the latest version of the bot. Pay attention to get the latest zip package form the Release page.
-
Unpack the zip file in the directory you created before
C:\BHBot
and double check you got all the required files- BHBot.exe
- BHBot.jar
- chromedriver.exe
- java-runtime (folder)
-
Run the
BHBot.exe
executable. You should now have two windows:- a console window where the bot is logging what is happening
- a Chromium web browser window with Bit Heroes on Kongregate.
-
If you run BHBot in the past (previous versions) everything should be ok and you skip the remaining steps
-
The bot should open the game and enter an idle state: on the first run of the bot you will need to allow Flash, download and setup the flash installer for Chromium and log in to your account.
-
From Bit Heroes settings, apply the following configurations
- Disable Auto Pilot on Death (this is required if you want to use the Auto Revive feature)
- Disable all notifications (they block the bot from reading resource values).
- Disable World Boss Requests
- Enable Auto Pilot
- Enable Auto Enrage (optional)
- Enable Reduced Effects
- Disable Battle Text
- Disable Overlay Status Bar
- Disable Aniations
- Decline merchants
- Decline Treasures
-
Finally in the bot console issue a
stop
command so that the bot will close. -
As it was the first time you run BHBot, a standard
settings.ini
file has been created. Review it and adjust it based on your preferences. Make sure to take your time to perform this step carefully as what you set insettings.ini
is crucial to run the bot. -
Once everything is configured run
BHBot.exe
again and the bot will start running with the settings you applied. If the game window is obtrusive you can use thehide
command in console to run it in the background.
Only use these steps if you know what you're are doing. Please also note that, as this procedure is intended for skilled people, the level of details will be high and no support will be provided (unless bugs are present).
-
BHBot requires the Java 11 run time to run correctly. Together with the standard executable version of BHBot you can find a modularized version of the Java run-time that only contains the required libraries. You can find this in the
java-runtime
folder of the distro. If you do not want to use it, get the Java 11 distro of your choice. Our recommendation is fore the AdoptJDK one. -
You can get the
BHBot.jar
file from the standard zip package in the release page of BHBot. -
Make sure that no
settings.ini
is present in your folder and runjava -jar BHBot.jar
(make sure to point to the right java path). You should now have two windows:- a console window where the bot is logging what is happening
- a Chromium web browser window with Bit Heroes on Kongregate.
-
Follow from step #6 of the standard process and when asked to restart, run once again
java -jar BHBot.jar
Releases are generally for milestone versions, to get the latest functionality you can clone the project and compile your own BHBot.jar.
BHBot is using Maven to manage dependencies and can be compiled with your IDE of choice. We recommend using IntelliJ as the community edition has built-in support for Maven.
Be aware that while these versions may contain the latest features they are also certainly development builds and will contain their fair share of bugs.
This is usually caused by having a resolution above 1920x1200, or DPI scaling above 100%.
Note that due to Flash this can be quite resource intensive. Due to the slow nature of energy regeneration if you wish to run multiple accounts on Windows it is more effective to use a Windows cron-like service (E.G Z-Cron) to stagger running and stopping multiple accounts, generally you only need to run the bot for 40 minutes to use 8 hours of shards/energy/tokens/tickets regeneration (A little more if there is an event/rare familiar persuading/autoshrine/rune/revive being used.)
To do this you can use one task in z-cron to start the bots batch file, and another batch file with
taskkill /f /im "chrome.exe"
taskkill /f /im "java.exe"
scheduled to stop the bot.
(Note that Z-cron will need to be ran as admin to reliably kill chrome/java).