Re: Scope of the usage, it doesn't change the overall point I was making, and I'd have made the same point had I been 100% accurate in my original response. Copy-pasting that original point for posterity: "Maybe they deemed what they did to be within the realm of acceptability. Different folks have different standards about what they deem acceptable, and different folks have different rules about what they will and won't purchase (examples I gave = minor cursing or blood). The developers didn't follow your rules, but they followed Steam's rules, which is more or less the law of the land."
Re: Blowback, I don't think your example is really a great analog for this situation, but it's also beside the overall point I was making about expected blowback: It doesn't mean that the person on the receiving end has done something that they view as wrong.
Re: The code - The implication on their part was that it was a small amount of code. Yes there's a difference, but to be totally frank I think you've positioned this as a "gotcha on a technicality" rather than addressing some of my other points. Out of curiosity, would 10 lines have been ok by your measure?
Regarding blowback, my follow-up sentence was "Whether the blowback was deserved or not is not for me to judge right here, and I don't know their actual feelings about what happened vs. the statement provided." Blowback is not always deserved. Suppose I put a bunch of anti-ICE stuff in my game. I'd anticipate some blowback from that. Would it be deserved? Depends who you ask. But I doubt it would be fun.
Yes, as I indicated there was a standard they did not meet, but what's also implied is that they didn't necessarily mean that to be THEIR standard. 10 lines or 0.1%, maybe they deemed what they did to be within the realm of acceptability. Different folks have different standards about what they deem acceptable, and different folks have different rules about what they will and won't purchase (examples I gave = minor cursing or blood). The developers didn't follow your rules, but they followed Steam's rules, which is more or less the law of the land. Which is why it's tough for me to see this as a middle finger-worth infraction.
I suppose in order to fully assess what happened I'd need to know the full context under which the statement was made. From what I understand, the developers included the AI note with a confidential IGF submission, where - from their statement - I gather the disclosure was suggested but not required. Jurors for IGF later posted about this on social media (which if true, seems like an ethical breach, but that's beside the point). Aftermath picked it up, told them they'd be writing a story on it, and asked them for a statement.
Assuming all that's true, to speculate: They knew they'd be getting a bunch of blowback, so they tried to provide further context and quell negativity. Whether the blowback was deserved or not is not for me to judge right here, and I don't know their actual feelings about what happened vs. the statement provided. As for the statement itself, the line "may not meet their standards" is pretty key. My guess, if I'm taking this at face value, is that they don't actually see what they did in this particular instance as a big deal or requiring of disclosure, and that disclosing it in the first place would have done more to normalize AI usage than the actual offense (10 lines of code) would warrant.
Of course, the tradeoff is that folks whose standards they did not meet - those who take a hard stance on any and all AI not being in their games - wouldn't be aware of it. As to whether the devs had an obligation to disclose it, I think you'd have to apply the same standards to a lot of other areas. There are any number of things that can potentially appear in games that certain people may deem inappropriate and take a hard stance on. I could be wrong about this but I don't think the presence of blood or minor profanity in a game are required to be on a store page (just a couple examples of things people might want to avoid). Maybe that should be a requirement, maybe not, but Steam says no, and that's the standard devs generally follow in regards to disclosures.
In any case, I don't think it warrants an immediate "middle finger". I don't think that does anything beyond contributing to a discourse that's already become super nasty, and it won't win you many new converts to your cause. If anything, the way this situation played out across social media seems to have provided your opposition with more ammo.
Anyways, that was long, but hopefully I was able to provide some helpful extra perspective on this. I hate seeing the vitriol around this topic, which unfortunately this platform tends to encourage.
Genuine question having not seen your stream: My understanding has been that games developed using AI exclusively on the coding side (as opposed to asset generation) are not required by Steam to disclose that usage. The note that was added to your original post includes links that appear to confirm this. Respectfully, am I missing something? If all this is true, it seems like the developers were not acting in bad faith?
@heywayfinder Oh wow, this was certainly a choice! I forget, could you turn them into bacon? If so, maybe the intent was to make them less sympathetic. Animals in SOR2 just poof out of existence when they die, death frames made me sad.
Thanks to the "extended" development of Streets of Rogue 2, my artists have had the time to produce a staggering 40+ types of fully animated animal varieties!
have a look at this SoR 2 MULTIPLAYER testing screen grab IF you welcome janky WIP stuff
also, be on the lookout for work-in-progress details that haven't been shown before
#IndieGameDev
@Devon_HD_@streetsofrogue No playable ghosts planned right now, but ya never know.
Vampires likely will be affected by being in the sunlight. I haven't started real work on that character yet
No way to be transformed into monsters, but could make for an interesting mechanic as long as it's reversible!