BotLab Devlog

In this thread, I share what is on my mind concerning BotLab, discovering and developing bots, in chronological order. It helps me organize my thoughts and remember useful discoveries.

If you are interested in a more detailed history, you can find that at

If you see something that is missing here, something I should be aware of, don’t hesitate to message me or post on the forum in the ‘Show and Tell’ category.

1 Like

People mentioned they have problems getting hash values for files.
Being able to share and identify files is essential when working on bots, so I wrote this guide on how to do that, using hashes:

1 Like

This week brings improvements specific for EVE Online.
As some people had difficulties adapting the memory reading to their use cases, I improved the example code in the Sanderling repository:

It now better shows:

  • Which part of the intermediate results we reuse when reading the UI tree multiple times from the same EVE Online client process. (In the Sanderling app, we reuse the address of the root of the UI tree, because this address does not change. By reusing this part we save time so that subsequent readings of the complete UI tree can be completed in about 200 milliseconds.)
  • Where the transition is between the intermediate representation (partial python objects) of the memory measurement and the representation found in the bot developers API. Observations in the last three years showed this is an important boundary: When we adapted the memory reading to new client versions from CCP, we did that in the part that happens after reading the partial python objects.

You can find the guide on adapting EVE Online memory reading here in the Sanderling repository at ./guide/

As always, if you want to learn more about how the memory reading works in EVE Online, don’t hesitate to post your questions on the BotEngine forum.

1 Like

While helping @huihui to develop an Industry Index Scraping script, I found some things to improve in the Sanderling App.
I have updated to Sanderling App with a simpler mouse input API: There is a way to Mouse Click on Entry without clicking on info button - #37 by Viir

The next improvement planned there is to reduce the time to get feedback on experiments and to support easier exploration of the APIs. It looks like there will be a REPL which supports incrementally building up functionality which can be composed into bots. The same interface will also support quick inspection of results from memory reading.

1 Like

I published the first version of this tool today, along with a guide on how to use it at A Simpler Way to Make EVE Online Bots

1 Like

An update regarding EVE Online:
I merged an update of the memory reading based on an observation shared by Kaboonus:

This was to adapt to changed in-memory symbols of the missions info panel.
You can download the compiled binary of version 2019-04-05 from

I also updated this EVE Online bot development guide accordingly: A Simpler Way to Make EVE Online Bots


I recently worked more on the design to solve the issues of bot operation interrupted sporadically by script bugs which are hard to spot:

1 Like

As mentioned earlier, I am working on a new version of the EVE Online bot framework, to solve the issues with understanding bot code and bad surprises at runtime, and recording and inspection of bot operation.

This is a report on the recent progress with developing this framework:
I explored possible solutions using the example of a warp to 0km autopilot bot. Today I uploaded a rough draft of how this framework could be used. This draft concentrates on static parts, framework API and programming language. Other aspects are not presented in there. The programming language part is already well demonstrated as this draft contains said autopilot bot, I copied the bot code below:

module Main exposing (botStep)

