I have been scripting for about a year now and I feel like I’m not improving much is this just a normal stage or is it just me?
1 Like
You really think you can become a pro in only 1 year the goal of scripting is solving problem and meeting markets need and make games that children love enjoy the journey padawan !
1 Like
Everyone learns at different paces! Personally, I was in the same boat as you when I first started scripting. Just remember to keep working hard, never give up, and don’t overwork yourself; take breaks when your body tells you that you need it and take care of yourself! And most importantly: PRACTICE, PRACTICE, PRACTICE! You’ve got this! 
5 Likes
For me, I learnt scripting quite fast for 2 years, and now in just 2 years I’ve become quite decent. All I’ve done is frequently make full games. This means that you get to see all the aspects of studio and get used to them all. Also, the devforum and youtube are of great help!!!
1 Like
Do more things that you think are hard or can’t do. We improve by going beyond our skill barrier. Think of this barrier as a challenge, don’t let it push you back.
2 Likes
What are you using, specifically, as a reference for skill? It’s important to be very critical and sharp on what you are using to evaluate your own progress. For example: looking at a really polished game like Phantom Forces and saying “I don’t think I could get anywhere near programming this, even after a year of work” isn’t unusual at all (in fact, that’s pretty par for the course!)
Rolling with the same example though, would you come to that conclusion because you’re A. not sure about how to go about designing some of the things in that game, B. not confident in your math (PF is a great example of a game with a lot of math), C. of the mindset that it would take you an extreme amount of time to make it, D. unfamiliar with the Roblox engine to really know the best way to create some of these things? In all of those cases, we’re dealing with different ‘issues’ (all of which get solved by chipping away at scripting). A. is a knowledge/concept issue, B. is a knowledge (but more in the lane of “skill”) gap, C. is an efficiency issue, and D. is a knowledge issue that really just comes from reading and trending engine updates and features as they release.
So rounding back, what are you using to assess your pace of improvement (or perceived lack thereof)?
On a separate note, which is about improving quickly and efficiently, I totally recommend creating as a means of improvement (if you’re not already doing this). More specifically, I recommend avoiding learning scripting for the point of learning’s sake (e.g., watching a YouTube tutorial and trying to replicate it before moving to the next one). Instead, I recommend learning for the point or articulating what’s in your mind/allowing you to create something.
For example: you are working on a game (either for yourself, a group, etc.) and you want to make a gate that opens and closes. In doing so, you are forced to ask questions, read up, and take a hard look at how to make options (particularly somewhat complex ones) move in the way that you want. When you finish this, you’ve probably covered quite a bit of ground - much more than you would had you just learned those concepts individually, as there’s less reason for them to stick.
1 Like
thank y’all so much guys I feel better now
Just note not sure if this is mentioned but scripting is a process of writing, trying and branching out.
You won’t know every method, I sure as hell didn’t when I started, I like looking back from time to time at things I worked on or old posts and seeing the progress I have made.
You learn a lot when trying out new projects, even if you don’t and use the same methods, looking on devforum I see other peoples problems and I search on devforum and the documention to try help. I learn new stuff doing that most the time.
1 Like
Then you simply aren’t learning anything. What have you tried?
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.