S L R book I remember when there was a glitch in the first S L R book that cost 10 $ . You could simply not buy the book but if you viewed it from Eververse it would award you the items from the book. This problem was fixed immediately , were other simple problems the community had asked for were ignored. The point is they got there ass in gear because it was there sweet precious eververst that had a bug ! Argument closed.

I feel for you dude, trying to see logic amongst this crowd. The end result for having a little intelligence and reason is being told you’re a fan boy.

"A little intelligence" being the key phrase. His statement is broad and ignores all of the data regarding Bungle's long history of fixing things at a glacial pace, and all the data on others that perform so much better. A blanket generalization that is either misinformed or willfully ignoring facts is not an intelligent statement.

No-one gives a damn about anything but results. That's the problem. And I see it a lot, usually from end-users and management types. They don't see how much or little goes on behind the scenes and just don't care. If you don't get it right, you're clearly being lazy or incompetent. Doesn't matter whether you try one thing and give up or spend ages trying dozens of things and just having the solution evade you. I've [i]seen[/i] situations like this one before. Both on the "I'm troubleshooting something for someone else" side [b]and[/b] the "Someone else is trying to fix something for us" side. And as to why things can slip through testing? I've known things work perfectly on a test system, or even on a live system, and then have something unexpected happen once it's put live on another. Or the fix that introduces a new (or previously solved) bug. Which probably won't become evident until that fix is merged in. And if you can't find another fix in time, you're left figuring out which of the conflicting fixes is needed more than the other. ([b]Note:[/b] Not always the one you would [i]prefer [/i]to keep - or the users, for that matter) And let's just be glad that, as far as we know, they've not had to deal with [i]an issue that happens every day without fail - but only after 12-24 hours after the last restart[/i]. Those are a real pain in the hindquarters to resolve. Especially when the dev thinks they've fixed it, upload the patch to your system and you come in the next morning to see a display stuck on and end-of-day screen. And then they have to figure out what's different between the system the fix worked on and the one it didn't. And it [i]still [/i]takes about a day to reproduce each time. It sucks balls and, in an ideal world, really shouldn't happen. But it does.