I believe there was also a commercial e-book published somewhere concerning how to use CC.. A shame there was never an "official" one, but I suppose since CC was a lot of patchwork a "comprehensive" manual about it would be far too much work for the Scirra team.

Doom.

You've made some pretty awesome contributions to C2, you know that? :D

I feel that there should be some sort of stickied topic, if there isn't one all-ready, that just directs ALL early adopters for badge questions, concerns, etc.

I mean, not like the badge matters in the end, but it's nice to have so not everyone is making a topic every other day about their badges (and mrsponkie, that's not your fault!)

I feel that for certain games with more of an arcade-like focus, set number of lives is way to go. If it's a short game by design, give a reason for coming back to it, aside from how obviously fun it is (ha). I like fixed lives + limited continues, but not all games call for that.

I would look up "Vertical Shooter Tutorial" since I think that does the EXACT same thing, gameplay-wise. Check out the Tutorial Lists in the Tutorial forum.

All in all, you could probably just take the instructions in the C2 tutorial and just copy them into CC, since the commands are so similar.

I think you'd need to work with the pathfinding plugin, or something. In any event I feel what you want to do would require some advanced math computation to get it to be just right.

Understandably, this is something that should be a bit low on the priority list.

Then folks like lucid, newt, deadeye, and R0J0 deserve goddamn "Bad Dudes" badges for all the stuff they've done around here.

;p

When you are dealing with enemy health, you should always set up the death event so that it's like

When EnemyHealth LESS THAN OR EQUAL TO 0

Because the way things work, often you can "overkill" an enemy and nothing will happen to it at -1, -3, or -500 health.

Basically, a lesson you should learn is that when you code in C2 (or anything else) you have to think of ALL the possibilities in your game. In this case, you can't just think "What happens when enemy's health is 0? Easy, death." You have to think "Well what if he's shot a whole bunch of times really fast? What if his health is below 0?"

you should post your capx file so we can see directly what you are trying to do.

How about your give your character a private variable, "InAir"

So that when your player sprite jumps, it can be like:

Player is jumping

-Set InAir to 1

InAir = 1

Control "Jump" is pressed

-Make player Jump

-set jump strength to (x)

Player is on ground

-Set InAir to 0

-Set Jump strength to default