GambleBot - AceOnline lab bruteforce-gambling

This program can use the laboratory in AceOnline like games and put specified fixes on your items. It is especially useful on private servers, where gamble-cards are free, but certain fixes really rare and require a huge amount of tries.

Features

• Auto-gamble weapons and armor
• Specify a list of acceptable pre- & suffixes
• Automatically build the next weapon once one if finished, useful if you need many for Legend-upgrade
• Resources (fixes, items to use) customizable by you (image files)
• Break the loop by hitting "ESC" (also closes lab)
• Randomized delays to make detection harder

Build

$ mvn clean compile assembly:single

Download

Check the Releases section for compiled versions.

Usage

• Put your desired pre- & suffixes in config.txt
• Copy or link the gambles, resets, enchant.png and identifier item you are using
• Copy or link the fixes you specified
• Set up your ingame inventory
• All files are loaded relative to your current working directory. For convenience, you should make sure that is where the JAR is located by "cding" there before starting.

$ cd /path/to/GambleBotDir/
$ java -jar GambleBot.jar

• Run the program (cmd) as admin if the Robot (mouse movement) doesn't work

• You may override lastItemPos (see below) by passing an CLI argument. This can be easier that adjusting the config file for every inventory change.

• It's best to run the game in borderless window mode. Fullscreen does not work.

• Make sure you have the correct/normal font(-size) ingame (Windows text scaling setting)

A user-made guide by "Silence/unforgivn": Guide_for_DrDelay_GambleBot_0.02.pdf

Config

You can create a file config.properties with these values:

• factordelay: MS to wait between the two factor button clicks - default: 400
• showdelay: MS to hover the weapon between gamble attempts - default: 1250
• numberW: It's possible to auto-gamble a bunch of items at once - default: 1
• lastItemPos: How much items / position of gamble-item in inventory - default: 56
• atumClientVersion: To calculate Factory-Button positions. Different for: ep3 or ep4 or DA - default: ep4

The file config.txt is the list of wanted fixes. The format is:

prefix1.png
prefix2.png
-
suffix1.png

Each fix on a line, a line with only a dash separates prefixes from suffixes. You may use a format like the following to only gamble suffix:

-
suffix1.png

Working Directory

Example structure of necessary files:

$ ls -1
Agareth.png // Fix
Aloken.png // Fix
Bandit.png // Fix
config.properties // Config
config.txt // Fix-Config
Demon.png // Fix
enchant.png // Item-Name Identifier (Enchant String or clean Woo/Arrow/... image)
GambleBot.jar // The compiled JAR
Greave.png // Fix
prefixGmbl.png
prefixReset.png
searcheye.png // Identifier item (Top-Left of your inventory). Even if it's a TownPortal, name it "searcheye.png"
Stein.png // Fix
suffixGmbl.png
suffixReset.png
Warrior.png // Fix

Inventory

• 1: Identifier
• Last slots: Weapons to gamble (Index numbers in this example: 54-56, you'd put lastItemPos=56 and numberW=3
• It does not matter where the gambles and resets are, as long you linked/copied the correct images
• There can be more items in your inventory than 60, it only matters what you see when fully scrolled down. Sometimes, if the last row is filled completely, a new line will appear and disappear based on whether the item is currently in lab; this can cause issues, so you should avoid filling the last line up completely.
• The items to gamble must not have only 1 fix and must at least be Enchant-1

Resources

Fixes and positions are scanned by comparing pixel-wise against the provided image files. Even the slightest difference in color matters. This means, on certain servers you may have to create your own files. Black (#000000) pixels are ignored, so fill up anything but the text with.

Credits

• All Contributors

License

The MIT License (MIT). Please see the License File for more information.