Sorry if I posted this here.
I wanted to know, do I need to learn things that I don’t really need to know to become a better developer? or should I only study things that I only need and then study relevant things when I only need them?
this is like education, you study things that you don’t really need later on in life
As a scripter I’ve never learned much that I didn’t intend to use immediately. It’s not hard to learn new things when you can apply them practically. It’s very hard to retain information that you don’t put to use in some relevant way.
If you really don’t need to know them, then no, by definition you dont need to know them to be a good developer. The question is if you’re right about not needing to know them. I can’t do physics/animations/complicated math stuff, and I definitely feel a bit gimped as a developer nowadays.
Learn stuff as you come across the need to is my advice, you’ll understand it better when its the thing in the way of your current project.
That’s actually your choice to decide.
What I would do is learn something difficult like Gui Collision, not because I have to use it or anything but because by learning how to it will increase my skill and knowledge.
It might be useful for something more advance in the future, or you might know how to do something because of it.
I agree with this. A lot of what I have learned has come from developing Roblox Battle Remastered, and then Ultimate Boxing.
As a side note, you may want to use more descriptive titles.
First of all, I’d heed @RBX_Lua’s advice, not the least because he has Lua in his name.
Nevertheless, in my yet-short life, I have learned many things which have become useful at a later date, and things which will likely never be of use. You should not attempt to discriminate knowledge in terms of usefulness before you make an honest attempt at learning it, as only time will tell whether it was worth it or not.
As for more personal advice, mathematics has been a great help in getting a deeper understanding of spatial programming, and interacting with the ROBLOX 3D environment.
Knowledge is optional. Being able to apply it is much more important.
Although not knowing the applied method fully (it’s not always necessary to understand it to apply it) makes debugging it much harder.
I’d suggest keeping track of all the little problems you come across.
As you learn, return to it every now and then and see if you can solve any of them.
If you’re stuck on something during a project, take a little time away from what you’re working on to learn about it, use it, and then work it in to whatever project you’ve got. I’ve got functions I wrote a year or two ago I still find handy today, and code today that solves a ton of problems from last year.
Just remember, you’re learning new things all the time! While you won’t immediately use them, it all adds up to one thing;
Depends what you mean by ‘need them’, it’s a great idea to just make games that come into your head no matter whether they are a possible money maker or will get popular, just try out your idea to see if it works. This is how pretty much all scripters learn, they think of an idea that hasn’t been done before and try and make it, and learn how to do a lot of stuff along the way.
Making a game teaches you so much more than just learning random stuff you might never use (and probably would have forgotten by the time you do use it).
I’ve made a lot of games, and 90% if what I know is from simply doing that. That’s my advice.
So what should I do? should I keep making games and only study things that I will need for the later on for the game?
Keep making games. If you want to make part of a game or a program but you don’t know how to do it, then learn how to do it.