I occasionally ask ai about code, but I don’t consider my stuff to be ai generated. I find that ai can only write simple functions - it makes mistakes more often than not with anything complicated. I’ve found ai helpful for learning some formatting and for immediate feedback (though the feedback itself is often useless). Often just typing out your issue can help you figure out what to do next, regardless of whether you send the message to ai or not.
To make code for fegba, you generally need to learn how to use the decomp, no$gba, febuilder, etc. and ai can only fill in some basic gaps in your knowledge. If you aren’t interested in learning to code, I don’t think you’ll really get anywhere with just ai generated code anyway.
I’m not worried about sloppy code on this forum personally - plenty of that already exists (and was not written by ai), yet people still use it. I’m not interested in drama by calling out specific people’s hacks as buggy, but I’ve had to fix enough things from a variety of wizards that I can confidently say that playtesting the code is often an afterthought, with the bare minimum done. No judgment here, as I’m also included in this - there have been many times that users have reported bugs to me after I’ve released code, and while I’ve usually gone back to try and fix these issues, there are some things I’ve never fixed, and probably more bugs that just haven’t been discovered.
Even things that have been extensively tested can suddenly break when in a new environment. It’s taken me years to anticipate and navigate around which patches might conflict with what I’m making, and I still end up releasing things that just don’t work or break things if you have certain asm hacks installed. I don’t think there’s an easy way to know if code wasn’t tested very well before release, nor to enforce this sort of rule, so I don’t personally support this rule. There are so few people who release custom code with any regularity that I’d also worry about discouraging these people. It’s ultimately up to the user to try the code themself and to figure out if it causes issues and/or if it’s worth using. If you install a bunch of patches at once, then spend a few weeks creating chapters before testing only to discover that the game now freezes from x action, that’s on you. Any time you install something, imo you should be prepared to uninstall it later or to revert to a backup if needed.
For community projects like skillsys, I do think code needs to be scrutinized more before being merged, as PRs (without ai code) have sometimes introduced new bugs, but at the end of the day, this is just a hobby, and we aren’t held to professional standards.
I personally haven’t noticed ai code as an issue around here, and I’m against strict rules about it. If you want to ban ai art, though, be my guest lol.