{-| This is a warp to 0km auto-pilot, making your travels faster and thus safer by directly warping to gates/stations.
The bot follows the route set in the in-game autopilot and uses the context menu to initiate warp and dock commands.
To use the bot, set the in-game autopilot route before starting the bot.
Make sure you are undocked before starting the bot because the bot does not undock.

import SimplifiedSanderling
        ( BotEvent(..)
        , BotEventAtTime
        , BotRequest(..)
        , InfoPanelRouteRouteElementMarker
        , MemoryMeasurement
        , MouseButtonType(..)
        , centerFromRegion
        , mouseClickAtLocation

-- This implementation is modeled after the script from

{-| We need no state for the autopilot bot
type alias State =

init : ( State, List BotRequest )
init =
    ( initialState, [] )

initialState : State
initialState =

botStep : BotEventAtTime -> State -> ( State, List BotRequest )
botStep eventAtTime stateBefore =
    case eventAtTime.event of
        MemoryMeasurementCompleted memoryMeasurement ->
            ( initialState, botRequests ( eventAtTime.timeInMilliseconds, memoryMeasurement ) )

botRequests : ( Int, MemoryMeasurement ) -> List BotRequest
botRequests ( currentTimeInMilliseconds, memoryMeasurement ) =
    case memoryMeasurement |> infoPanelRouteFirstMarkerFromMemoryMeasurement of
        Nothing ->
            [ ReportStatus "I see no route in the info panel. I will start when a route is set."
            , TakeMemoryMeasurementAtTime (currentTimeInMilliseconds + 4000)

        Just infoPanelRouteFirstMarker ->
            case memoryMeasurement |> isShipWarpingOrJumping of
                Nothing ->
                    [ ReportStatus "I cannot see whether the ship is warping or jumping."
                    , TakeMemoryMeasurementAtTime (currentTimeInMilliseconds + 4000)

                Just True ->
                    [ ReportStatus "I see the ship is warping or jumping, so I wait."
                    , TakeMemoryMeasurementAtTime (currentTimeInMilliseconds + 4000)

                Just False ->
                        ++ [ TakeMemoryMeasurementAtTime (currentTimeInMilliseconds + 2000) ]

botRequestsWhenNotWaitingForShipManeuver : MemoryMeasurement -> InfoPanelRouteRouteElementMarker -> List BotRequest
botRequestsWhenNotWaitingForShipManeuver memoryMeasurement infoPanelRouteFirstMarker =
        announceAndEffectToOpenMenu =
            [ ReportStatus "I click on the route marker to open the menu."
            , mouseClickAtLocation
                (infoPanelRouteFirstMarker.uiElement.region |> centerFromRegion)
                |> Effect
    case memoryMeasurement.menus |> List.head of
        Nothing ->
            [ ReportStatus "No menu is open."
                ++ announceAndEffectToOpenMenu

        Just firstMenu ->
                maybeMenuEntryToClick =
                        |> List.filter
                            (\menuEntry ->
                                    textLowercase =
                                        menuEntry.text |> String.toLower
                                (textLowercase |> String.contains "dock")
                                    || (textLowercase |> String.contains "jump")
                        |> List.head
            case maybeMenuEntryToClick of
                Nothing ->
                    [ ReportStatus "A menu was open, but it did not contain a matching entry." ]
                        ++ announceAndEffectToOpenMenu

                Just menuEntryToClick ->
                    [ ReportStatus ("I click on the menu entry '" ++ menuEntryToClick.text ++ "' to start the next ship maneuver.")
                    , mouseClickAtLocation (menuEntryToClick.uiElement.region |> centerFromRegion) MouseButtonLeft |> Effect

infoPanelRouteFirstMarkerFromMemoryMeasurement : MemoryMeasurement -> Maybe InfoPanelRouteRouteElementMarker
infoPanelRouteFirstMarkerFromMemoryMeasurement =
        >> .routeElementMarker
        >> (List.sortBy (\routeMarker -> routeMarker.uiElement.region.left +
        >> Maybe.andThen List.head

isShipWarpingOrJumping : MemoryMeasurement -> Maybe Bool
isShipWarpingOrJumping =
        >> Maybe.andThen .indication
        >> Maybe.andThen .maneuverType
        >> (\maneuverType -> [ SimplifiedSanderling.Warp, SimplifiedSanderling.Jump ] |> List.member maneuverType)

Upload with all the details is on github:

1 Like

Today I worked on removing a bottleneck from EVE Online bot development. In the past, adapting the memory measurement parsing code required a developer to set up Visual Studio and use a .NET build. To remove this friction, the parsing code is moved into the bot scope, where it can be changed as easily as your own bot code.
The commit in the Sanderling repository adds an example of how to write the serialized memory measurements to files, so these can be easily imported when experimenting with changes to the parsing code:

After running this new derivation code on a process sample, you will find the files partial-python.json, sanderling-memory-measurement.json and sanderling-memory-measurement-parsed.json in a subdirectory named after the process.

I improved the names for the derivations to:

  • Avoid having two different kinds of ‘memory measurement’.
  • Clarify that the reduction happens from partial python to get the other versions.

The names of derivations are now:

  • partial-python
  • reduced-with-named-nodes
  • reduced-with-named-nodes-parsed-further


Design of the EVE Online bot framework continues:

I continued the design based on the draft from last week.

The linked commit adds the following parts:

  • Sample files containing derivations from EVE Online memory measurements, to use as a reference for automated testing of parsing code.
  • Example bot (Main.elm) to ensure fundamental functionality is covered in the first release.
  • Bot-side code for the interface of EVE Online bots to the hosting app (Sanderling_Interface_20190513.elm).
  • EVE Online specific functionality (Sanderling.elm). This also contains code to parse the contents of memory measurements from Sanderling.
  • Automated tests for the interface functions and memory measurement parsing functions.

With this version, the new framework is almost ready for the first release.

1 Like

Did some fine-tuning for the EVE Online bot framework today:

1 Like

The new EVE Online bot framework has landed! :tada:

Besides releasing the software to run EVE Online bots, I also uploaded this guide which explains how it works:bots/ at 56fd088fb5c7c52fe08ada90f75acc0f652e753c · Viir/bots · GitHub

Updated guide to fix a problem in the example of how to start a bot:

Thanks @Kaboonus for pointing out that problem!

Next step is writing guides on how to develop EVE Online bots.


Today I started the guide on developing EVE Online bots, describing how to set up the programming tools to efficiently work on EVE Online bots. You can find it here:

As questions come up, I will expand this.

1 Like

An update regarding EVE Online:

I published a new version of the bot framework and updated the download links in the guide accordingly:

With the new software, a generic interface between bot and host is introduced, which offers more flexibility in the functionality integrated into a bot.

One concrete example of how this flexible interface improves over the old Sanderling app: This allows coding custom logic to choose a windows process in case there are multiple instances of the game client process present.

Most developers won’t need to use this new interface directly but will use it indirectly over libraries encapsulating these low-level functionalities for easier use.

An example of such a library is the one for EVE Online, contained in the warp-to-0 auto pilot bot, in the file Sanderling.elm:

Recently there was a change in EVE Online which affected several users: After an update of the EVE Online client, some bots had issues undocking a ship from a station. @Aseratis and @Kaboonus fixed this problem as you can see in these posts:

Another update regarding EVE Online:

I released version 2019-05-29 of the bot framework and the botengine console. The new version brings several improvements:

  • To improve the readability of the bot code, cleaned up the interface between bot and host (engine).
  • Added the bot side interface to set a configuration for a bot.
  • Better support for identifying bots: The bot ID is now displayed in the user interface. Also, a change in the packaging of a bot from local files fixes nondeterministic bot IDs. (The problem where the bot ID would change without changes in the files. (This problem was caused by timestamps being added at the time of loading the bot)).

I also updated the guides to the new version of the software: bots/ at 32559530694cc0523f77b7ea27c530ecaecd7d2f · Viir/bots · GitHub

You can download this new version of the bot running app directly from

Recently some people reported problems with downloading bots to load them into the engine. Today’s release of the new BotEngine Console adds a new feature to address this problem. Instead of downloading the bot from Github manually, you can now let the BotEngine Console do this for you. To use this new feature, specify the Github URL with the --bot-source parameter. The engine will then take care of the download:

This bot source looks like a URL. I try to load the bot from Github
I found 8 files in ''.
I loaded bot 266EDDE2CCA2F71BC94DFD941F469E5F3DA20DACFD08A08E680B0C09646DF6C1.
Starting the bot....

I also updated the guide to explain the different kinds of bot sources and include examples:

You can download this new version of the Console from

Recently people reported issues slowing them down when using bots. This new release of the botengine console adds a feature to fix these bot configuration issues. The new feature allows you to:

  • Configure a bot using the command-line interface, by adding the new --bot-configuration parameter.
  • Configure a bot without changing the bot code, which in turn means without changing the bot ID. This means we can compare bots easier, by using the now more stable bot ID.

I updated the guide to illustrate how this new feature is used, including an example command line:

After the improvements on bot discovery and operation as reported in June, work continued on the bot development side in the last two weeks.

@TOBIAS95 had some questions, and while answering these I used the opportunity to write in more detail how the process of bot development works.
Some of the topics covered:

  • How do we describe what a bot should do, in a way that avoids misunderstandings between people?
  • How can I take and save the screenshots used to describe a bot?
  • How can I share the files I collected with other people?

I posted this guide here:

This week, I explored the bot implementation process further, based on the example screenshot given last week. This exploration answered several questions about developing bots:

  • How can we easily model example files to use in automated tests, for example when testing image file decoding implementations? The elm app implemented here displays a Base64 encoding of the file chosen by the user. The elm module containing the automated tests demonstrates how such a Base64 representation of a file is converted back to the original Bytes sequence representing the file.
  • How do we decode an image which was stored into a BMP file using Paint.NET? The automated tests added here model files and expected elm values resulting after decoding these image files.
  • How do we locate user interface elements in screenshots? The pattern model implemented here supports flexible configuration of a search which works with screenshots from video games like EVE Online.
  • How can we make it easy for developers to find the right search configuration for their use-cases? The graphical user interface implemented here supports quick configuration and testing of image search patterns.

I posted the complete exploration here:

I made progress with the guides for bot developers:

Last week, I started another exploration to learn how to further improve the development process for the image processing parts in our bots.
One result of this exploration is a guide which explains how to test candidate functions with example screenshots quickly. Using this approach, you can test the image processing parts of your bots without the need to start a game client. Instead, you point the test framework to an example screenshot and review the results.

I illustrated the approach to image processing and finding objects in screenshots with an example implementation and image.

A byproduct of this exploration is a demonstration of file loading (and parsing) in a bot. So if you have a use-case where you need this, the demo bot implemented here might be a good starting point.

I posted the completed exploration to the repository on Github here:

For more details, see the overview document at bots/ at c36d58b7a68fa07ba5ca15668ef68f550778938f · Viir/bots · GitHub