You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Peery
9e5c269238
Finished a basic harvester logic which sets its harvesting and destination (where it brings the resource to) in memory which can be set by the overlord. The harvester uses a state machine which persists also via memory to know what its doing and currently just travels to its harvest_spot, harvest, travels to its destination and delivers there and then repeats. This means there is currently close to no error handling. For example if the storage is full, the harvest target is cooling down or the creep dies of age or damage is an issue. The creep also doesn't register its death or damage in anyway. |
2 years ago | |
|---|---|---|
| src | 2 years ago | |
| .credentials.json.sample | 2 years ago | |
| .gitignore | 2 years ago | |
| Gruntfile.js | 2 years ago | |
| design_plan.txt | 2 years ago | |
| package-lock.json | 2 years ago | |
| package.json | 2 years ago | |