Skip to content
GitHub Explorer

CodeZombie/statecraft

View on GitHub ↗Related repositories →

active 2025-01-06 → 2025-06-01 (UTC)

Partial coverage12,718 / 14,510 hourly files (88%) · 2 absent upstream · 1,786 failed, retryable2024-12-14 → 2026-08-11 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
77
Pushes
22
Pull requests
2
Issues
27
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 147 days from 2025-01-06 to 2025-06-01. Pushes: 22 total, peak 3 in a day. Pull requests: 2 total, peak 1 in a day. Issues: 27 total, peak 5 in a day. Comments: 26 total, peak 7 in a day. Stars: 0 total, peak 0 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
CodeZombie7622126
dmatthewclark1010

Recent activity

Latest issues, pull requests and releases

  • Issue comment#10CodeZombie2025-06-01 19:52
    Implement StateStack
  • Issue#44CodeZombie2025-03-31 00:40
    Switch Node2D to CanvasItem in State.draw()
  • Pull request#43dmatthewclark2025-03-27 06:30
  • Issue#40CodeZombie2025-03-22 15:50
    Event Evaluation Order?
  • Issue comment#33CodeZombie2025-03-22 15:09
    Add a `add_physics_process_event()` method.
  • Issue comment#35CodeZombie2025-03-22 15:05
    New Action API
  • Issue#35CodeZombie2025-03-22 15:05
    New Action API
  • Issue comment#37CodeZombie2025-03-22 15:04
    State Machine Bonding
  • Issue#37CodeZombie2025-03-22 15:04
    State Machine Bonding
  • Issue comment#38CodeZombie2025-03-22 15:02
    bi-directional relay messages?
  • Issue#38CodeZombie2025-03-22 15:02
    bi-directional relay messages?
  • Pull request#39CodeZombie2025-03-20 02:12
  • Issue#33CodeZombie2025-02-27 04:21
    Add a `add_physics_process_event()` method.
  • Issue comment#21CodeZombie2025-02-23 22:40
    manually transitioning a StateRunner may not reset the current state's Status correctly.
  • Issue#21CodeZombie2025-02-23 22:40
    manually transitioning a StateRunner may not reset the current state's Status correctly.
  • Issue comment#27CodeZombie2025-02-23 22:33
    Consider Object.signals?
  • Issue#27CodeZombie2025-02-23 22:33
    Consider Object.signals?
  • Issue comment#28CodeZombie2025-02-23 22:33
    States should automatically emit "entered" and "exited" signals
  • Issue#28CodeZombie2025-02-23 22:33
    States should automatically emit "entered" and "exited" signals
  • Issue comment#31CodeZombie2025-02-22 18:14
    Interstate communication
  • Issue comment#31CodeZombie2025-02-22 18:08
    Interstate communication
  • Issue#31CodeZombie2025-02-22 18:02
    Interstate communication
  • Issue#30CodeZombie2025-02-22 17:38
    StateRunner Node
  • Issue#12CodeZombie2025-02-22 16:54
    Should we be able to execute `run()` on a Single state?
  • Issue#20CodeZombie2025-02-17 04:52
    EXIT_POLICY may behave strangely when set to REMOVE after first run()

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.