The wormnet server has failed. we will be working on the problem and will update you with our progress.

An obvious act of aggression against our sovereign server that shall require an immediate and decisive response.

This means war, cleaning ladies!

Two of my two computers died today because I was raging over WormNET all the time :P
Yeah, I'm German, what did you expect???

So you turned your keyboard sideways to repeatedly smash it as hard as you could against the edge of the desk?

any updates on the wormnet wreckage??

Yeah and I screamed "It's connecting, it's CONNECTING!!! I DO NOT WANT IT TO CONNECT AAAAAAAAA"

its back online now, sorry for the rage inducing outage!

And afaik noone can join hosted games :)

its back online now, sorry for the rage inducing outage!

The game id distribution procedure is almost entirely broken. (no one can host games)

The issues had nothing to do with any "game id distribution procedure".

Should be fixed now.

Thanks for that. I bet fixing that ate the whole night?

Noone believes steps anyways so what :P
Next: Issues because of Missing-Donut-Delivery-Service; I'm-A-Teapot and Where-Are-My-Cornflakes.

Next: Issues because of Missing-Donut-Delivery-Service; I'm-A-Teapot and Where-Are-My-Cornflakes.

Please contact your HTCPCP-enabled device manufacturer if you're receiving HTTP 418 error codes.

Oh darn, and I thought I could finally send files like english-strawberry.tea to my teapot :mad:

The issues had nothing to do with any "game id distribution procedure".

from what I saw, and from the reports, the SetGameId was failing to be sent by the server.
if you have a better explanation, i'd like to hear it :)

Especially the wiki article could need some info why the server was down at all *and because I'm soooo curious!*

As I wrote on said wiki article (http://worms2d.info/WormNET_statistics#Timeline), the problem was misconfiguration.

WormNET was reinstalled on a new server, however that server's configuration (namely, php.ini) differed from the old one - namely, the setting "display_errors" was enabled. This caused PHP to send warning messages to users whenever the code did things like rely on PHP's archaic undefined-variable-to-string-literal conversion or accessing undefined array indices.

Since the "create game" request doesn't actually have any interesting data in the response body, by itself that didn't cause any problems; however, sending out a warning to the user meant that PHP had to start writing the message body, which means sending all response headers as well. Since the new game ID is being sent as a header (SetGameId), it couldn't be sent, which caused the warning "Cannot modify header information - headers already sent" to follow the others.

Sorry I didn't read the wiki article recently. And useful explanation :)
is the new server faster or something? X)