c4countdown

.

Kai Laddiman wrote:Er, why do the guys who came first yesterday get 63 points yet there was 60 entrants? Unless there's a special bonus or something.

This should probably be explained somewhere but yes, you get 3 bonus points for a perfect score. For some reason the page is claiming that the perfect score is 102 (it was actually 92) but has given out the bonus points correctly anyway.

OK, I get it now, but I can't see how I had any control over it.

Wey hey I palookaed you all. Lovely conundrum btw

What a shame that TROMBONE is not yet a verb. Not outside the Profanisaurus anyway.

Ian Volante wrote:What a shame that TROMBONE is not yet a verb. Not outside the Profanisaurus anyway.

Oh god, I know, I went for TROMBONED too. Mind you, my entire Duel yesterday may well be nominated for Best Comedy Performance at the next BAFTAS.

Gutting. Not because I botched the conundrum (which I did), but because my duel hanged upon completion, denying me an easy 59 points (and breaking my 'all duels this month completed' run).

Well - 3rd is my highest finish yet! Congratulations to everyone who finished in third to day! It seems like all our hours of practice are finally paying off!

Ben Wilson wrote:Gutting. Not because I botched the conundrum (which I did), but because my duel hanged upon completion, denying me an easy 59 points (and breaking my 'all duels this month completed' run).

Shit it. Until you posted that, I had no idea that my 3rd place wasn't counted either.

Matt Morrison wrote:

Ben Wilson wrote:Gutting. Not because I botched the conundrum (which I did), but because my duel hanged upon completion, denying me an easy 59 points (and breaking my 'all duels this month completed' run).

Shit it. Until you posted that, I had no idea that my 3rd place wasn't counted either.

Same

In light of these distressing reports, I think it's only fair to give everyone who missed yesterday's conundrum 0 points.

Yeah my game hung after the conundrum too, odd.

Simon Myers wrote:Yeah my game hung after the conundrum too, odd.

Grr, same here.

Number of people who submitted any actual bug reports: 0.
Number of bugs I can therefore do anything about: 0.

And of all those people who were placed third, I'm listed first. It's not often I'm 3rd in a list of 61 people! Damn you, Lee and Paul. If you hadn't got that answer in three seconds I'd have been top of the list.

Charlie Reams wrote:Number of people who submitted any actual bug reports: 0.
Number of bugs I can therefore do anything about: 0.

Sorry Charlie, I had an exam at 9:30am yesterday morning and another tomorrow. My available time is therefore quite short. Here's the applicable part of my log:

