Players have been asking for the ability to filter out games made with Gen AI.
We've added an automatic tag on SteamDB based on the AI gen content disclosures on the store pages.
Disagree. They can be connected to actual game mechanics. For instance, it’s quite easy to ask an LLM to output something in json format:
{
"name": "The Master of Evil",
"hitpoints": 205,
"class": "vampire,"
}
and so on. You might object that it could make mistakes here. Suppose the detectable error rate is 10% (I actually think it’s lower from what I’ve played around with.) Rerunning it in the case of a such an error (e.g. malformed json, invalid class name, hit points exceeds bounds, etc.) reduces to 1%, then 0.1% etc., and in the end there can be a non-AI fallback just for certainty. Admittedly, the errors are not i.i.d., but still it should be pretty low. Many traditional procgen techniques, such as map generation, also use rejection sampling in this way, with even larger rejection rates than 10%.
It’s easy to generate something as generic as that, not as easy to generate mechanics. And if you don’t generate mechanics then you’re only doing fluff like I said
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]
No game suggestions, friend requests, surveys, or begging.
No Let’s Plays, streams, highlight reels/montages, random videos or shorts.
No off-topic posts/comments, within reason.
Use the original source, no clickbait titles, no duplicates.
(Submissions should be from the original source if possible, unless from paywalled or non-english sources.
If the title is clickbait or lacks context you may lightly edit the title.)
Disagree. They can be connected to actual game mechanics. For instance, it’s quite easy to ask an LLM to output something in json format:
and so on. You might object that it could make mistakes here. Suppose the detectable error rate is 10% (I actually think it’s lower from what I’ve played around with.) Rerunning it in the case of a such an error (e.g. malformed json, invalid class name, hit points exceeds bounds, etc.) reduces to 1%, then 0.1% etc., and in the end there can be a non-AI fallback just for certainty. Admittedly, the errors are not i.i.d., but still it should be pretty low. Many traditional procgen techniques, such as map generation, also use rejection sampling in this way, with even larger rejection rates than 10%.
It’s easy to generate something as generic as that, not as easy to generate mechanics. And if you don’t generate mechanics then you’re only doing fluff like I said
ah, I misunderstood by what you meant by “generate mechanics.” My bad.