dev_null

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.

That’s incorrect. The Steam AI badge only concerns gen-AI assets, not code. So UE or middleware that was coded with AI doesn’t make the game need the badge at all. Whether you agree with that or not is another thing, but that’s the current Steam rules. AI disclosure is only for assets, not code.

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.

In 2019, not last year. In 2019 they started releasing deobfuscation mappings so that any modder can get the deobfuscated code if they want by applying the mappings. That was the big change. Last year they stopped obfuscating the code in the first place, but that didn’t change anything, just removed a simple step to modding of not having to use their mappings anymore.

Same here, and currently Let’s Encrypt is a central point of failure for my stuff. I don’t use any Cloudflare services, so adding it as a fallback for Let’s Encrypt seems like a good option to have.

Ohh, looks nice too. The more the merrier I guess.

How is that worse than now? Right now Let’s Encrypt is a single point of failure, if I can setup my certs to go Let’s Encrypt and then if Let’s Encrypt is down go to Cloudflare, then surely that’s better than not getting a cert at all when Let’s Encrypt is down.

It’s more redundancy. Am I missing something?