lol :)

edit: And by the way i sneaked a patch out yesterday after the discussion of the FormClosing event so it's 1.0.4 that is the current version (see first post) :)

I've decided that another project needs more work first. I'm going to write an application that randomly disconnects me from Rise of Flight multiplayer servers every few hours. It won't help me stay connected, it won't help me find out what else is doing it, but at least I'll have the satisfaction of knowing what might be causing it some of the time...

Yup. CloD isn't alone in having problems. There I was in a D.F.W., feeling smug as I'd just dropped a sample of the Kaiser's best bombs on the enemy from the astonishing height of 2,500m (RoF bombers tend to be somewhat realistic in the rate-of-climb department, in that they don't seem to have one), and heading back over the mud below. Glanced back to see what the AI gunner was doing (a crack shot, but stupid - some things never change), and he disappeared before my eyes. Along with the gun, and everything else, except a hole where his cockpit had been. And no, it wasn't some bounder in a Camel or a Spad, just a bug - that promptly lead to a message that I'd been disconnected. Yup. A statement of the obvious, with no clue whatsoever as to why. Actually, that gives me an idea. I'll write an error-message interceptor, that replaces useless generalisations ("parameter error") with ultra-specific randomly-generated ones ("Negative dividend in procedure wingFoldGammaCorrectionParseURL - preemptive stack-underflow"). Again, no use for actually fixing anything, but at least it gives the illusion that it is fixable... ;)

Lol, RoF sure have their problems too (even though it's a truly great game at heart). The first months where almost as painful as for CloD, but they did catch up to make it rather robust after a year or so... But just like you describe, the pain of dying in an unhandled exception is the worst one ;)

/mazex

Use this app :) It won't be fooled by the latest trend of necro bumping... It already "knows of" the version 14305 brought up by pencon today and the 14413 thread brought up yesterday by Foo'bar (a bit surprised by that as Foo'bar has done much good before - like those trains!)

Then of course, they have to use their previous routine for it to work, so no guarantees ;) The only guarantee is that it's "necro bumping safe" ;)

for this kind of "bloody mindedness" (the actions of a thorough meathead) - instant ban, no question, should be the response

I do agree that it's childish, but at least Foo'bar bumped "his one" with:

"Unbelievable, all this is already 1 year ago. Feels like last month."

Which I must admit was a bit funny at least - and not pure evilness like pencons comment that was just done to confuse people into downloading it. The effect of bumping the old threads is however the same but as Foo'bar selected a date that is yet to come (4:th of may 2012 is not yet here in Sweden at least) even though there was the patch thread from the 27:th of april for him to "choose from" then as pencon had not bumped it yesterday... So - I think he did that deliberately to not fool anyone into downloading it?

EDIT:

And looking at the fact that Foo'bar has actually contributed to the actual CloD game with his marvelous trains gives him some "slack" for me at least (even though it was stupid!):

His stuff:

http://fooblog.mexxoft.com/

/Mazex

New "non mandatory" version 1.0.5 - same as CloD now :)

I had some network problem this night and it retried 100 times with no success - and then it shows a message box that it's aborting before sending the email about it... So you don't get the mail until reading the message :) The "abort" mail was a last minute bonus - mental note, never add such things without testing - I know ;)