Message me any time in game.
Matchmaking: Huh?
Message me any time in game.
Looks like the matchmaker found a bunch of players with short character names.
Nothing to see here folks, everything’s working as intended.
to be faceroll at the high levels, because it
needs to be accessible to the casuals and bads.
Found a missing ‘+ 1’ (literally) in the matchmaking code. Will get this fixed soon.
In the mean time, it doesn’t factor in 2 of the same profession, only 3+.
Isle of Janthir: Flux, Latch, Aegir
(edited by Justin ODell.9517)
Found a missing ‘+ 1’ (literally) in the matchmaking code. Will get this fixed soon.
In the mean time, it doesn’t factor in 2 of the same profession, only 3+.
yeah and what about 4 like some ppl posted..
In the mean time, it doesn’t penalize 2 of the same profession, only 3+.
Well, I don’t know… this isn’t suppose to happen twice in a row, right?
http://i.imgur.com/C5YZOZw.jpg
http://i.imgur.com/xJg8pU6.jpg
Found a missing ‘+ 1’ (literally) in the matchmaking code. Will get this fixed soon.
In the mean time, it doesn’t factor in 2 of the same profession, only 3+.
Glad you found a fix, and from my own experience coding for grad school I know how easy it is for syntax errors to sneak into code. Just curious (and I hope I’m not being rude) how do those kind of syntax errors make it through multiple layers of QA?
So you literally didn’t test queueing with two of the same class? WTF?
Or they did test it on different configurations and went to live on the wrong config
Norn Guardian – Aurora Lustyr (Lv 80)
Mia A Shadows Glow – Human Thief (Lv 80)
yeah and what about 4 like some ppl posted..
4 is treated as 3, which has score reduced by 2 * scorePerCommonProfession.
3 is treated as 2, which has score reduced by 1 * scorePerCommonProfession.
2 is treated as 1, which has no score reduction.
If you take a look at the wiki the score penalty isn’t that high, and it was being made to have even less impact because of this bug.
http://wiki.guildwars2.com/wiki/PvP_Matchmaking_Algorithm#Configuration_2
Tomorrow I’ll up the penalty when I get the bugged fixed, see if that set’s it right.
If it doesn’t work, I’ll also see about changing it to an exponential calculation.
Isle of Janthir: Flux, Latch, Aegir
Found a missing ‘+ 1’ (literally) in the matchmaking code. Will get this fixed soon.
In the mean time, it doesn’t factor in 2 of the same profession, only 3+.
Glad you found a fix, and from my own experience coding for grad school I know how easy it is for syntax errors to sneak into code. Just curious (and I hope I’m not being rude) how do those kind of syntax errors make it through multiple layers of QA?
A missing +1 is a logic, not syntax, error.
And it can slip through QA if QA isn’t specifically testing for it. Doesn’t make the results any less egregious, however.
to be faceroll at the high levels, because it
needs to be accessible to the casuals and bads.
Just curious (and I hope I’m not being rude) how do those kind of syntax errors make it through multiple layers of QA?
Long story short, it’s my fault. We had bots and all that running and it was my job to validate that it was working as expected, I missed this.
Only caught the issue because I wrote a C++11 match simulator over the weekend and I was validating that it works identical to the real systems. May end up releasing the source code to that, which is why it can’t just reuse our existing C++ code.
Isle of Janthir: Flux, Latch, Aegir
You’re a good guy, Justin.
We believe in you