this post was submitted on 19 Jun 2026
115 points (99.1% liked)

PC Gaming

15101 readers
387 users here now

For PC gaming news and discussion. PCGamingWiki

Rules:

  1. Be Respectful.
  2. No Spam or Porn.
  3. No Advertising.
  4. No Memes.
  5. No Tech Support.
  6. No questions about buying/building computers.
  7. No game suggestions, friend requests, surveys, or begging.
  8. No Let's Plays, streams, highlight reels/montages, random videos or shorts.
  9. No off-topic posts/comments, within reason.
  10. Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)

founded 3 years ago
MODERATORS
UncleBadTouch@lemmy.ca
EXiLExJD@lemmy.ca
KairuByte@lemmy.dbzer0.com
115
"We wouldn't have caught the issue without it": Slay the Spire 2 gets a patch for broken RNG after player turns in gruelling eight hour video exposé (www.rockpapershotgun.com)
submitted 1 month ago by ooli3@sopuli.xyz to c/pcgaming@lemmy.ca
6 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] festus@lemmy.ca 5 points 1 month ago

Here's a write up that, eventually, gets to the RNG stuff. https://tck.mn/blog/correlated-randomness-sts2/

I think the Tl;dr though is that the way they set their RNGs up were with seed=run_seed + hash("rng instance name"); this meant that all of the rngs they used had seeds that were constant offsets to each other. The PRNG algorithm they were using (C# standard library) happens to have a property where if you shift the seed by some constant, your rng's output shifts by a linear amount corresponding to that. As a result, all the rngs for what are supposed to be independent things were basically all giving the same results just offset to each other.