EVINSERT:Welcome to the game! Anything said in this room remains between you and your opponent.<br><br>Variant: normal rules.<br />Rounds of 3 seconds.<br />Format: C.<br />Scoring: standard scoring.<br />Dictionary: English (ODE).<br /><br />
SpecPanel: adding text
SpecPanel: Setting caret
SpecPanel: done.
CX Synch stage 1 (writing)...
ClientGame179 << GameEvent{key=179,pos=1,o=87621}
CX Synch stage 2 (reading)...
ClientReceiveThread >> GameEvent{key=179,o=87622}
RX GameEvent{key=179,o=87622}
ClientReceiveThread >> GameEvent{key=179,o=apterous.game.ConundrumPuzzle@7db0b9}
RX GameEvent{key=179,o=apterous.game.ConundrumPuzzle@7db0b9}
XX GameEvent{key=179,o=87622}
XX GameEvent{key=179,o=apterous.game.ConundrumPuzzle@7db0b9}
CX Synch done.
CX Conundrum round started...
CX getting shuffle...
CX Got shuffle, passing to player...
Read 5480 bytes.
******************** READ 5480 ******************
TPP 5
1
CX initializing plexer...
CX awaiting message
PROCESSINGE
PROCESSINGE
[E]Awoken!
CX want buzz
ClientGame179 << GameEvent{key=179,pos=1,o=net.ConundrumEvent$BuzzRequest@3c6542}
CX awaiting message
PROCESSINGE
ClientReceiveThread >> GameEvent{key=179,o=[Buzz for P=1]}
RX GameEvent{key=179,o=[Buzz for P=1]}
XX GameEvent{key=179,o=[Buzz for P=1]}
Awoken!
CX buzz: [Buzz for P=1]
CFRAME: informBuzz 1
PROCESSINGN
PROCESSINGN
[N]###78
TPP 5
PROCESSINGN
PROCESSINGC
PROCESSINGC
[C]###67
TPP 5
PROCESSINGC
PROCESSINGH
PROCESSINGH
[H]###72
TPP 5
PROCESSINGI
PROCESSINGI
###73
TPP 5
PROCESSINGH
PROCESSINGI
PROCESSINGR
PROCESSINGR
[R]###82
TPP 5
PROCESSINGR
PROCESSINGE
PROCESSINGE
[E]###69
TPP 5
PROCESSINGE
PROCESSINGN
PROCESSINGN
[N]###78
TPP 5
PROCESSINGN
CX sending keepalive
KeepaliveThread << net.MessageToServer$Keepalive@8f03a5
CX sent keepalive
Patience out
Awoken!
CX got answer from iface, sending
ClientGame179 << GameEvent{key=179,pos=1,o=net.ConundrumEvent$Answer@bbddbf}
CX awaiting guess response
ClientReceiveThread >> GameEvent{key=179,o=net.ConundrumEvent$IncorrectNoContinue@127669d}
RX GameEvent{key=179,o=net.ConundrumEvent$IncorrectNoContinue@127669d}
XX GameEvent{key=179,o=net.ConundrumEvent$IncorrectNoContinue@127669d}
Awoken!
CX got guess response: net.ConundrumEvent$IncorrectNoContinue@127669d
Awaiting solution
ClientGame179 << GameEvent{key=179,pos=1,o=net.ConundrumEvent$End@bf591c}
CFRAME: informDeclaration P1 guessed ENCHIREN on 2938 ms: Incorrect
Read 1590 bytes.
******************** READ 1590 ******************
Awoken!
Round ended on 17485 ms
AWT-EventQueue-3 << net.MessageToServer$RequestGamesInProgress@11c0042
ClientReceiveThread >> net.MessageToClient$GamesInProgressUpdate@154fe09
RX net.MessageToClient$GamesInProgressUpdate@154fe09
XX net.MessageToClient$GamesInProgressUpdate@154fe09
Exec delta: +[1334265338962678412: net.GameSummary@f21c39]
Exec delta: +[1021225286531006426: net.GameSummary@11b12e1]
Exec delta: +[-4063130829204127745: net.GameSummary@74a7af]
Exec delta: +[-8228375940650212652: net.GameSummary@ad0bd6]
Exec delta: +[-6015528760004975967: net.GameSummary@e44d85]
ClientReceiveThread >> net.MessageToClient$GamesInProgressUpdate@d20b73
RX net.MessageToClient$GamesInProgressUpdate@d20b73
XX net.MessageToClient$GamesInProgressUpdate@d20b73
AWT-EventQueue-3 << GameEvent{key=179,pos=1,o=net.BlockingNetworkLayer$Poison@135fd95}
Logging out of #179
Awoken!
{ClientGame179} CXPLAY
java.io.IOException: net.BlockingLayerInterruptedException: java.io.IOException: Stream ended (poison object extracted)
at util.Channelplexer.take(Channelplexer.java:101)
at net.client.ClientRoundConundrum.play(ClientRoundConundrum.java:124)
at net.client.ClientGame.play(ClientGame.java:82)
at applet.frontend.MainPanel$1.run(MainPanel.java:95)
AsyncDespatcher << net.MessageToServer$SubscribeEvent@a3c69a
CX sending keepalive
KeepaliveThread << net.MessageToServer$Keepalive@cc87c1
CX sent keepalive
thread applet-applet.frontend.MainApplet << net.MessageToServer$Goodbye@5347c3
Layer closed
{AsyncDespatcher} Async message despatch error
java.lang.InterruptedException
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(Unknown Source)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(Unknown Source)
at java.util.concurrent.LinkedBlockingQueue.take(Unknown Source)
at net.client.CXInfoClient$AsyncDespatcher.run(CXInfoClient.java:57)
That was the bad thing: java.lang.InterruptedException

Paul Howe wrote:In light of these distressing reports, I think it's only fair to give everyone who missed yesterday's conundrum 0 points.

I agree

Actually, I was a little shocked, not because it was easy but 2/61 with some of the best conundrummers around is surprising. I'm sure that I have been the grateful recipient of points before when I have scored 0 but 59 pts for being rubbish

I've possibly had the same problem today as others did yesterday with the duel. I locked up after the final round. The main text said I'd completed, but the duel window didn't finish.
While that was there, I still managed to play a couple of games which terminated correctly.

Howard Somerset wrote:I locked up after the final round

Oooh, that arthritis getting worse?

Howard Somerset wrote:I've possibly had the same problem today as others did yesterday with the duel. I locked up after the final round. The main text said I'd completed, but the duel window didn't finish.
While that was there, I still managed to play a couple of games which terminated correctly.

I did as well, the window hadn't closed and seemed like it wouldn't. However, unlike yesterday's duel, it did pop up in the game browser afterwards. I did get the conundrum though and I have a console report to prove it if needed.

Has anyone had this problem against other bots or is it just the Duellist?

Charlie Reams wrote:Number of people who submitted any actual bug reports: 0.
Number of bugs I can therefore do anything about: 0.

A fair point, but it wasn't entirely obvious that anything untoward had happened at the time.

Charlie Reams wrote:Number of people who submitted any actual bug reports: 0.
Number of bugs I can therefore do anything about: 0.

Actually to be fair Charlie I did make a comment to you on msn at the time, though you were unavailable.

Ben Wilson wrote:

Charlie Reams wrote:Number of people who submitted any actual bug reports: 0.
Number of bugs I can therefore do anything about: 0.

