ImO, the goal is to find the statistic cheaters will skew since they are cheating.

Lets say, one is wall-hacking in Counter-Strike. In Counter-Strike, many maps have a central location/lane called "mid". There is often a kind of mind-game of limited information going on:

  - Does 0, 1, or both teams have an AWP(=one-shot kill sniper)
  - Is the enemy sniper guarding mid?
  - Which entrance to mid is the enemy sniper currently watching?
  - Has the enemy sniper guarded mid in the beginning, but has now left?

If you can accurately dissect/classify/log player behavior, I expect the statistics to look similar to those of poker players who cheat and know the cards of the other players on the table: https://media.pokertube.com/uploads/2025/12/5d96fe17d39043a0...

  |gap      |gzip      |bz2  |lzma    | 
  |---------|----------|-----|--------|
  |0        |2.7%      |18.9%|  *0.9%*| 
  |8 KB     |2.4%      |17.8%|   0.9% |
  |*40 KB*  |*94.4%*   |17.7%|   0.4% |
  |1 MB     |*104.3%*  |19.7%|  *0.9%*|

  | I would like to respond because you're speaking authoritatively but this is mostly your opinion.

  | Indeed. The goal is to reduce cheating to a manageable level. It is impossible to eliminate.

  - dont trust the client
  - really dont trust the client
  - support / let customers host the servers (they are the ones who will put in the time required to deal with cheaters, and they will also be there once the devs/publisher have abandoned a game)
  - Use statistics a lot more: mark outliers for review, and until review, aggressively move them to their own matchmaking bracket. 
  - Implement a "demo"-style replay format for matches/sessions (which therefore contains all inputs of all parties). Make all "ranked" or eq. matches publicly available (no names/chat, just the gameplay) and people will develop tools in their free time to detect cheaters.

  | Ryzen 7 and an AMD GPU

If Zen3+ vs Zen3 is a significant architectural difference, than it would slightly miss the 5 year mark, since it was released 4.5 years ago.

It does not affect "multiplayer" in general, to the contrary, most multiplayer games are not affected (coop games, MMOs, RTS).

  | It's nearly impossible to play multiplayer games now without KLAC. The cheating is out of control.

  | Unfortunately this is an ideological hill that many Linux devs are willing to die on

Comments URL: https://news.ycombinator.com/item?id=49726166

Points: 3

# Comments: 0

Why? If i had the money, I would do the same.

"Why should the community trust Nexus Mods with SteamDB?"

You shouldn't have to take our word for it, so here are the commitments, in writing, that you can hold us to:

  SteamDB stays free.
  Nothing currently free goes behind a paywall.
  We don't sell your personal data.
  SteamDB keeps its own identity, site and community.
  The extension stays free and keeps working.

Serious question - what is 'dysfunctional' about 'blue cities' that works better in 'red cities'?

Why would anyone with brain give them any good will for that? I might believe them if they would give Luanti 2x the damages and gave in writing that they will pay 10x damages the next time this happens.

If you want to buy a toy that makes noise, get a non street-legal car for the race track. There is no reason why 99.9..% of the population should be required to tolerate more (street-)noise than necessary.

The U.S. reduced it by 37%, while increasing output by ... 12%.

https://ourworldindata.org/grapher/electricity-mix?tab=line&...

Also talking into considering the insane wealth disparity and the current rate of change, "coal" is just ragebait.

https://ourworldindata.org/grapher/electricity-mix?tab=line&...

We've received reports of a small percentage of Framework Laptop 13 7040 Series BIOS updates resulting in non-bootable boards and are investigating the root cause of the issue. In the meantime, in addition to replacing in-warranty Mainboards, we are making exceptions for out-of-warranty replacements where we can confirm a stable-release BIOS update caused the board to become non-bootable.

In parallel to this, we're introducing "Crisis Recovery Mode" BIOS functionality to enable a path for failed updates to be directly recoverable. Our latest Framework Desktop BIOS release includes this functionality, and we are actively bringing it to Framework Laptop 12, 13, and 16 in our upcoming BIOS

We've received reports of a small percentage of Framework Laptop 13 7040 Series BIOS updates resulting in non-bootable boards and are investigating the root cause of the issue. In the meantime, in addition to replacing in-warranty Mainboards, we are making exceptions for out-of-warranty replacements where we can confirm a stable-release BIOS update caused the board to become non-bootable.

In parallel to this, we're introducing "Crisis Recovery Mode" BIOS functionality to enable a path for failed updates to be directly recoverable. Our latest Framework Desktop BIOS release includes this functionality, and we are actively bringing it to Framework Laptop 12, 13, and 16 in our upcoming BIOS

> Naturally, I reached out to Framework support, who told me to unplug the laptop, let the battery drain, and power it back on again afterwards, hoping the laptop would recover by itself. Unfortunately, it never did, and after giving Framework a bunch of information, they informed me that since my 1-year warranty has expired, I have no option but to purchase a new Framework motherboard, which will cost at least CA$500.

This is very disappointing.

  1) Framework failed in not implementing a bootloader which takes a BIOS file on a USB-Stick and flashes it w/o requiring a working BIOS/Firmware or even a CPU/RAM. Every $70 Desktop-Mainboard worth its salt has this feature.

  2) Considering 1) and that it was an official BIOS that caused the issue, Framework should repair (replacing/re-flashing the BIOS chip) for shipping fees max.