hora/mlustard

Node.js utility for determining what's interesting about a Blaseball game event.

hi, i'm horațiu 👋

i'm a web developer and educator.

i am especially good at teaching beginner programmers the basics in (almost) any programming language.

i'm available for hire as a private or group tutor / code mentor. you can reach me at: horacodementor at protonmail dot com

mlustard's Issues

Capture skate tricks

Add more metadata about special events

Right now, mlustard is only logging that the following events take place:

• blooddrain
• partying
• reverb
• birds (circled, pecked, or that they were just there, hating blaseball)
• allergic reaction
• incineration (RIV)
• becoming magmatic
• feedback
• electricity zap
• becoming unstable
• consumer attack

It would be cool if some more information was logged about these events, like:

• which player(s) was affected
• what the event resulted in, or why it took place (ie: was a debt collected when a rogue umpire incinerated someone? who replaced the incinerated player? was the incineration because of instability, and did that chain to someone else)

Note to self:

• s7 d32 🐅 vs 🗣️ is useful for checking for debts, instability chaining
• s14 d101 🌹 vs 🏋️‍♀️ has owen picklestein being attacked by consumers in an outcome for a birds circling event (an inning after picklestein was attacked in the lastUpdate), what's that about?

Capture unruns

runners on base not being registered for older games

see: https://reblase.sibr.dev/game/aa1b7fde-f077-4e4b-825f-0d1538d02822

refactor how checking for interesting states works

• for every check, there's either a regex to check against the update text, or a function that returns t/f if a condition is met on the chronicler object

• for every check, something is updated on the analysis object

• each checker file could just be pairs of checks/updates, to make adding new checks easier

Capture outs on fielder's choice

Add a test that hits chronicler?

Would it be overkill to add a test that hits chronicler, checking from the newest logged game events and going backward to a set point, making sure that any incoming changes to the game event object doesn't throw any errors?

Make module backwards-compatible

The current implementation requires Node 14.0.0 or higher, since I used the optional chaining syntax which was first introduced without the need for --harmony in that version.

Would be nice to make this mode backwards compatible though.

capture run loss from shame pit

" The Shame Pit activates! Jazz Hands lose 1 run from the Jazz Hands's Shame."
Season 5, Day 113 – Breckenridge Jazz Hands vs. Chicago Firefighters

figure out a way to keep docs up to date

also, update them

Capture missing special events

• baserunners swept elsewhere
• salmon swim upstream
• mind tricks
• double strikes
• item events (breaks, fixes, new items)

Capture all info from game event

Even if you can deduce that info from game event props

Add secret base

• special
• baserunners?

Capture player mods, if any

Separate tests out into their own files

It's a bit overwhelming right now.

Add getter functions

mlustard would be more useful if it also had a bunch of helper functions, like:

• didSalmonSteal or getSalmonStolenRuns
• etc