Im Back Im working to make A-Bot Working with Capitals and Supers with Fighters
Those are the points to do:
1. Check Local Status → If clear then continue else wait for the clear status → Done! 2. Undock → Done 3. Active Perma Modules → Done! 4. Warp at 50km from the selected Anomalies → Done! 5. If Anomaly is empty (so any blue or corp or alliance member is inside continue else he change anomaly) → Done 6. In anomaly empty then align to the bookmark “INSTADOCK” → Done! 7. Activate the “Network Sensor Array” → Done! 8. Put out the fighter! and start the fight → Done!
9. At end of the anomaly repeat from the point 4 to the 9
In all this the bot have to check if the local is clear, if in local appear any neautral or enemy he have to stop the work and warp at 0km on the INSTADOCK and then dock to the station
If anyone want help me on this please, post here the relative code of the point he done.
Implementation of retreat to InstaDock safespot and dock at the end of warp → Done
Active Perma Modules → Already implemented in to A-Bot by bot.config
Implemented function “ShouldBeActivePermanent” This function will activate after the bot land in anomaly the modules settend into the bot.config under the voice “ModuleActiveBeforeFight”. Example: "ModuleActiveBeforeFight": ["Networked Sensor Array"]
Next Implementation:
Use FighterSquadron on combat
Warp at 50km on the anomaly
Check if the anomaly it’s already taken from another mate
Have you considered just using the “warp to” function and set the default value to 50km in the client? To simplify things.
The option to have it check if someone else is in the anomaly after warping to a new site will be a huge pluss!
I dont have a capital so I don’t know, but can’t they use the “dock” command from the warp list?
If so you would get around that then, when retreating using dock instead of warp to.
@Fuzzy If I have to retreat I warp on the safespot and then I dock, so I have not the “dock” entry into the menù, I done this to avoid the possible to be out docking range then the warp end at the station
Sorry Im not able to answer you in russian, however I translated your post with google translate.
At the moment isn’t possible test it, Im still working on the code, I made this topic to update what I change/integrate into the A-Bot and for find some other devs to help me on that.
Я буду разрабатывать альтернативный скрипт для фарма зелёных аномалий на VEKSOR , в NPC системах ниже 0,0.
Готов взять за основу
Алгоритм действий.
1 . Проверка нейтрала в системе
2. Проверка наличия корабля в случаи отсутствия взять корабль из ангара по имени корабля
2 . Открытие меню аномалий.
3. Варп на аномаль и определение занято или нет. ( возможно прописка конкретных типов аномалий)
4. запуск дронов и зянятие орбиты на объект.
5 назад в цитадель.
Sorry man, but Im not working on A-Bot for ship under the capitals, I am working only for the capitals and motherships, almost of the operation from you typed are already done in the actual A-Bot.
What do you have add in case you want use Vexor are:
Check for the ship in hangar
Check if the anomaly it’s already taken
Go back to station
Maybe for some action like: check if the anomaly is already taken, check the local status I can share here my codes to add/modify in H-Bot.
Improved the return of single squadron if under attack, now the bot give the speed bonus command after the recall and reconize more better the status of retreat without spam the “Recall to launch tube”
Improved the reconize of squadron’s status when are into the tube, now the bot not give the launch command if almost one of squadron is “ready”
Improved the attacking of squadroins, avoid F1 spam (activate/deactivate of the attack)
In Task:
Check if the anomaly is empty or already taken, if taken “ignore” the current result from the list and then warp to next anomaly
Check if a fighter die, if the squadron size is below the max then fill up the squadron again
Hello dude, I was wondering if it will be able to dock at citadels? I’ve been looking for a capital ratting bot but it seems like they only use stations for docking (some hunter send in a dictor to bubble a station so they can catch people warping there).
Keep up the good work, looks promising
Edit: One more question, regarding…
“5. If Anomaly is empty (so any blue or corp or alliance member is inside continue else he change anomaly)”
Do you mean the bot will warp you away to another anomaly IF there is someone at the site? Don’t wanna steal other ppls ticks
Hi man, about the Station/Citadels, yeah work with both, my code not go to check the kind of station, use an tatctical safespot to instadock, and then go to give the dock at the station/citadel, the only staff to do is set the station/citadel fullname into the code, and he run.
Example:
→ Bot enter anomaly and align to the tactical safespot outside the station
→ During the anomaly neutral/hostile enter in system
→ Bot detect the neutral/hostile then warp at 0km on the tactical safespot outside the warp
→ Landing on the safe spost he give dock command so instadock
About the point number 5. this is to prevent stupid ppl can report for botting if you go inside and run her/his anomaly, and avoid possible convos
My bot is in testing, because is maked in base what I need, so at the moment it’s not possible change the various stuff without change the source code.
Yesterday I finished all main functions to make the bot usable, but Im monitoring the various aspect to understand if is safe keep it run alone, for example I saw sometines if more squadrons are keeping damage the bot tend to go in “crisis”.
So before release it I need: make configurable the station name etc from the bot.config file and then make improve the action management of the bot
