barolet / kovans-ogbot

Automatically exported from code.google.com/p/kovans-ogbot
0 stars 0 forks source link

Attacking same planet several times #103

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
This has happened to me several times.

If the bot finds a new planet (daily inactive scan), and that planet has 
much more resources than average, it will be put on the top of the table.
The problem is that if the planet has 3 or 4 times the ammount of 
resources that the second one it will get a rentability value very high, 
so high in fact that even after the bot send a fleet and cuts the value by 
half it will still be number one on the rentability list, wich means that 
the bot will try to attack it again, but it will send a probe before the 
attack, and restore the original value for resources for that planet, and 
the cycle begins. The bot will continue to believe that the planet has 
lots of resources even after sending 5 (or more) fleets to attack, and all 
those fleets will have enough ships to bring those resources (when the 
second will have half, the tird 1/4, and so on..). The only way now to 
stop this is to cancel the fleets manualy, and keep canceling them until 
the first or second fleet attacks the planet, only then will the bot stop 
sending fleets.

I have one suggestion for this problem:

Put a internal timer on this planet with 105% (or some other value that is 
relevant) the time it takes the fleet to reach it, and if the bot decides 
to attack the planet again, if the timer is not zero, don't send a probe 
and assume the value it has now is accurate. if the timer is zero send a 
probe and continue as normal.

Original issue reported on code.google.com by HugoMCae...@googlemail.com on 22 Mar 2007 at 3:45

GoogleCodeExporter commented 8 years ago
That's right, it's an old known bug. 
It was reported in spanish at
http://code.google.com/p/kovans-ogbot/issues/detail?id=18, but I'm marking that 
one
as duplicate of this.

Original comment by jsceballos on 22 Mar 2007 at 3:58

GoogleCodeExporter commented 8 years ago
Fixed in next version (> 2.1.2d)

Original comment by jsceballos on 25 Mar 2007 at 8:10

GoogleCodeExporter commented 8 years ago

Original comment by jsceballos on 9 Jun 2007 at 9:58