More weird conundrum behaviour, this time during
this hypergoatconundrum attack. Here's the relevant log-
Awoken!
Challenge set update, informing 1 listeners.
ClientGame4453574190770034780 << net.MessageToServer$ExistingGameRequest@6c5ac4
ClientReceiveThread >> net.MessageToClient$ExistingGameResponse@1bb0662
RX net.MessageToClient$ExistingGameResponse@1bb0662
XX net.MessageToClient$ExistingGameResponse@1bb0662
Existing game vs 101: null
Existing game: null
CX Synch stage 1 (writing)...
ClientGame4453574190770034780 << GameEvent{key=4453574190770034780,pos=1,o=87621}
CX Synch stage 2 (reading)...
ClientReceiveThread >> GameEvent{key=4453574190770034780,o=87622}
RX GameEvent{key=4453574190770034780,o=87622}
ClientReceiveThread >> GameEvent{key=4453574190770034780,o=apterous.game.ConundrumPuzzle@122e89e}
RX GameEvent{key=4453574190770034780,o=apterous.game.ConundrumPuzzle@122e89e}
XX GameEvent{key=4453574190770034780,o=87622}
XX GameEvent{key=4453574190770034780,o=apterous.game.ConundrumPuzzle@122e89e}
CX Synch done.
CX Conundrum round started...
CX getting shuffle...
CX Got shuffle, passing to player...
TPP 3
1
CX initializing plexer...
CX awaiting message
1
PROCESSINGS
PROCESSINGS
[S]Awoken!
CX want buzz
ClientGame4453574190770034780 << GameEvent{key=4453574190770034780,pos=1,o=net.ConundrumEvent$BuzzRequest@11a67fe}
CX awaiting message
PROCESSINGS
ClientReceiveThread >> GameEvent{key=4453574190770034780,o=[Buzz for P=1]}
RX GameEvent{key=4453574190770034780,o=[Buzz for P=1]}
XX GameEvent{key=4453574190770034780,o=[Buzz for P=1]}
Awoken!
CX buzz: [Buzz for P=1]
CFRAME: informBuzz 1
PROCESSINGC
PROCESSINGC
[C]###67
Patience out
TPP 3
Awoken!
CX got answer from iface, sending
ClientGame4453574190770034780 << GameEvent{key=4453574190770034780,pos=1,o=net.ConundrumEvent$Answer@1fc1b56}
CX awaiting guess response
ClientReceiveThread >> GameEvent{key=4453574190770034780,o=net.ConundrumEvent$IncorrectContinue@118cb72}
RX GameEvent{key=4453574190770034780,o=net.ConundrumEvent$IncorrectContinue@118cb72}
XX GameEvent{key=4453574190770034780,o=net.ConundrumEvent$IncorrectContinue@118cb72}
Awoken!
CX got guess response: net.ConundrumEvent$IncorrectContinue@118cb72
CX awaiting message
CFRAME: informDeclaration P1 guessed SC on 13279 ms: Incorrect
ClientReceiveThread >> net.MessageToClient$SpectatorMessage@80b973
RX net.MessageToClient$SpectatorMessage@80b973
ClientReceiveThread >> net.MessageToClient$GamesInProgressUpdate@10f3a9c
RX net.MessageToClient$GamesInProgressUpdate@10f3a9c
XX net.MessageToClient$SpectatorMessage@80b973
EVINSERT:Charlotte Melia is playing Stephen Porritt. <a href="
http://dog.com/spectate.html?-435232210 ... ectate.</a>
XX net.MessageToClient$GamesInProgressUpdate@10f3a9c
Exec delta: +[-6293627484571137632: net.GameSummary@d115db]
Exec delta: +[7528316312883109573: net.GameSummary@f20964]
Exec delta: +[-3658474037421825461: net.GameSummary@46a171]
Exec delta: +[-8710331940071757019: net.GameSummary@1110f31]
Exec delta: +[-4352322101418486103: net.GameSummary@fc63be]
SpecPanel: adding text
SpecPanel: Setting caret
SpecPanel: done.
CX sending keepalive
KeepaliveThread << net.MessageToServer$Keepalive@1dcd49d
CX sent keepalive
ClientReceiveThread >> net.MessageToClient$SpectatorMessage@6313e1
RX net.MessageToClient$SpectatorMessage@6313e1
XX net.MessageToClient$SpectatorMessage@6313e1
EVINSERT:Nick Wainwright completed today's Daily Duel.
SpecPanel: adding text
SpecPanel: Setting caret
SpecPanel: done.
ClientReceiveThread >> net.MessageToClient$GamesInProgressUpdate@1a5d193
RX net.MessageToClient$GamesInProgressUpdate@1a5d193
XX net.MessageToClient$GamesInProgressUpdate@1a5d193
Exec delta: -[7528316312883109573: null]
Exec delta: +[6032279655768484214: net.GameSummary@16237e0]
Exec delta: +[6960829081154569957: net.GameSummary@1425e17]
Exec delta: +[-4352322101418486103: net.GameSummary@2f6aea]
CX Revealing goat hint
ClientReceiveThread >> GameEvent{key=4453574190770034780,o=net.ConundrumEvent$TimeoutUnsolved@1dd1c39}
RX GameEvent{key=4453574190770034780,o=net.ConundrumEvent$TimeoutUnsolved@1dd1c39}
XX GameEvent{key=4453574190770034780,o=net.ConundrumEvent$TimeoutUnsolved@1dd1c39}
Awoken!
CX timeout unsolved
ClientGame4453574190770034780 << GameEvent{key=4453574190770034780,pos=1,o=net.ConundrumEvent$End@1a256c7}
CFRAME Timeout unsolved SCINTILLATED
ClientReceiveThread >> GameEvent{key=4453574190770034780,o=net.ConundrumEvent$End@10ab67f}
RX GameEvent{key=4453574190770034780,o=net.ConundrumEvent$End@10ab67f}
XX GameEvent{key=4453574190770034780,o=net.ConundrumEvent$End@10ab67f}
Awoken!
CX sending keepalive
KeepaliveThread << net.MessageToServer$Keepalive@178986b
CX sent keepalive
Challenge set update, informing 1 listeners.
Basically it says I timed out after entering the C even though I know I entered all the letters at normal typing speed.
A magazine publishing company for whom I do a lot of freelance proofreading work even had it in their house style guide for a while until I got them to take it out. How do these things start and why do they spread?
