Closed dgets closed 5 years ago
The algorithm that I'm currently implementing uses a static (constant set) number of squares per side to determine the area to examine. It would be better to have this set up to take a side length as an argument, in order to make it more useful for varying tasks and under different processing time requirements.
I'm going to go ahead and pause on feature/map-breakdown-data in order to implement this quickly here. It'll assist in being able to implement new functionality more easily, so it seems like a justifiable diversion from what I was previously working on.
This has been handled.
It appears that, using
MapCell.mark_unsafe()
, we can easily create a route taking maximal halite conservation and/or mining en route back to the shipyard/dropoff fairly easily. I think that it's a fairly good bet right now that a large portion of the halite is disappearing in transit back to the drop point, so this isn't a bad next focus branch.