Manually logging into the wrong game is easy using SWATH alone. The simplest way is to click "No" when it asks if you want to auto-login, then select the wrong game. You can also log out of the correct game, think "Hmm, I wonder how this other game is going", and forget to turn off parsing before you look at it. Even just viewing the scores clutters the SWATH database with the names of players from the other game.
My complicated solution is that whenever the TWGS "Selection (? for menu): " prompt appears, my lexer enters a special TWGS_PROMPT state. From there, the letters [A-PR-Z] followed by a newline trigger a "gameSelected" event. The parser compares the selected game to the database and puts the lexer into either the CORRECT_GAME or WRONG_GAME state. Any other input drops the lexer back to the TWGS state, where it watches for the prompt to appear again. A newline by itself indicates the beginning of an asynchronous message from the server, like a shutdown announcement. That gets a little more complicated because the announcement could contain a message from the sysop, and that message could contain anything, including a game letter on a line by itself. To get around this, my lexer enters yet another special state when it sees the beginning of an async message, and remains in that state until it sees one of the standard server messages beginning with the ASCII bell character. The "Selection" prompt is not redisplayed, but you are actually still at that prompt, so the lexer falls back to the TWGS_PROMPT state and starts looking for a game letter again.
I *think* I've covered all the bases... but man, this was needlessly complicated. No surprise that other helpers don't even try.
|
