So in the meantime when bot is running not dying and happily looting, maintaining drones and killing EWAR targets as top priority. I’ve been playing with my fittings.
Then I’ve came up with armor instead of shield fits and that made me tweaking my bot even more And because I did not like recompiling every time I’ll change fit… I have made some changes
So, for those interested in some bits of my code
This bit takes care about armor/shield fits and accordingly maintaining all my security protocols valid. (otherwise bot will warp off on armor fit when shields are below 15%
// armor ship
if (armorRepairers.Count() > 0)
{
ActualHitpoins = armorHitPoints;
if (bot?.ConfigConstants.ArmorPermaTank == true)
{
yield return bot.EnsureIsActive(armorRepairers);
}
else
{
Random rnd = new Random();
int RepairStartAt = rnd.Next(520, 850);
int RepairEndAt = rnd.Next(870, 1000);
if (ActualHitpoins < RepairStartAt)
{
yield return bot.EnsureIsActive(armorRepairers);
}
else if (ActualHitpoins > RepairEndAt)
{
yield return bot.DeactivateModule(filteredArmorRepairers);
}
}
}
// shield ship
else
{
ActualHitpoins = shieldHitPoints;
}
If you are wondering why there are Random generated numbers, wonder not!
I do run capstable fits, but am not running armor-reppers all the time, simply because Dreads have neuts and in some cases you’ll not be able to warpoff in time when you get hit by neut. So maitaining as full cap as possible is very important.
Secondly randomizing when armor rep will run and when not is more closer to humans as it usually never occurs at exact numbers. So randomizing when to turn them on/off makes it way more difficult to even recognize this bot …
This code simply starts repping somewhere between 52 - 85percent of armor, and turn them down between 87 to 100percent
note: of course this can be applied to shield boosters easily as well.
Enjoy