Combat Anomaly Bot errors and will not run

I have a json, but the site won’t let me upload it, so the notepad export is below. The bot appears to start after “start playsession” but then immediately errors out with the below. What other info can I provide?

Edit: I had to truncate the below because the forum gave a “too many characters” error. Hopefully there is enough here.

“botlabClientVersion”: “2022-10-28”,
“botId”: “0edb5a7f0f115d617dc09f2725591aec4c6bcb1e041abfae48e9ef58ffb79418”,
“initialBotSettingsHash”: “314856”,
“sessionCustomName”: “2022-11-17T14-06-35”,
“onlineSessionId”: “ac6c586b97e28363cc2c”,
“lastBotStep”: {
“sessionAgeMilliseconds”: 150242,
“statusTextFromBot”: “Visited anomalies: 1.\nShield HP at 93%.\nI see the drones window: In bay: 8, in local space: 5.\nCurrent anomaly: ISG-844. Seeing 0 other pilots in the overview.\n\u002B I see ship UI and overview, undocking complete.\n\u002B\u002B We are in anomaly \u0027ISG-844\u0027\n\u002B\u002B\u002B I see no locked target.\n\u002B\u002B\u002B\u002B I see an overview entry to lock.\n\u002B\u002B\u002B\u002B\u002B Lock target from overview entry \u0027Coreli Guardian Spy\u0027\n\u002B\u002B\u002B\u002B\u002B\u002B Click menu entry \u0027with text equal \u0027Lock target\u0027\u0027.\n\u002B\u002B\u002B\u002B\u002B\u002B\u002B Open context menu on overview entry \u0027Coreli Guardian Spy\u0027\n----\nEVE Online framework status:\nLast reading from game client: 000031-144737: 0 rects containing 0 pixels\nLast result from volatile process is: Success: {\u0022ReadFromWindowResult\u0022:{\u0022Completed\u0022:{\u0022processId\u0022:25100,\u0022windowClientRectOffset\u0022:{\u0022x\u0022:10,\u0022y\u0022:39},\u0022readingId\u0022:\u0022000031-144737\u0022,\u0022i…\nCurrent activity: Waiting for completion of task \u0027send-effects-64\u0027: Send effects to game client”
“finishReason”: {
“RuntimeExceptionFinishReason”: [
"System.Exception: Bot reported decode error: Failed to deserialize event: Json.Decode.oneOf failed in the following 2 ways:\n\n\n\n(1) The Json.Decode.oneOf at json.ApplyEventOnMainBranchRequest[0].eventAtTime failed in the following 4 ways:\n \n \n \n (1) Problem with the given value:\n \n {\n \u0022TaskCompletedEvent\u0022: [\n {\n \u0022taskId\u0022: \u0022send-effects-64\u0022,\n \u0022taskResult\u0022: {\n \u0022RequestToVolatileProcessResponse\u0022: [\n {\n \u0022Err\u0022: [\n {\n \u0022FailedToAcquireInputFocusError\u0022: [\n {\n \u0022error\u0022: \u0022Response field success is null\u0022,\n \u0022exceptionToString\u0022: \u0022System.AggregateException: One or more errors occurred. (A task was canceled.)\r\n —\u003E System.Threading.Tasks.TaskCanceledException: A task was canceled.\r\n at System.Threading.Tasks.Task.GetExceptions(Boolean includeTaskCanceledExceptions)\r\n at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)\r\n at System.Threading.Tasks.Task\u00601.get_Result()\r\n at BotLab.Client.InterProcessCommunication.InterProcessCommunicationState.RequestInputFocus(TimeSpan maximumWaitTime)\r\n at BotLab.Client.PlaySession.PerformTaskRequestToVolatileProcessConsideringInputFocus(String agentTaskId, RequestToVolatileProcessConsideringInputFocusStructure requestToVolatileProcessConsideringInputFocus)\r\n at BotLab.Client.PlaySession.\u003C\u003Ec__DisplayClass90_0.\u003CStartAgentTask\u003Eb__2()\r\n at System.Threading.Tasks.Task\u00601.InnerInvoke()\r\n at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)\r\n at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task\u0026 currentTaskSlot, Thread threadPoolThread)\r\n at System.Threading.ThreadPoolWorkQueue.Dispatch()\r\n at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart()\r\n— End of stack trace from previous location —\r\n\r\n — End of inner exception stack trace —\r\n at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)\r\n at System.Threading.Tasks.Task\u00601.get_Result()\r\n at BotLab.Client.InterProcessCommunication.InterProcessCommunicationState.RequestInputFocus(TimeSpan maximumWaitTime)\u0022,\n \u0022remoteResponseString\u0022: \u0022\u0022,\n \u0022delayDurationMilliseconds\u0022: 2017,\n

1 Like

Thank you for the report, I will look into it.

This part on the error stack trace indicates that problem happens when multiple instances are open:

Did you run multiple bots at the same time? I will need to test this kind of setup. It should work, but this error indicates there might be a bug in the engine program code to coordinate between multiple instances.

Interesting, yes. I almost always have the local alarm bot running. I’ll turn it off and see what happens.

Edit: one reason I do this because sometimes the bot needs “help”. Specifically, if hostiles come in the bot pulls drones immediately. But if you are pointed or scrammed by rats, you’re very fucked because the bot tries to keep warping with drones in. So you need the local alarm so you can intervene.

It would be awesome to add a “#1 priority is kill whatever has me pointed” logic. Currently the logic seems to be “big ships first”. If the logic were “frigates first” this would also solve the issue because point/scram is always frigate rats.

Edit to the Edit: When hostiles come in, best order of operations would be.

  1. Align to structure.
  2. Is pointed? If yes then kill point. If no then
  3. Pull drones.
  4. Neut on Grid? If no, wait for drones. If yes.
  5. Dock.
  6. Drones withdrawn? No, wait for drones to get back, if yes, Dock.

#1, align to structure, is key because it allows instant warp if point is dead and hostiles arrive on grid. If drones are 50km away, you lose a lot of precious time waiting on drones to come in before aligning/warping out.

1 Like

Thank you for the clarification.
I will look into scenarios with multiple instances for further testing. I am working on a fix, but it will take a few days until the new version of the client is ready.

I found the bug which caused bots to stop in scenarios with multiple bots running at the same time.
This bug is fixed in version 2022-11-26. You can download the new BotLab client from

Newer, better version with some other improvements:

thanks I appreciate the quick response

1 Like