Just need some advice on using ai to code. Im not a great scripter, im ok with basics but struggle with bigger systems. I made a quest system the other day and used ai to tell me all of the structure and instructions without showing me exact code. I copied little to nothing.
Should i be using ai this much?
1 Like
I think Ai is a great resource, but I’ve started to notice some problems with my own workflow. I would have Claude give me structure advice, and try to learn from that, but I noticed 2 things.
(This is my experience with Ai)
-
AI can be pretty inconsistent with the advice it gives. I was working on a ui system, and it advised me to create a networker for my ui, and then a couple days later I was asking it for some improvements, and it told me the networker wasn’t useful. I think part of that is due to my ineptness to know what it envisioned using the networker for, but not knowing how to use the networker seems like a warning sign.
-
I lost critical thinking skills. By relying on Claude to give me the structure of the code I found myself unable and unwilling to think about a problem for more than a couple minutes. “Why should I devote so much time when Claude has the answer?”. I’ve been taking a break from using AI everyday. I’ll still ask occasional questions, and ask it for code examples, but I’ve been trying to wean off it a bit and relearn how to sit with a problem.
My solution:
I’ve been trying to read more on forums for my questions, and read more books. I picked up Game Programming Patterns by Robert Nystrom and have been really enjoying learning things I heard Claude mention, but I never really understood. Sitting with problems has been super fun and engaging, and i’m finding that I understand my systems a lot better!
Ultimately, you might learn differently from me, but these are just some of my thoughts. Hopefully they help you think about whether or not you should be using Ai as often.
Extra thing:
I think it’s similar to tutorial hell. Eventually you have to bite the bullet, and just have to dive in.
3 Likes
AI should be rather used as an assistant than building your entire game directly as luaU is easy to learn
Your post has helped with the question that i tried to figure out on my game by scripting, your post is excellent and scientifically detailed.
2 Likes
AI is literally made to agree with you, it will go anywhere you take the topic/conversation to. You should only take small pieces of advice from it in a fragmented manner, it’s definitely not a good idea to do otherwise because AI will often give you false “peer” reviews in order to agree with you which makes you feel validated, and by extension gives you (potentially) false confidence in more significant decisions.
Obviously I don’t know you or your experience with AI, but I doubt this actually happened. It reads to me as if you didn’t lose anything but rather found a new happy path for thinking through problems. I think it’s very important to make the distinction here because this part is a bit fearmonger-y.
From personal experience so far with AI, at least Studio one I guess it is helpful only in 2 ways:
- It can help you understand basic scripting concepts, by answering specific questions, which are extremely important if you wanna level up your skills.
Questions like
“Why is it important to use WaitForChild for workspace objects on LocalScripts”.
Are answered quite understandable and more importantly you can ask it something more specifc.
But it depends to the question. It may make mistakes ofc. - It is awesome in congrating you when you correct it.
You may ask it for a little more complex system and it would give you the least optimized system where memory leaks are must.
But once you suggest it a better approach, it congrats you and gives you a better approach.
Sure it would get better with time but I highly encourage you learn the basics first and then let the magic happen as you would make so much better and efficient systems than the AI itself.
I can see how it seems a bit fearmongering ish, but I think it is something to be concerned about. You’re right in saying I didn’t actually “lose” it, but I find it similar to how doomscrolling impacts your brain. With Ai the reflexive part of your brain is highly active, so sitting and thinking about problems has a higher barrier. I’ll definitely think about how I phrase it in the future, but I do think it is something to be wary of.
Your approach is actually solid, and you’re asking the right question at the right time. Using AI for architectural guidance without copy-pasting code forces you to understand why systems work, which is where real learning happens.Here’s the distinction that matters:What you’re doing well:- AI explaining structure and flow (quest states, progression logic, data relationships)- You’re implementing it yourself, which means you’re debugging, iterating, and internalizing the patterns- This builds intuition for larger systems faster than tutorials aloneWhere to draw the line:- Don’t use AI to generate entire modules you won’t read or modify- If you’re copy-pasting 70%+ of any script, you’re creating technical debt—you won’t understand it when it breaks- For monetization systems (game passes, DataStore transactions), always understand the code. These handle real money and player trust**My recommendation:**Keep doing what you’re doing, but be intentional. Use AI for:- Architecture walkthroughs (how to structure quest data, state machines, etc.)- Explaining specific problems (“why does my RemoteEvent fire twice?”)- Pseudocode and logic flowThen write the actual code yourself. Start small—maybe 50-100 lines at a time. When you hit a wall, ask AI for a specific snippet explanation, not the whole solution.By the time you’ve built 3-4 quest systems this way, you’ll naturally write them without AI help. That’s the goal. You’re not trying to become an AI operator; you’re using it as a tutor to compress your learning curve.The fact that you’re questioning yourself means you’re thinking about this correctly.