Event Sheet Organization

I'm trying to start really experimenting with wrapping my head around the C2 logic to get the basics down. Before I get too far ahead of myself, would someone mind critiquing my organization of the event sheet?

Is this type of organization going to work well when my projects begin to grow and is this what I could use as a basic include for future platform projects? I want to get started on the right foot before I start adding tons of variables.

I've managed to get rid of all of my animation transition glitches between 3 animations with what I have so far. Is this typically what your platform player movement sections somewhat look like?

Thanks for any advice!

<img src="http://i.imgur.com/7XsUm.jpg" border="0" />

So far so good. Its a good idea to keep basic mechanics separated so that you can enable/disable them as needed during gameplay. Eg: with one action you can disable the entire "player movement" group during a cut-scene for example. or when you pause the game etc.

Thanks! I didn't realize I could enable/disable entire groups, will keep that in mind!