I'm seeing a lot of parenting advice here that is probably true, but has the potential for a catastrophic downside. It is likely that a 9 year old isn't intere

I'm seeing a lot of parenting advice here that is probably true, but has the potential for a catastrophic downside. It is likely that a 9 year old isn't interested in the work that goes into game dev, yes, but it is possible that any given 9 year old has a much richer understanding of the world than one might give them credit for. If your son is one of those, one of the worst things you could do is to coddle them and avoid the hard work of learning. Kids who are indicating that they're ready to expand their universe are in a fragile state of motivation, and it's easy to kill that by deciding for them "what they are capable of". Of course, you don't wanna push the issue if they're not in that place (which is also fine). Maybe _try_ treating them as a co-creator, with all the attendant admissions of what is and isn't known ("I'm not sure how we could do that, buddy, but here's where we can start looking"), and if they don't respond with the appropriate level of motivation and energy, then default to making something in roblox or whatever. To answer your specific questions: - unity is really not a bad starting point, it's very batteries included - rather than keeping the project contained, build your way up to the vision with smaller "practice" projects - start subscribing to premium GPT. For total beginners to code there really is no better tool (I know I'm gonna catch flak for this, but having a tight feedback loop with some working code is preferable to doing everything the "right" way when you're self-teaching)