19 August 2018 Tagged: eulorac++

Build 29

This release contains further mining reliability fixes.

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: multiple mining outputs in the same quality band are mis-stacked

  • FIXED: ordinary claims are skipped because the key description is parsed improperly

  • FIXED: claim marker text is parsed to include extraneous spaces

  • FIXED: craft-table is sometimes tested at the wrong time

  • FIXED: lag can cause old recipe to be used with current claim

    • Now the recipe is fully initialized between rounds, for reelz this time

  • FIXED: bot will leave mining output behind if /takeall doesn’t return promply

Daniel P. Barron - 2018-08-31 19:31:35

Been using this for a few days. Works great!

Add a Comment