killer-queen-stats / libkq

Killer Queen Library for Event Processing and State Tracking in Golang

libkq

Killer Queen Library for Event Processing and State Tracking in Golang

libkq's Issues

Third Party Triggers

Ability to add custom-written triggers that run along with the provided triggers. For instance a trigger on a game end event might run the normal state.endGame state.resetStats ... etc but also might run a user-provided function that sends an OBS websocket call.

Event to Trigger to State Engine Framework

libkq frontend should be bleak -- state can be pulled via an HTTP request which simply returns JSON.

Three different portions of code.

1. . Websocket client that processes events. on event call trigger.
2. . Triggers. Each trigger should be named according to the KQ event. They then make changes to the game state. example would be trigger.playerKill would call state.killAdd for the winner and state.deathAdd for the victim.
3. . State. Modified over-arching data object of the "game" from totals down to each players individual stats. state calls should preferably not call other state calls, and should mostly be called by trigger functions. State functions should also have a reporter that returns the current value.

TODO: Simple "Cab Simulator"

kqstats had a pretty cool feature that let you replay logs back in for testing.

Would like to do that again except maybe make the cab simulator a separate program all together. This would make unit testing harder but also I hate testing anyway.