You are correct, I recall Ashley stating that an include in CC just pastes a copy of the events when compiling, meaning it compiles multiple copies of the included event sheet. I don't have any other ideas how to improve things, though.

I disagree - if you set the scale to 0.55 instead of 1.1 you would have gotten the effect you want. You also could have done set size and multiplied the width and height by 1.1 and used a trigger once. Having no set base value for what 1 means in the scale action would be more confusing, I think.

Moved.

Voted!

Thanks, yup I'm also stoked to get such a positive reaction from everyone! Can't wait to share some of the games over the next few months...although we'll probably need to pixelate some of the shared screenshots to respect the forum. <img src="smileys/smiley2.gif" border="0" align="middle" />

Thanks for trying to be considerate for the rules of the forum, but pixelation isn't really enough. If you're going to post images, only post them of non-explicit parts of the games.

You can use 'is overlapping' instead.

All The other game dev programs stink

C'mon, that's taking it too far. Discussion of other tools is allowed on the forum, but please refrain from being insulting about it. Statements like that tend to offend and drive people away, and we want this to be a very welcoming community. Just because you don't like them doesn't mean they're not good for other people.

Yeah - we can already select either the accelerated or non-accelerated version of physics for cocoonjs - so could it be made that c2 automatically uses the asm.js version when exporting to node webkit, or having an option somewhere so we could decide for ourselves? Or perhaps include both in the exported game, and automatically use the asm.js version if it's a browser that supports it, and otherwise revert to the previous version?

I agree, everything looks great, except for the sand duneish parts, which make it look like a frozen desert. Unless, of course, that's what you want.

Looks awesome! I was wondering if you were going to make a full game of it.

spy84 - I have too much else going on at the moment to research it.

Integrating game closure into C2 is likely something that would take longer than a week or two. Integrating HAXE has been discussed before, and Ashley said it wasn't really an option because it would take probably around 6-12 months, development of anything else on C2 would have to halt for that whole time, it would make all third party plugins not work, and by the time it was integrated, it's likely other solutions would have caught up and improved sufficiently in that time to the point of making move pointless. What's more, is it would likely have it's own set of problems - stencyl decided to use HAXE for their next version years ago, and they still haven't gotten it working yet - likely because the transition wasn't as smooth as they hoped it would be.

Awesome, thanks for helping us out!