Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(+1)

I saw this come up again in the context of a post by Nifflas on Bluesky (regarding small bespoke neural nets). Thankfully in his case it was clearly ok.

But frankly I find the AI content guidelines, and the discussion here, to be completely unhelpful except in the most extreme yes or no cases. (And also very "Game centric") 

It's very easy to think of realistic use-cases that don't obviously fall either side of the tagging policy. Some examples:

  • Reproducing a large amount of public domain map data verbatim in some sort of "Atlas" application would obviously not require such a tag. But using that same data as source data for a realistic procedurally generated map would.
  • What if my game supports DLSS (or equivalents)?
  • What if one of the major gamedev tools (Unity, etc) shoves AI crap into the runtime?
  • Is it anything algorithmic using external data or just "Generative AI"?
  • Perhaps just content generated using matrix multiplication or weighted directional graphs?