• dev_null@lemmy.ml
    link
    fedilink
    English
    arrow-up
    25
    arrow-down
    2
    ·
    19 hours ago

    The Steam AI badge is specifically about gen-AI assets. A game that’s 100% vibe coded, but uses human art, doesn’t need the badge according to Steam rules.

    And while AI assistance with code is common, gen-AI assets not so much.

    • Aria@lemmygrad.ml
      link
      fedilink
      English
      arrow-up
      3
      ·
      17 hours ago

      DLSS is GenAI, but you get crucified if you don’t have it. At the same time if you report using it by applying the badge, you also get crucified. There is no widely liked game on Steam from the last five years that doesn’t have some genAI somewhere, unless they’re visibly small in scope. If you just build an Unreal or Unity sample project it’ll already have GenAI (assisted) fonts and (GenAI denoised) sound effects, and probably a lot more.

      Somehow games have transported the “No VFX” Hollywood marketing.

    • fartsparkles@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      17 hours ago

      Where does it say that? Their content survey details for when developers are meant to disclose AI usage simply refers to it as the use of AI in generating “content” which would cover code since the mechanical implementations etc are all “content”.

      A 100% vibe coded game should be disclosing as AI pre-generated content.

      • dev_null@lemmy.ml
        link
        fedilink
        English
        arrow-up
        4
        ·
        16 hours ago

        We are aware that many modern game development environments have AI powered tools built into them. Efficiency gains through the use of these tools is not the focus of this section. Instead, it is concerned with the use of AI in creating content that ships with your game, and is consumed by players. This includes content such as artwork, sound, narrative, localization, etc.

        What you linked is pretty clear to me. Tools and code are not “content”. That’s Valve’s intent.

    • saltesc@lemmy.world
      link
      fedilink
      English
      arrow-up
      6
      arrow-down
      5
      ·
      19 hours ago

      Oh, my… 100% vibe coded is excluded?!

      So basically, even if it’s okay on release, it’ll never receive an update or bug fixes, because the “dev” literally has no idea what’s actually going on.

        • saltesc@lemmy.world
          link
          fedilink
          English
          arrow-up
          6
          ·
          17 hours ago

          Just a hunch that vibe coders don’t have the patience to learn the fundamentals of how their project is actually working, let alone understand methods for fixing the back end or be good enough at using an LLM to try get it to do it well.

          Some people would use vibe coding to learn, but “laziness” is a far common occurring adjective with vibe and coded projects require a lot of patience and knowing what’s going on.