Elf M. Sternberg
Fixed end-state handler to stop taking Ball messages when end-state detected. Looking at Yahoo's results board, failing at this could result in the system looking as if I had poor win-state detection. Fixed win-state detection to enclose the card matrix. This makes the coordinate tests look like it takes coordinate pairs, which is the effect we want, improves readability, and reduces errors.
|9 years ago|
|.gitignore||9 years ago|
|LICENSE||9 years ago|
|README.md||9 years ago|
|bingo.coffee||9 years ago|
|package.json||9 years ago|
|package.yml||9 years ago|
Yahoo's running this contest. Read about it here: http://yahoobingo.herokuapp.com/
This took me about 40 minutes, total. I was thinking about re-writing this in Bacon, but my Bacon is pretty raw. At best, I could propertize the cards to create a new card (i.e. a new state) every time a ball came in, but that seemed a little overwrought.
It was nice to have an opportunity to hack Coffee and Node again.
I don't know that I trust Yahoo's server. At least once I got back a "you lost" signal from the server. Since this client includes full playback of every game, I could see that I had clearly won. Unfortunately, my initial code assumed "lost" as the default state, so I couldn't see if maybe the 'won' signal was lost before receiving the disconnect. I've changed that to 'playing,' so we can see that condition now.