Actually to be fair Charlie I did make a comment to you on msn at the time, though you were unavailable.

That's not a bug report. This is a bug report.

Charlie Reams wrote:Has anyone had this problem against other bots or is it just the Duellist?

First time this has happened to me that I know of (i.e. "finishing" a game but everything locks up after clicking "end round" after the last round). The only different thing I can think of is that the duel was one singular round; not a format I ever otherwise play.

(Having said that, I just played a single conundrum against Prune and had no issues).

Simon Myers wrote:

Charlie Reams wrote:Has anyone had this problem against other bots or is it just the Duellist?

First time this has happened to me that I know of (i.e. "finishing" a game but everything locks up after clicking "end round" after the last round). The only different thing I can think of is that the duel was one singular round; not a format I ever otherwise play.

(Having said that, I just played a single conundrum against Prune and had no issues).

My current theory is that it's related to the Duellist buzzing in with the wrong answer, which no other bot can do. Did anyone playing yesterday's Duel not buzz and still experience this problem?

Charlie Reams wrote:

Simon Myers wrote:

Charlie Reams wrote:Has anyone had this problem against other bots or is it just the Duellist?

First time this has happened to me that I know of (i.e. "finishing" a game but everything locks up after clicking "end round" after the last round). The only different thing I can think of is that the duel was one singular round; not a format I ever otherwise play.

(Having said that, I just played a single conundrum against Prune and had no issues).

My current theory is that it's related to the Duellist buzzing in with the wrong answer, which no other bot can do. Did anyone playing yesterday's Duel not buzz and still experience this problem?

Ah but I had the same problem in today's duel and I got the final conundrum right, therefore the Duellist wouldn't have had cause to buzz.

Ben Wilson wrote: Ah but I had the same problem in today's duel and I got the final conundrum right, therefore the Duellist wouldn't have had cause to buzz.

It's not the same problem though because, as you said, today's Duel got saved correctly whereas yesterday's didn't.

Charlie Reams wrote:

Simon Myers wrote:

Charlie Reams wrote:Has anyone had this problem against other bots or is it just the Duellist?

First time this has happened to me that I know of (i.e. "finishing" a game but everything locks up after clicking "end round" after the last round). The only different thing I can think of is that the duel was one singular round; not a format I ever otherwise play.

(Having said that, I just played a single conundrum against Prune and had no issues).

My current theory is that it's related to the Duellist buzzing in with the wrong answer, which no other bot can do. Did anyone playing yesterday's Duel not buzz and still experience this problem?

I can't remember if the Duellist buzzed, and I'd err on the side of him not having done. It's possible that my getting it wrong after the time caused a conflict when the Duellist had to buzz but time had run out?

Kai Laddiman wrote:

Howard Somerset wrote:I locked up after the final round

Oooh, that arthritis getting worse?

And I'd been hoping it wasn't noticeable.

Hmm, seems Dan Van, Oli Garner and Charlie (maybe amongst others) had different rounds for rounds 5 6 and 7 at least. How odd.

Kirk Bevins wrote:Hmm, seems Dan Van, Oli Garner and Charlie (maybe amongst others) had different rounds for rounds 5 6 and 7 at least. How odd.

If it helps crack the mystery - my duel hung after I guessed the first conundrum incorrectly, so I exited the server and resumed the duel. If it happens again I'll try and log a report.

Dont know if anyone else is experiencing the same problems today. When I buzzed on the last conundrum and got it wrong, the remaining time went to the dualist. However, the full music played again and the dualist didn't didn't buzz. I closed to window using the cross instead of the bad at the bottom. Does that mean my duel today doesnt count, and if so would it be possible to have it reset so that I can run the conundrum again - not to see if I can get it - but just to close the window properly. Thanks if you manage to read this , Charlie!

Barry Evans wrote:Dont know if anyone else is experiencing the same problems today. When I buzzed on the last conundrum and got it wrong, the remaining time went to the dualist. However, the full music played again and the dualist didn't didn't buzz. I closed to window using the cross instead of the bad at the bottom. Does that mean my duel today doesnt count, and if so would it be possible to have it reset so that I can run the conundrum again - not to see if I can get it - but just to close the window properly. Thanks if you manage to read this , Charlie!

Your duel's been recorded on the game browser so it'll have gone in properly, no need to worry. Unless Charlie says otherwise, of course.

Surely drafty is a word? Admittedly I was probably thinking of draughty at the time, but surely drafty is an acceptable alternate spelling? No?
I'd've won yesterdays dual were it not for that.

Neil Zussman wrote:Surely drafty is a word? Admittedly I was probably thinking of draughty at the time, but surely drafty is an acceptable alternate spelling? No?
I'd've won yesterdays dual were it not for that.

No. Frayed knot. DRAFTY is explicitly listed as a US spelling of DRAUGHTY.

Saturday's duel appears at a cursory glance to have used at least three different sets of letters! I noticed the different maxes from round nineteen.