The individual license states you can have a licensed copy of C2 on as many machines as you wish, as long as only you are the one using C2. The business license allows only one machine to have a licensed copy, but anyone can use that one machine.

Still exists in r66.

I have GMS as well as C2 and I would be very interested to see the files you used for comparison.

Just from little testing I've done, I found I can create the GMS demos in C2 in a ridiculously short time, whereas anything of note in GMS needs to be done in GML.

But, as everyone else has noted, to get the best out of either - or any software really - takes time, effort and a lot of practice.

If you're getting disheartened, then do small prototypes of the problems and post them for others to possibly help.

Never hurts to ask for help.

The manual entry for Plugins is HERE.

Download the SDK and use your favorite javascript editor, load whichever template you need and then off you go. You will obviously need javascript skills in order to create either a plugin or behavior.

As Ashley has previously said, there are so many different monetization APIs that it would be easier to contact the relevant one and get them to create a plugin, as they already know their API. Otherwise, you will need a good understanding of javascript and the relevant skill to do this yourself. There is no 'tutorial' for creating API plugins.

You could post a request in the Extending C2 section to see if one of the current plugin devs would be interested in developing this. It doesn't hurt to ask.

C2 can support any API using the SDK.

You're probably better off using Google for getting info on this as from what I can gather (those who know please feel free to put me right) you will need to configure the server to allow this.

DUTOIT

You can tell your a father as you have the patience of a saint !

Your sprite collision polygons for Sprite are a mess :/

Best practice - if you follow Ashley's excellent tutorial - is to use an invisible box sprite with the platform behavior which is used for all collisions, then place your animated sprite at the same position.

If you don't want to do that, then make sure all your animations have the correct collision polygon - easiest way, Right mouse set to bounding box then apply to all animations.

The collision polygon on your sprite is almost non-existent.

Best practice is to use an invisible oblong sprite for us in collisions with the platform behavior and just attach your main animated sprite to it

helena

Exactly.

I use Corel X6 for everything so the image editor is of little use, except for creating prototype images such as boxes and circles.

I expect Ashley will develop it eventually, but he is only one man, after all, and there are SOOOOOOO many other more important things he should concentrate on... ****cough modularity ****

—

The licensing for the free edition says you are not allowed to use it for commercial purposes, and selling the .capx is, strictly speaking, a commercial endeavor - see How Licenses Work.

Maybe it would be for the best if you just asked Ash or Tom if it's OK, as they are the ones with the final say.