majmalphunktion wrote on Jul 25^th, 2016 at 9:07pm:



Single Window Fighting - designed to adversely affect the enjoyment of 100% of the player base to stop a minority from exploiting Turdbine's poor coding and quality control.

Own it.  It was your brainfart.    

Steel wrote on Jul 27^th, 2016 at 1:44pm:


Well there's new content twice a year... we have new ( Epic ) quests at least twice a year... Too bad they are just old low level quests with mobs that got the umongous HP treatment... from his point of view it still does count as new content.

I guess some people didn't even read or at least understand the highlights of the post I got dinged by mal. To really sum it up an MMO development team has virtually no actual advanced warning if the umbrella wants to kill it. That even if the game is earning more then it costs to even just maintain they may well kill it off rather then sale it and risk making a rival grow their former product.

And worse of all is a fate perhaps worse then maintenance or shutdown the fate of the unmaintained. Please look up Gotham City Imposters a MOBA that rapidly remade its cost to make and had an active player community who all can attest to one single issue it kept getting ever more unstable. This is because as soon as it was released it was ignored by WB all involved moves to other projects and the game left on steam to con people because it doesn't see a dime reinvested
D

Revaulting wrote on Jul 27^th, 2016 at 6:08pm:

My grudge is important because it's mine 

Flav wrote on Jul 27^th, 2016 at 1:45am:


He keeps posting every 4 months saying he is working on it.  Something along the lines of:

"It is hard to document how to install SQL server and set it up to work with everything, that and all the GLS and authentication server changes we need to make to accommodate it"

Fuck the people who can't figure out how to set it up, they are the ones who shouldn't be running it in the first place.

Durk wrote on Jul 29^th, 2016 at 10:54am:


I agree with you.

Either you have the required clues to install and run or you don't, if you don't have the clues, you can either learn them or just let it drop.
No point in trying to explain DBA stuff... waste of time and money... people that will try to install it will come back whining when it fails without any idea why it failed. 

Flav wrote on Jul 29^th, 2016 at 12:15pm:

Plus, documentation is unnecessary, if you release the basics the community will develop detailed instructions for you, and support anyone having problems. Like that stupid compendium thing Turdbin had (has?)- who ever used that over the wiki? The community can do it for you better, faster, and cheaper, so stop making lame excuses.

DropBear wrote on Jul 28^th, 2016 at 9:49am:

My mistake, then. Carry on.

DropBear wrote on Jul 28^th, 2016 at 9:49am:

Come on, now. When did I suggest anyone here is using their time well?

That may have been sarcastic. Just maybe.

Quis wrote on Jul 30^th, 2016 at 10:25pm:



Shit like this make me laugh so fucking hard. You're so fucking wrong it's hilarious.

Sailias wrote on Jul 31^st, 2016 at 12:07am:


Agreed.  I learned a lot time ago to not make comments about how easy it would be to maintain code that I didn't write and have I've never actually seen.  Any consultant or PM that takes a quick glance at the UI/surface view and does no code review or due diligence but claims "all the problems are because your previous/current team was a collection of stooges and I can clean this up in no time" is talking out their ass and should definitely not be trusted.

That doesn't mean that your previous/current team isn't a collection of stooges.  It just means that the solution complexity and effort (and thus time frame and budget) isn't actually known yet.  In fact, the bigger the stooges the creators were, the bigger the mess and the harder the fix will most likely be.   

Would you trust a mechanic that looks at a wrecked car with front end and hood damage and gives you an estimate without even looking under the hood or checking for structural damage?  I wouldn't.

Quis wrote on Jul 30^th, 2016 at 10:25pm:

I think your estimate may be irrationally optimistic, but I agree with the general sentiment. They could even go with the PlaneShift model where the code is open source but the assets are proprietary so they would benefit from community coding while still having a product to sell.

But that would require mastery of source control basics, a subject Turbine has repeatedly proven utterly unfamiliar with.