Best Of

Not too strange. Just using the numbers from your screenshot, this is how the radiance breaks down by AQ placement:



We do kinda see that larger drop fro 10000 to 6500 compared to the drops at lower levels, but is it out of place? It is a bit tricky to judge, because the ranges of alliances that get each reward vary in size. Suppose we graph the radiance earned relative to the average alliance ranking that gets that particular reward:



Now that drop from 10000 radiance to 6500 radiance doesn't seem quite so odd, because it actually fits fairly well with the overall shape of the reward curve drop off. Maybe it is a tad larger than I would extrapolate, but not by a ton.

If you ask me which reward points are out of place, I would say it is most likely that 31000 should be closer to 30000 and 6500 should be closer to 7000. But those are minor deviations from the reward curve.

You said 6500 multiple times, (including saying it should be closer to 7000) but in the chart I posted, the number is 6000.

Even in the chart you presented, it looks on my tiny phone screen like the average ranking curve gets steeper *after* the top 500 then levels out again.

Based on me eyeballing the chart and the fact you said 6500 twice, I’m guessing you might have plotted that data point incorrectly, which would make it a tad more of a drop than is already depicted.

Anyway, it feels really messed up that there’s a huge incentive for the top 50 to jockey for position, then very little incentive considering the massive climb needed between 50 and 500, then a huge incentive to push into the top-500 (or keep your spot there), then minimal incentive past that.

It matters a lot. It doesn’t matter much at all. It matters a lot. It doesn’t matter much at all.

Do you guys remember how Crowdstrike bricked/bluescreened millions of servers recently?

It’s because it’s kernel level and had one bad update.

Not a chance I would install this on my main computer. Steam doesn’t use kernel anti cheat software for good reason.

1. The Steam version of MCOC also uses Easy Anti-cheat, as does other games on the platform.

2. Crowdstrike didn't brick things because it was a kernel mode driver. It blue screened Windows because it was a kernel mode driver. It pseudo-bricked systems because it was part of the boot process, so it prevented Windows from booting properly. You had to bypass it by booting into safe mode and removing the driver to allow Windows to boot properly, or in some cases boot from alternate bootable media, which was problematic for many systems where remote safe mode boot was not an easy option.

I was on a rapid response mitigation team for Crowdstrike and fixing it in real time at the time, by the way.

3. All the security software that protects people from this stuff is also implemented as kernel mode drivers, including the Malwarebytes warning that started this thread. If you don't trust kernel mode drivers, you aren't running any security protection software, which is ludicrous.