Quite ridiculous that players with 3m gp are in the top10 kyber 1 in GA. This was first reported in decembre 2023. Why is it still the case 4 month later?

hey those players obviously are high skilled."skillrating" is the name. they are just so good

"LordSlugger;c-2463151" wrote:"Sdtbarbarossa;c-2463140" wrote:hey those players obviously are high skilled."skillrating" is the name. they are just so goodLollllLet me show you what i mean because i don't think you understand the problem...1st pick a guy at position 72nd pick, the guy who should be 1st but at positi9n 14th...It is simply impossible.yea that 3M GP guy definitly outsmarts the 14M GP guy. Thats why.

"Wed_Santa;c-2463178" wrote:This has been discussed in a couple of previous threads. It’s a legacy issue from the switch between the old and new ranking system. I thought this only started happening when they started the new squish a few months back, unless that's what you meant by "new ranking"?

"Wed_Santa;c-2463178" wrote:... it’s not a bug - it’s just working as unintended.Not to go too off topic, but what is your definition of a bug, then? There seems to be a few folks with extremely narrow definitions of "bug" that fly in the face of how I've seen the term used--both professionally and casually.

"Ragnarok_COTF;c-2463188" wrote:"Wed_Santa;c-2463178" wrote:... it’s not a bug - it’s just working as unintended.Not to go too off topic, but what is your definition of a bug, then? There seems to be a few folks with extremely narrow definitions of "bug" that fly in the face of how I've seen the term used--both professionally and casually.At danger of going on esoteric tangent (I guess that’s less of a crime as the forum only has 3 days’ of life left) I would define a bug as a situation where the intended machine logic does not function (eg due to an unidentified flaw in the code etc). In this case, I’d argue the machine logic works but there is an unintended consequence. That’s not so much a bug in the code as in the wetware (and not so much we can do about that). But my interpretation of what happened in this case is speculative (which is much more fun than labouring through the code to see what actually happened - clearly a philosophy shared by our friends at CG) - so happy to consider the possibility that it may be a bug. In which case it’s like that bug that makes people like cats - hard to make sense of but it won’t actually do any harm.

Will the GA ranking problem be adressed soon?

20 Replies

barbarossa5
Seasoned Ace
1 year ago
hey those players obviously are high skilled.

"skillrating" is the name. they are just so good
LordSugger
Seasoned Traveler
1 year ago
"Sdtbarbarossa;c-2463140" wrote:
hey those players obviously are high skilled.

"skillrating" is the name. they are just so good

Lollll

Let me show you what i mean because i don't think you understand the problem...

1st pick a guy at position 7
2nd pick, the guy who should be 1st but at positi9n 14th...

It is simply impossible.
Whatelse73
Seasoned Ace
1 year ago
"LordSlugger;c-2463151" wrote:
"Sdtbarbarossa;c-2463140" wrote:
hey those players obviously are high skilled.

"skillrating" is the name. they are just so good

Lollll

Let me show you what i mean because i don't think you understand the problem...

1st pick a guy at position 7
2nd pick, the guy who should be 1st but at positi9n 14th...

It is simply impossible.
Range1974
Seasoned Ace
1 year ago
You assume the ranking is based on something like highest skill points or most wins. Maybe the ranking is based on something completely illogical.
barbarossa5
Seasoned Ace
1 year ago
"LordSlugger;c-2463151" wrote:
"Sdtbarbarossa;c-2463140" wrote:
hey those players obviously are high skilled.

"skillrating" is the name. they are just so good

Lollll

Let me show you what i mean because i don't think you understand the problem...

1st pick a guy at position 7
2nd pick, the guy who should be 1st but at positi9n 14th...

It is simply impossible.

yea that 3M GP guy definitly outsmarts the 14M GP guy. Thats why.
Calgacus66
Seasoned Ace
1 year ago
This has been discussed in a couple of previous threads. It’s a legacy issue from the switch between the old and new ranking system. It generates an odd pool of underpowered players at the top end of the ladder but it’s not a bug - it’s just working as unintended.

It’s a bit of a pain for those 14m tryhards who get knocked off the top spot by some casual player returning to the game after a couple of years living in an ashram- but otherwise doesn’t affect the price of eggs.
M0st1yHarm1ess
Seasoned Ace
1 year ago
"Wed_Santa;c-2463178" wrote:
This has been discussed in a couple of previous threads. It’s a legacy issue from the switch between the old and new ranking system.

I thought this only started happening when they started the new squish a few months back, unless that's what you meant by "new ranking"?
ccmoose
Seasoned Ace
1 year ago
"Wed_Santa;c-2463178" wrote:
... it’s not a bug - it’s just working as unintended.

Not to go too off topic, but what is your definition of a bug, then? There seems to be a few folks with extremely narrow definitions of "bug" that fly in the face of how I've seen the term used--both professionally and casually.
Calgacus66
Seasoned Ace
1 year ago
"Ragnarok_COTF;c-2463188" wrote:
"Wed_Santa;c-2463178" wrote:
... it’s not a bug - it’s just working as unintended.

Not to go too off topic, but what is your definition of a bug, then? There seems to be a few folks with extremely narrow definitions of "bug" that fly in the face of how I've seen the term used--both professionally and casually.

At danger of going on esoteric tangent (I guess that’s less of a crime as the forum only has 3 days’ of life left) I would define a bug as a situation where the intended machine logic does not function (eg due to an unidentified flaw in the code etc). In this case, I’d argue the machine logic works but there is an unintended consequence. That’s not so much a bug in the code as in the wetware (and not so much we can do about that).

But my interpretation of what happened in this case is speculative (which is much more fun than labouring through the code to see what actually happened - clearly a philosophy shared by our friends at CG) - so happy to consider the possibility that it may be a bug. In which case it’s like that bug that makes people like cats - hard to make sense of but it won’t actually do any harm.
Calgacus66
Seasoned Ace
1 year ago
"PeachyPeachSWGOH;c-2463186" wrote:
"Wed_Santa;c-2463178" wrote:
This has been discussed in a couple of previous threads. It’s a legacy issue from the switch between the old and new ranking system.

I thought this only started happening when they started the new squish a few months back, unless that's what you meant by "new ranking"?

I had thought it was the Squish when we were discussing it in January (I don’t really like the Squish or any Bayesian shenanigans which tend to throw up more problems than they solve) but the following comment from @StarSon sounded convincing to me:

"StarSon;c-2455496" wrote:
"ZaneMorell;c-2455495" wrote:
That is so bizarre. Guess CG is finally going to have to show their math on how they actually calculate rankings.

Unless it’s not wai.

No they don't, because it's not a squish and has nothing to do with calculations. These are just accounts that had that SR before they changed things and then they didn't join for a long time. Now they are joining GAC but sitll have an inflated SR so get put at the top of K1 (and sprinkled elsewhere as well). They'll fall quickly enough, though it's still a super bummer for the people that don't get the easy wins up there.