This post is a follow up to the Roblox studio post I made nearly two months ago. You should probably read that first.
Sooo i’ve done almost every Lesson that CK Studio + has to offer:
Great! So does this mean that I can create fully-fledged high quality Roblox games?
Absolutely Not.
I’ve got a long way to go before I can even begin making a game. I mean sure, i’ve covered remote events (for client replication)/client server model/local scripts/functions/services/etc, but there were times where I lost focus, got interrupted, or was just completely lost and copied the solution code.
I’ll be honest, not everything I learned stuck. The more lessons I did, the more sense it made AND the more confusing it got…if that makes sense. One thing leads to another which clears up one thing…but leads to a more complex thing. It can get messy, Retention was by far my biggest issue.
If you do plan on using CK Studio + (or any teacher at all like Alvin Blox). I’m going to give you a few tips to help you have a better time with this stuff than I did. Not saying I didn’t enjoy it, I’m very glad I was able to try to learn something I actually wanted to learn. But it’s not easy and i’ll have to keep at it…
Don't Force It
- Probably the biggest lesson i’ve learned when starting this journey. If you don’t feel like doing a lesson, don’t do it. You will not be focused nor will you care enough to retain what the person is saying. An example of where this applies in my lessons was when I did the “Tycoon” Challenge. Where you had to build 3 different machines to clean/cut/refine the rock. Well I was feeling out of it and got lazy so I used the cleaner machine model for each.
-
If you told me to replicate this for you, I couldn’t. All I remember is that I connected the touched event to a function to make the buying stuff work.
-
It’s not like this stuff is graded. It’s something you do because you wanted to do it! Go at your own pace. My biggest mistake was biting off more than I can chew and doing lessons when I didn’t feel like doing them.
Keep Some Form Of Documentation
-
Sure, the Roblox API reference manual exists and it’s comprehensive. However, it’s always a good idea to keep track of what you learn so that you remember it better.
-
Don’t over-do it though. I made the mistake of writing down nearly the entire script of the videos I was following, mainly because every sentence was one key point after another. This made lessons that were supposed to take 22 minutes 2-3 hours. I even made a quizlet, about 100 terms. Idek if some of them need to be terms at all.
-
My quizlet is staying private, but here’s the API manual.
Do NOT try to make a big game as your first
-
Nothing wrong with having big dreams, i’ve got a great idea planned on a trello rn, but i’m going to shelve it for now. This is because I want it to be good, and until I get that scripting/building/modeling/music-making/ and story-telling experience, it won’t be good. So I will wait before showing it to the world. Even if it takes years. There’s nothing worse than having your most ambitious idea fall flat.
-
You don’t have to be a one man band like Vetex. Originally when I went into this whole thing, becoming a “one man band” was my intention. But after realizing what I was dealing with, I may end up with a team after all. Idk.
It's Ok To Make "low tier games" like obbies for practice
Obbies have a terrible reputation for being clickbait-y, low-effort, and overall terrible.
However.
They are somewhat easy to make and are good for practicing your modeling skills. You do not have to publish them, it’s best if you don’t since it’s for your eyes only. Which brings me to my next point-
Practice Practice Practice!
-
Another one of my biggest mistakes was not practicing the material I went over before moving on to new material.
-
You can document day and night, but actually putting it into the computer is what matters most. Everyone has a different scripting style, you just have to find yours. In scripting, there are multiple ways to do the same thing…don’t do “else if else if else if” though. Please.
