Hearthpwn

Just wonder, how is it possible to high legend rank with less than 30 games. Even from rank 4...

There was a bug that made players start at rank 1 5 stars and only had to play 1 game to hit legend. The current rank 1 guy hit legend and played 1 game after legend and stopped playing. The problem bug didn't hit as many N.A. but on EU there were over 3000.

This is normal. This is what professionals do. They play 24/7 and they game the system wherever possible. Otherwise they wouldn't be as "competitive" (at least in score).

I'm not that mad tbh

NO, you misunderstood, for people at legend rank, who wants points for the HCT, you need to play 30 games to be eligible for points, not "30 games an you wil be legend"

Please read and understand before comment

nope.

Meh... I'm failing to reach Legend for more than 30 games already... I have been to rank 1 3 times this month...

I wish this ''joke'' would rotate with the old sets

Where is the joke?

Quote from DiamondDM13 >>

Small Illogical Brain, is the best one can take away from anyone using that. It would be great if people all had an idea how programming works, and just how annoying it is to have issues pop up and have to fix them but trying to do so without making other issues in the meantime. It's like people don't realize almost any adjustment you make to your code can have remifications in other places and create completely different issues from the oness you were trying to solve.

Quote from DiamondDM13 >>

Small Illogical Brain, is the best one can take away from anyone using that. It would be great if people all had an idea how programming works, and just how annoying it is to have issues pop up and have to fix them but trying to do so without making other issues in the meantime. It's like people don't realize almost any adjustment you make to your code can have remifications in other places and create completely different issues from the oness you were trying to solve.

Quote from Dr_Horus >>

I wish this ''joke'' would rotate with the old sets

It sounds like you studied programming, and not software engineering, there is quite the difference between a code monkey and someone writing actual well structured software.

For a card game, it is actually way easier to write automated test cases that can run every night with expected out put and generate a report when it differs, since they don't have to show any graphics and there the move set is very restricted (you can't move in 360 degree space) hence pointing out these fixes that cause cascading bugs. They don't actually have to run the game for many of these cases, they can just lay out a sequence of events and see results, e.g. play card X in board spot 1, attack spot 2 of opponent, does menu Y die, does death rattle Z go off, whatever. Same with the ladder ranking, if player rank X fights Y with these amount of legend points, he should go up to rank Z, etc.

So, I argue that they are not using their resources very well if such small changes cause such catastrophic bugs that they never caught. I am willing to believe they let some intern deploy the patch to production and he screwed up, but I think it is just a bad code base and lack of testing...

If that is the line you want to take, I can quite simply turn that logic around on you and ask you if you can show me in their code everything that is done right, but they still change one thing and break everything else?

The fact of the matter is that there are some bugs I can understand that cause something like a graphical glitch which require running the actual graphical client and getting exactly that scenario since they are using the Unity engine that they did not develop. However, the logic related to their cards and menus suggests more of a code base that is haphazardly thrown together and difficult to maintain. For example, look at Deathstalker Rexxar not including all the beasts and then blizzard talking about how much work it would be to add it in and then finally caving on it... makes me think there is some huge if/else ladder deciding the beasts that are applicable and some weird code to assemble the text on the card for the blended beasts and then associate the different attributes to the beast like health, charge, lifesteal, etc.

All I can really say is that these random huge bugs (like ladder issue) that someone should have easily caught really make me wonder what kind of mess they have.

Quote from Tatsumasa86 >>

 

Quote from DiamondDM13 >>

Small Illogical Brain, is the best one can take away from anyone using that. It would be great if people all had an idea how programming works, and just how annoying it is to have issues pop up and have to fix them but trying to do so without making other issues in the meantime. It's like people don't realize almost any adjustment you make to your code can have remifications in other places and create completely different issues from the oness you were trying to solve.

 

 Are you a software engineer? The main idea behind this "small indie company' meme suggests that Blizzard is a small group of coders that created a horrible mess of spaghetti code that is impossible to maintain. Given that they are a large company, there is no excuse that they should not have resources to devote to a well engineered product with plenty of time to devote to regression testing. A good code base should not function like you suggested where changing one item creates a wild cascade of issues in other components... and even if it does, again refer to the regression testing they should be performing.

If you do program in such a haphazard climate every day, then you have my sympathy.

Fair enough

HAHA :P (jk if I know you)