Don't worry, if he's tested enough, and is actually learning off it, It's a great tool and people aren't going to bash them for that (source: no one ever told me anything about me admitting to have used AI in my Quake 3 projects + some of my upcoming projects, with the permission of the authors, have absolutely no problem in me using AI to link some stuff).
Projects like this fall on GPL most of the time, so he's allowed to use AI and redistribute (not sell, though) them. There's no license on the OG website, and the "reuploaded" Source is basically on the same boat there. No license. But I highly think It's GPL. May need to wait for more confirmations.
Since you're new at this, I highly advice you to learn a tiny bit of Git. Especially how .gitignore works.
People will bash AI for writing code yet pretend that people didn't steal/copy codes off StackOverflow before AI became an accessible tool lmaoYou don't need to tell people that you're using it.
If you were using lots of caffeine or methamphetamine to program faster, it doesn't matter
If AI did all of the work for you, and you're taking the credit, that's something else... still impressive though, and the product can still be good.
But if you are simply using AI to help, no problem at all.
Okay so I decided to add to the reame.md to make the attribution more robust since i absolutely don't want to take credit or clout for adding mappers. what'd have been dishonest if i were to say it's my own work, but at least here, people know that I used AI to help, and this is my first time ever using AI to update emulators.You don't need to tell people that you're using it.
If you were using lots of caffeine or methamphetamine to program faster, it doesn't matter
If AI did all of the work for you, and you're taking the credit, that's something else... still impressive though, and the product can still be good.
But if you are simply using AI to help, no problem at all.
I just have git add the new files individually. i always make sure never to add the roms or any compiled builds.
Just add the bare minimum that will output a working build. README.MD and LICENSE handle the rest. Comments will handle what specific lines of code do.
"To compile pocketnes.gba:
I saw the README. You can make it a bit nicer using # (for big texts) and ## for smaller texts, in case. You may also use this to make it a bit nicer. https://readme.so/
Please add compiled builds... Nobody likes setting up build environments on their system just to get a file they could have easily downloaded instead.
Ok so you used a couple resources but one of them kind of looped and crashed out while the other had a good backbone for creating the requested additions you sourced online such as the various mapper files while asking for bug corrections pull from the pulls of the existing code.
