team-remember-to-hydrate / battlecode23-team-remember-to-hydrate

GNU Affero General Public License v3.0
1 stars 0 forks source link

Strategy: Carrier II #7

Closed 1NF053C closed 1 year ago

1NF053C commented 1 year ago

Goal: Implement the simplest "working" version of this strategy as possible

Rationale: This will enable the team to decide on how to "enhance" this strategy (if needed) once this is functional (depending on individual bandwidth)

Strategy:

Capabilities:

Explanation: Have my carriers effectively path find to the initially sensed well (usually Ad) and back to HQ. This will reduce meandering and increase growth of that first sensed resource, however, this alone might reduce growth of the opposite resource. (Mana if first sensed well is Ad). A minimum effort way to mitigate this risk is to mix carrier exploration strategies (Carrier I strat to find Ad + Mn around the map, plus a few carriers using Carrier II to squeeze more growth out of that initially sensed well (usually Ad).

How to decide what to implement for the next version of this strategy: "Resilient" Iteration:

  1. Build effective robots that are good at doing the job they are meant for in simple cases
  2. Identify potential failure, unexpected input, condition or malicious attack on the bot
  3. Modify or Add capability that enables robot to maintain useful level of functionality (its job) without disruption
  4. If entirely disrupted from its job, consider modification that would let it return to job quickly

Example disruptions that could be handled in next implementation:

  1. Carrier is attacked. This would disrupt it from its job. https://github.com/team-remember-to-hydrate/battlecode23-team-remember-to-hydrate/issues/8 can prevent this from becoming an issue.
  2. Well is being consumed at its max resource production rate Mitigation: Sense another well, Start consuming that. (todo: create issue for this when someone has the bandwidth to implement)