joaomatheusfcorrea / betakore

Automatically exported from code.google.com/p/betakore
0 stars 0 forks source link

unique AI sequences #12

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Some AI sequences should be unique, like sellAuto and storageAuto. when, for 
example, telling kore to use autostorage when there's already this sequence in 
the AI queue we should decide whether to redefine it or just ignore...
Just saw one of my bots with 212 storageAuto sequences

Original issue reported on code.google.com by marcelof...@gmail.com on 20 Dec 2014 at 6:35

GoogleCodeExporter commented 9 years ago
It looks like Commands doesn't check the queue before adding a new process. I 
think the best way is just to ignore the new one (I commited it to the r146).

They are the same thing anyway. Dequeuing the old process just to queue it 
again doesn't make sense.

Original comment by jefferso...@gmail.com on 23 Dec 2014 at 4:20

GoogleCodeExporter commented 9 years ago
Dequeuing the previous sequence is useful when changing configs. But this could 
lead to unwanted macros behavior. I'll just improve the output in this case (we 
shouldn't print "Initiating auto-buy" when it's not initiating anything). If 
there's any other sequence that should't have duplicates we'd better implement 
something like AI::queue('sequence', { no_duplicate => 1 })

Original comment by marcelof...@gmail.com on 23 Dec 2014 at 5:07