QUOTE(The Amateur Working Bee @ Aug 2 2012, 09:41 AM)
thats funny then, if they patched or fix any shit already, what would be the RIGHT time to announce a bloody PATCH?
you are telling me you fix a shit and after you fix it, you dont tell users what the fark u fix? waiting for a right time to tell? dafuq?
its like for example Toyota recalling all their cars to fix "something" but not telling owners what they are fixing till the time is right? makes sense to you?
go check out the Starcraft2 team, they did a farking good job putting patch notes up and updated BEFORE a bloody patch is made, A-BLOODY-FULL-DETAILED-INFO, double thumbs up to the Starcraft2 team, Diablo3 team can go suck a d*** or continue smoking their pot.
chill mang chill.... since week 2 onwards we already D3 team sux bad... now u rage also no farking use... when they start to work like dis forever they will do it the same way... they wont bloody farking change their way...
the problem in D3 dev team is that they dont have a good "leader".. a good leader brings the team up no matter what shyt happens...
e.g. in a company the leader is the kind where lazy around anything / everything also later... the results? employee under him also later la... in the end no product who is the main blame? the leader...
same applies to D3... if the Leader said dont release the farking release notes / just say later only release... so the client rage no one farking care...
This post has been edited by leongkokloon: Aug 2 2012, 10:09 AM