• Maalus@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    20 days ago

    If you have a broken save, and a dev personally fixes the issue, then repairs your save and sends it back - that’s not something that “every gaming company has”. You are conflating “reporting a bug that gets reported by 3000 other people and gets fixed” with “a dude with 600hrs in the game has an issue that makes him unable to play further. Let’s fix it for him specifically because he put so many hours into the game”.

    • SchmidtGenetics@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      7
      ·
      edit-2
      20 days ago

      Yes that’s what happens in most cases….

      Using your Example, they actually specify they don’t deal with the issue your brought up!.. holy shit dude, read the article and maybe know what you’re talking about here…?

      So what issues would they deal with and why aren’t you dealing with any points that address the actual topic and keep going off on unrelated topics?

      WOW also wouldn’t need your save since it’s all online, but games without online saves ask for your save. Maybe this is what’s confusing you about submitting them? Online is automatic lmfao.

      • stringere@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        7
        arrow-down
        1
        ·
        20 days ago

        At least when you’re wrong about something you’re willing to keep doubling down and not see how!

        • SchmidtGenetics@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          3
          ·
          edit-2
          19 days ago

          The good news is that Griffiths managed to save the player’s, uh, save. In a further update, he posts a video of the game running flicker-free in the same area on the same save. Per Griffiths, the problem was a “general engine bug/limit being reached,” which means that his fix will “probably help other large bases that had this issue on Xbox.”

          So where is the save being sent back for an engine issue….? This specific fix had nothing to do with fixing a specific save issue, they got sent a save that HAD the issue, and used that to fix a generic issue. Why is everyone going on about this being a save fix?

      • Maalus@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        arrow-down
        1
        ·
        20 days ago

        Dude you didn’t even read what I said and defaulted to saying the same stuff you said earlier. Replying to you is pointless - you’re doubling down when you are wrong and basically just talking to yourself. I don’t know why either - don’t lile NMS? I don’t like them either. But I will give credit when it’s due.

        • SchmidtGenetics@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          3
          ·
          edit-2
          19 days ago

          I read what you said, and you still haven’t read the article with the argument you keep going on about.

          The good news is that Griffiths managed to save the player’s, uh, save. In a further update, he posts a video of the game running flicker-free in the same area on the same save. Per Griffiths, the problem was a “general engine bug/limit being reached,” which means that his fix will “probably help other large bases that had this issue on Xbox.”

          So how is this anything about using personal assistance with a save…? They used the save to fix a generic bug, which is what I was originally talking about until you derailed the topic with your bullshit.

          So again, did you ever. Read the bloody article…? Because nothing you’ve talked about is related to it…