search

dgets / nightMiner

Halite III Bot - rewriting Halite III bot from scratch with better project structure plans
6 stars 1 forks source link

Properly assign destinations prior to early_blockade() being activated #49

Closed dgets closed 5 years ago

dgets commented 5 years ago

I'm noticing, as of this last commit (that being edf515dced7c2f8bafa3e2774d33a2722a161ea1), that as of nightMiner.py, line 68, that though the _earlyblockade routine can be accessed here, none of the destinations have been set up for any ships that are going to be working on it yet. Clearly I got sidetracked and forgot to properly note where I had left off on things.

I'm not sure if this is responsible for any of the issues from an improperly set current_assignments[id].destination value just yet, but fixing it along the way just in case, and because it's sure to introduce new bugs at some point here.

dgets commented 5 years ago

Okay, so we only need to trigger the initialization once, probably. That might help a little bit. Other than that, it'd be good if the ships ever got their commands to move towards the destinations, instead of just sitting there being re-initialized every turn...

dgets commented 5 years ago

I don't think that they're being re-initialized any more, but I'm still having problems getting the damn ships to go to their destinations after early_blockade() is enabled.