• SchmidtGenetics@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    26 days ago

    No, but they tweeted what they did, it didn’t have to made public by the dev, but they obviously did it for the viral marketing, and then an article picks it up and here we are. Someone is being accused of saying an article is commissioned lmfao.

    If every dev that did this tweeted about it, yeah you would hear about it more, but most devs have better things to do than get some stupid marketing for things almost every dev already does.

    So I ask you, why else would someone tweet about a mundane thing like fixing a bug?

    • modifier@lemmy.ca
      link
      fedilink
      English
      arrow-up
      3
      ·
      26 days ago

      Who is they?

      To my knowledge, an individual NMS employee with no named affiliation in his handle tweeted about the situation, certainly with a note of personal pride. Is that what you find inappropriate? That a person was individually proud of something that you find unremarkable?

      Because if HelloGames has been pushing this beyond a retweet or something, I wasn’t aware.

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

        The dev who the article was about…? Who else would “they” be in this context?

        So they posted to social media for clout? That’s an even worse take.

        And no it was a specific dev… did you even read the article?

        . As No Man’s Sky engine programmer Martin Griffiths details over on X

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

        Actually in this specific case it wasn’t even that…

        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.”

        The save helped with it, exactly like I’ve been saying this whole time.