28 July 2018 Tagged: eulorac++

Build 28

This release contains mining reliability fixes.

UPDATED Links now point to build 28.1 which adds the following three changes:

  1. FIXED: bot crashes client when table gets full

  2. ADDED: handling for "not successful" message from /explore

  3. ADDED: bot will now stop if loot drops on the ground

UPDATED 2 Links now point to build 28.2 which additionally fixes a key parsing defect which can cause bot to dance away from table and across map in search of non existing claim marker.

Feedback is welcome, please use #eulora.


You have to have your craft-table in inventory. It’s not smart enough to look on the ground for one. If you leave it on the ground it will proceed as if you have no table, potentially leaving your table behind.

If you have mining enumerations inside a container in your inventory while bot mining and any new enumerations auto-stack into the container, the bot isn’t smart enough to look there.

The bot isn’t smart enough to figure out if a table on the ground is yours or not. Avoid bot mining near other craft-tables on the ground as the bot is likely to get confused and halt when transfer to wrong table fails. This applies to the public craft-table as well.

I suggest you use an explore timeout of at least 30000 for reliability.

For reference the command is as follows:

/bot explore nTimes moveStrategy strategySize leaveKeys useMaxMaterials maxDelay exploreTimeout qualityBand

For example:

/bot explore 200 line 100 1 M 8000 30000 100

Which gives you a qualityBand of 100. If you do not set a quality band, a default quality band of 1 will be used which permits stacking only of identical qualities.


  • FIXED: mining outputs from a single dig requiring 2 or more new table slots are wrongly stacked into the same slot causing unexpected stacking and or bot stoppage if the items can’t be stacked together.

  • FIXED: bot breaks when mining is started with an empty table.

  • FIXED: "You were unsuccessful since you moved" while exploring.

    • The bot now tries really hard to hold still, and immediately forces client compliance with server position messages.

  • FIXED: if the bot gets "You were not successful since you moved" while building a claim it doesn’t retry.

  • FIXED: if the enumeration doesn’t land in inventory in a timely fashion following the explore success message, the bot gets confused and builds using the most recent recipe.

  • FIXED: bot stops if lacking ingredients to build claims higher than tiny and small.

    • Now the bot will stop when unable to build a small or tiny but will lock other types and move on.

  • FIXED: bot gets stuck waiting if the nearby claim markers are so dense that the new marker doesn’t appear.

    • The bot will now dance around the new claim marker’s position to elicit its details from the server.

Add a Comment