Changes to bot 12d565847a

Request Feedback
1

I have only used this bot for a few hours now but these are some of the things that i would like to see added or changed about bot 12d565847a.

  1. The ability to orbit specific objects/structures instead of orbiting various rats.

  2. Allow for a variable amount of time to be waited at the end of each site. While using this bot it has let multiple commander spawns go free because it is warping away too quickly at the end of sites.

  3. It would be nice to have the bot close the various site message popups that appear when warping to sites. I have noticed that sometimes having the site message popup interferes with the bot and causes problems. (like not targeting when entering a site)

  4. Not allowing the bot to spam warp to various anomalies while you are all ready in warp to an anomaly.

1 Like
2

Also im not sure if it is just me and my settings but this bot does not want to warp away from a site that is all ready inhabited by another player.

To be able to utilize this function do friendlies need to be visible in my targeting overview? If so that sets a very dangerous precident. If the bot we to accidentally target and attack a friendly, that would be disastrous.

3

I have been looking over the code for this bot to try to tweak it in the ways that i want, as well as looking over the forums to find alternative answers. I stumbled across this post by @Viir

----------------------------------------------------------Declaration

overviewEntriesToOrbitNames : List String
overviewEntriesToOrbitNames =
[ “broken” ]

---------------------------------------------------------Code

shouldOrbitOverviewEntry : EveOnline.ParseUserInterface.OverviewWindowEntry → Bool
shouldOrbitOverviewEntry =
.objectName

Maybe.map
(\objectName →
overviewEntriesToOrbitNames
|> List.any
(stringContainsIgnoringCase >> (|>) objectName)
)
Maybe.withDefault False

I was wondering if I could paste these two parts into the original code of 12d565847a. I figured the declaration part could go on line 226 in the list of other declarations. and the actual code part can go on line 690 to keep it next to the other orbit command.

1 Like
4

Hey, thank you very much for sharing these insights!

I think we implemented this already in bot d66ba405fe: https://catalog.botlab.org/d66ba405fe

I strongly recommend you check out d66ba405fe, because that one is much newer than 12d565847a and has more improvements included.

Any of the overview windows should work for seeing the other pilot. That bot looks at all overview windows.
In case you still see that problem with d66ba405fe, we might need to tweak it to adapt to the appearance in your game client.

The current implementation depends on comparing with the local chat window to decide which overview entry represents a player:

If you see an alternative approach, we could adapt that.

5

Thanks for the response @Viir

I have tried to use bot d66ba405fe it has a list of its own problems, so i am using the most stable bot i have found so far to actually preform the functions I want from it. Most notably bot d66ba405fe continually spams the attack function when the player is using drones. I do not want to run this bot while that is happening because that seems like a very easy way to detect the bot.

6

This is 100% due to my settings, i had to add blues to my active overview tab, and then the bot would recognize other players.

Im wondering if it would be better to allow the bot to use the directional scanner set to the lowest scan range. Upon landing at site, hit the D-scan once and if there is a ship in the dscan list warp to another site.

7

Thank you for the update!

Sounds good, that approach should work as well :+1: