ToDo

Open
#1 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
game-dev

Research direction

The issue names no files, tests, or entry points. First clarify whether the work covers mining capacity, timeout prevention, bot behavior, or all three, then identify the relevant game-loop and bot code. Done should be defined with concrete behavior and timeout or gameplay tests.

Written by the indexing model from the issue text.

Description

enhancement

Fill mining capacity for owned planets after all the planets are occupied

Ensure timeouts don't occur (see Matthew's highschool friend's)

Build a bot that shifts to a planet by planet basic after a certain point in game

Dominant language
Python
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eli1797/Halite2Python

All issues in eli1797/Halite2Python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.