Andon wrote on May 7^th, 2012 at 12:12pm:


Yes.

Reinstall ddo instead of making a thread about this.

It means you have successfully bought all the useless shit from the ddo store.

You have graduated to buy the useless shit from the lotro store.

Congratulations

Hi Welcome

You appear to be new here. The first thing you should know is that we are not friggin' pansies here. You can spell out 'the fuck' instead of using some lame, filter-evading 'dafuq'.

We try to keep a certain standard of discourse here. Please comply or Epoch may break out his phosphorous.

Vissarion wrote on May 7^th, 2012 at 2:55pm:


I think it's a meme thing.

Vissarion wrote on May 7^th, 2012 at 2:55pm:


Lrn2spell, noob!  It's thesaurus, not phosphorus.

Schmoe wrote on May 7^th, 2012 at 1:01pm:

I snorted! 

Ugh. I got hit by this one too. Spent about 3 hours last night trying anything I could to fix it while I re-downloaded the client.

None of the tricks on the knowledge base worked, my ticket through tech support was useless, as it just linked me to the knowledge base...as far as I can tell, all they'd have to do is put up download links to the correct TurbineInvoker.exe.config and TurbineLauncher.exe.config (which are the files they fucked up) and everything would be hunky-dory. It's possible that a .reg file would need to be distributed too, I'm not sure. Sadly, the files in the backup folder and the ones on my LlamaLand install do not work.

I *hate* fucking downloading this crap on my limited bandwidth, but the old high res installer I had DIDN'T WORK EITHER. >.<

What a clusterfuck.

So my tech support ticket got me nowhere, through no fault of the tech support people, I fear, but this made me cringe.

Quote:


And that, right there, tells me that Turbine is NOT, in fact "powered by our fans", unless they only mean in the "you guys pay money so we can keep the lights on" sense.

I ran a few scans in whatchanged.exe but I didn't think to do it BEFORE I started altering files, so I have nothing concrete to post on precisely which files were the problem. >.<

That's what I get for attempting to patch after 3 hours of sleep over two days. Operating on 0 cylinders makes for bad IT thought processes.


Oh well,  unless the person responsible got fired (I'm hoping not, I'm guessing it was a lotro employee working long hours too, since they're pulling lotro devs to finish this expansion) I imagine this will crop up again, just due to shitty version control so I can spot it then and write up the fix someone else should have spent time figuring out.