active 2025-09-04 → 2025-09-04 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 1 days from 2025-09-04 to 2025-09-04. Pushes: 4 total, peak 4 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 48 total, peak 48 in a day. Comments: 0 total, peak 0 in a day. Stars: 0 total, peak 0 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| michaelnutt2 | 52 | 4 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
- Issue#82michaelnutt22025-09-04 19:04As the MatchRunner executes a game, serialize the game events (MatchHeader, Round, MatchFooter) into FlatBuffers.
- Issue#79michaelnutt22025-09-04 19:04It should contain the main while loop that calls GameWorld::run_round() until the game is over.
- Issue#77michaelnutt22025-09-04 19:03Implement a run_match function that takes two player bots and a map as input.
- Issue#76michaelnutt22025-09-04 19:03Create a MatchRunner struct in src/runner.rs.
- Issue#68michaelnutt22025-09-04 19:02Investigate popular Wasm runtimes like **Wasmer** and **Wasmtime**.
- Issue#66michaelnutt22025-09-04 19:01Write tests for the RobotController implementation to ensure that API calls correctly modify the GameWorld state.
- Issue#64michaelnutt22025-09-04 19:01Create a struct that implements this trait, holding a reference to the GameWorld and the current robot's ID.
- Issue#63michaelnutt22025-09-04 19:01Define a RobotController trait in src/api.rs with methods for all robot actions.
- Issue#62michaelnutt22025-09-04 19:01Ensure the test suite runs with `cargo test`.
- Issue#61michaelnutt22025-09-04 19:00Ensure the project compiles successfully with cargo build.
- Issue#60michaelnutt22025-09-04 19:00Add the `flatbuffers` crate as a dependency.
- Issue#59michaelnutt22025-09-04 19:00Initialize a new `cargo` library or binary project.
- Issue#58michaelnutt22025-09-04 19:00Write an integration test where a robot paints a pattern and the engine correctly identifies and completes it.
- Issue#56michaelnutt22025-09-04 19:00Write unit tests for the pattern-checking logic against known positive and negative cases.
- Issue#55michaelnutt22025-09-04 19:00Implement `check_resource_pattern` and `check_tower_pattern` functions.
- Issue#51michaelnutt22025-09-04 18:59Implement a general `apply_damage` function that handles health reduction and robot death.
- Issue#49michaelnutt22025-09-04 18:59Create an `Action` enum in Rust to represent the different types of game actions.
- Issue#47michaelnutt22025-09-04 18:59Update the robot's position in all relevant data structures.
- Issue#46michaelnutt22025-09-04 18:59Apply the movement cooldown (`GameConstants::MOVEMENT_COOLDOWN`).
- Issue#44michaelnutt22025-09-04 18:59Implement a `move_robot` method on `GameWorld`.
- Issue#43michaelnutt22025-09-04 18:58Write unit tests for `ObjectInfo` to verify that creating, destroying, and querying robots works as expected.
- Issue#41michaelnutt22025-09-04 18:58Implement methods for `process_beginning_of_turn` and `processes_end_of_turn`.
- Issue#39michaelnutt22025-09-04 18:57Write unit tests for coordinate conversion logic to prevent off-by-one errors.
- Issue#38michaelnutt22025-09-04 18:57The `GameWorld` struct should own an instance of `LiveMap`.
- Issue#37michaelnutt22025-09-04 18:57Add methods for accessing walls, ruins, and paint at a given location.
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.