(in the video part1)
And this is exactly what you are required for C2 too.
C2 is an engine made to help you. It has already solved numerous problems related to game making for you already.
If you were to program your game from scratch, you would have to first create a context render, have some bit of code to get the inputs from the user on a "low level", etc...
All this, C2 does it for you, and it does it very well so you almost don't have to care about it.
Nevertheless it is better to know about it as it will enter the scope of your design.
The scope, range and support to solve problems is framed by the software, so that you can focus on your game's mechanic/behavior instead of "the whole thing" (low level technology, "out of the game" concerns).
That's what an engine does.
C2 provides you with building blocks (plugins) like the Sprite which can contain/display one or several frames (images/textures) and display them in an animated way.
The Sprite can also be moved "physically" in the layout. It has properties. You can assign it behaviors that will give it new "possibilities of action". All those objects have interactions and inter-connections.
Every feature of C2 is treated in the manual. It's not the funniest (nor only way) to learn the tool, but be sure to keep this link as a "go to" when you are working with C2.)
° You'll still have to analyse and solve problems inherent to your games.
For that you can rely on a massive amount of knowledge already sitting in the tutorial part of the site as well as in the forums.
You are left to figure some stuff out eventually, as it is your game, your design, but you can learn a great deal from what has already been done/posted and expand from it.
If you are a totally newcomer in the word of game making/have little knowledge about it rest assured that all you beginners questions are already answered on the forum. Be sure to search through it. Have a look at that other tutorial I wrote if you haven't already.
It should give you the keys to finding efficiently documentation and your answers through the site.
If you're really stuck/lost, don't hesitate to post you'll probably get an answer in the day or two from the active and helpful community.
Analytical and abstract thinking.
This helps. As stated in the video, if you got it, you have it since a young age and already have explored systems and maybe even have tried to pick up "true programming language" to a certain extent.
If not, don't worry, as said in the video you can work it. You already have those skills, you just need to apply them to making games.
Reading through the manual and the tutorials on the site and experimenting/linking the concepts in/to C2 is a good practice too.
And the more you practice in C2, the more "fluent", used to it you will be and the easier things will get.
° Analyse the games you play.
This is a very interesting exercise. To learn more about it I recommend you to check those two other videos from extra-credits (part 1, part 2).
Check Scirra's arcade, try to find/guess by seeing/playing a game how the author did it (he used C2, just like you). Even get in touch with him to ask.
Or check and start discussions in the Game Design forum. Don't be shy, don't hesitate to post/ask questions, there are lots of game designers amongst the community that are expecting to answer those types of questions.
° "Having a wide body of tools and lots of experience to draw from"
C2 is a tool. It provides other tools. Plugins, behaviors, layouts... each element that is available from the IDE to make a game is a tool with a specific usage, properties, etc...
Having the experience using those tools will come with time and practice. As said earlier, check the manual. Experiment in prototype/quick new projects. Explore, be curious, force yourself to think out of the box. Figure out what are the effect of all the actions/conditions/expressions available in any plugin/behavior. Learn their interactions, have fun.
With experience, you'll be able to anticipate what plugins, events, layout/pattern you will need and use, in what setting/configuration.
- Be curious, check how other members implement a solution to a problem/make game mechanics (you may find lots of useful capx examples/posts/topics referenced in the "How do I FAQ")
- Learn techniques (ways to implement a feature) and learn "when and how to apply it".
This is the key to elegance and to being able to make more and more complex games and being able to maintain them along time.
"Accumulate as many tools on your tool-belt as possible so when the time will come you'll know exactly what to use."
Solve problems quickly and elegantly.
If you are still a student, enjoy this blessed time of life to learn and explore. Your brain can store a huge amount of new things and to make a game you need to be able to address a wide area of subjects. Having basic knowledge in all of them will make your job of making a game easier and even allow you to work in team easier.
Any experiment you make, you can publish on a blog/portfolio and add a link to the blog on your resume when you'll be job seeking.
If you are around/over your thirties (like me), you know it's getting really harder to learn new things and life is taking.
But what you already know, you master it better. You already have had problems to solve in your life, in many ways. You already have that skilled and knowledge, find the time to practice and apply it to game making.
If you can't devote a huge amount time on this, just aim for little short games.
Even if it takes 5 years until you make a game that resembles the game of your dream, it's not wasted time.
Another great way of learning/gaining experience is to work on collaborations.
Check the Help Wanted forum, a forum especially dedicated to such projects and job offering.
A very good way to learn his craft.
This forum was created recently, but I'm sure a lot of great projects will be posted there allowing hobbyist and more "serious" users along making great games.