I changed the anomaly to take to “Angel Hub”, but for a strange reason, when it finishes the first anomaly, the bot opens the scanner, and says “there’s no anomalies, warping back to home”, when there’s actually like three more.
The answer at the same question is here: ( +/- couple posts up or down)
and also here
I really thank you for each feedback of my bots, there are invaluable infos for me, and I will appreciate if you continue sending them.But is not good to expect at 100% possibilities covered by any bot, unless if you created a game designed to be played 100%automatic;
I don’t think the problem is the 0,0001 delay. The anomaly list is populated. I have 4 “Angel Hub” in anomaly scanner. This is the situation:
Bot starts, undocks, iterates through anomaly scanner and correctly ignores the ones that should be excluded. It just leaves unfiltered those I want to run (Angel Hub. The system has 4 Angel Hub permanently, with almost 100% uptime). Then, bot takes warp to the first item in the anomaly scanner, and successfully completes the site. It reopens again anomaly scanner, but it seems it can’t iterate again through the list. There are four warpable anomalies, but the bot isn’t able to see it somehow, it thinks there isn’t any anomalies left in the system, and just warps to “home” and stay tethered forever.
I think it could be caused because the bot doesn’t use the same function (or whatever you call it, sorry, I’m not programmer ^^’ ) as when undocking and warping for the first time.
To sum up, the bot correctly iterates through anomalies list when starting it, but fails to “read” when completes first site.
I think this problem could be fixed telling the bot to retrieve anomalies list (again) when tethered, or leaving anomaly scanner open all the time?
I’ll be grateful if you could shed some light to this problem!
if you find a second function or method who execute “taking anomalies” on my script, I give you a champagne. ( that if you are adult and drinking alcohol is not forbidden at your age or your health )
I already explained to you why this is happening.
The script is working for everybody, except you. For me is working like it is for … 20 H daily on different chars.
So you could change your script in a more appropriate version for yourself.
So, follow the execution of code
buddy … i found a bug … when the bot finds a dread … it keeps going back and forth to the site in infinite loop without doing nothing …
also when you enter an anomaly claimed by another player it just stands still doing nothing
anyway, I updated the dread behaviour and moved upper the lines to open the probe window; if it doesn’t work for you then the log vital to detect what is happening in your case.
like usual updated git:
I don’t know, I told you if your bot stops and wait, that means you have darkblue on ally and green on corp players., but if is not the case, you can check and inspire yourself from the picture I posted already.
without a log from you I cannot do nothing, I don’t have divination powers like telepathy, visualisation at distance, etc to see why your bot stays when he find friends on site and not ignore the anomaly and get out from there like mine do on every same situation
and if you just tell " he stays there" that doesnt help at all; you can describe at least: the window pobe is opened already?the mouse hovering there? in the window the “km” is there or not?.
with your exact description and the log, I can guess what happens, and why, by extrapolation. Without them is pure speculation ( or divination)
You asked to have it rolled back… what has changed in the version you are using? You just download the last version that worked for you. I looked at the github version and the last series of commits was a couple of days ago
if you want to go back you will have to use this
strange, because I runned the last version half a day and is working.
you can see the changes if you look on commit list ( on the code, it shows in red what is deleted and green what is in +)
the last version is an sumum of
+add delete bookmark when dread is there and changes in measurement modules
agreed with you, garbage version is better because is simpler (even so I saw if you have salvage drones and combat, sometimes it launch the salvage drones in combat mode , but that happened when I runned 3 chars - 2rdp and one main, so the lag was consistent… ram at full, etc etc)
click on commits, chose your best, copy paste the link ( it has to be the one with blop inside) or better, go to raw, copy/paste the code in your file.
alright thanks buddy i will also give garbage a shot …
1 more thing can you make a guide or toturial on how to make multiple bots running at the same time ? i tried RDPWrap and i couldn’t make it work the new windows are always buggy and too slow