How to make a game around the same level as the sample game?
I am now learning the c++ code part of the UE 4. I have read some codes of the sample projects provided here (for example, Sample Survival Game, Unreal Match3, Platformer Game etc. ). I can read through the classes, understanding about 50%. But if I make the game, I will certainly not be able to code things like this. Or, I don't even have a concept of how these things are coded in such ways. For example, sometimes for a very simple thing, I may just use one function to achieve it, while they spend tons of classes. I even doubt whether those codes are necessary or simply adornments, 'cause I sometimes delete lines of codes and the project still runs perfectly.
I watched all of the video tutorials, some twice and even more, but I think these only cover the most basic parts. If I wanna make a game at the level for sale, these can't be enough to help me.
So how can I get rid of this embarrassing stage? Any recommendations?
asked Jun 19 '16 at 04:09 PM in C++ Programming
A fellow David! Welcome to the world of game development! It's a continuous learning cycle. The best ways to make great games is to... make games.
Start simple. Create by imitation. You see a cool game out there that looks basic enough? Try to create it. I started, way back in 2005, by creating clones of Pong, Breakout, Tetris. Each project taught me something. The most important thing, being, finishing a project.
Once you feel confident and aware of the toolset, raise the ambition. Participate in game jams to really focus in and practice for a weekend. Epic Games provides one each month!
It's a long process. Don't expect to overcome all challenges within a day, week, or even month. There is a LOT to learn in this field. Some choose to be generalists (your gameplay programmers), some choose to specialize (artificial intelligence, graphics, physics, audio, tools). Find what makes you happy and go for it.
When you feel comfortable, join an independent team and help!
Ask LOTS of questions. Sure, hunt on google.com for help, but don't feel bad if you need to ask a question (here or on other forums).
Regarding the code you see. Part of being a good programmer is learning how to architect the house. We just don't throw boards down and call it good. We plan, write maintainable code, and constantly improve the code base. This naturally leads to way more classes, functions, variables, etc. Deleting some of this stuff may not show issues today, but they're usually purposely planned. Just because deleted code still works today, doesn't mean it works in all scenarios.
Follow this question
Once you sign in you will be able to subscribe for any updates here