I would suggest you do some step by step tutorials first. They don't take long and will give you a basic understanding of how C2 works. Then think about one little piece of your project, like, how to make a sprite mirror and flip and rotate. THen pick another little piece, and so on.
I have used and learned 3 different game development softs (Game Editor, 001 Engine, and now C2). C2 is very powerfull, the few bugs I encounter are not hard to work around and are quickly fixed, and the design is very slick and well thought out. It is also very versatile. However (and this is not a complaint), it does not handle game-style specific things like equipping weapons/armor, transitioning levels, inventory management, making bullets come out of guns, etc. Those things are all possible, but not done for you. 001Engine for example is a tile RPG engine and does those kinds of tasks for you, but if your game is not the same type as the type 001 is geared for, it feels restrictive very quickly.
I'm telling you all this because I think it will be helpfull to narrow your focus down to figuring out how to do the little basic things first. Once you have those under your belt, the bigger stuff will become much more apparent.
The other thing I would advise is that as your project gets more complex, it is vitally important to keep it organized. Use Groups and Comments like a madman. Make sure that before you close your project for the day, ask yourself "If I don't get back to this for a month, will I be able to pick up where I left off?"
Sorry this doesn't directly answer your questions, but — E Bear 's car analogy is dead on.