I always learn software by using it as well, but that also means looking at examples (a lot of them are provided with the download and many others are here on the forums)

Following a tutorial that isn't about what you want to achieve isn't a very nice thing to do, but it does provide you with basic (and as such) nescessary information about the use of Construct2.

This basic information will help you also when asking for solutions to event-creating, because you have a far greater understanding of the possibilities and the way things are done. (and for the right names of certain aspects of your project.)

Sharing through Dropbox is what is most used on these forums.

Making artificial intelligence is hard, very hard.

You have to tell the computer what to do in every situation.

If this move is possible do it, if not see if this is possible, if not try this, etcetera. You will have to decide which moves are preferred. In men's morris it is pretty clear that creating a line of three, or preventing the other player to do so are the best moves if possible.

you should also try to randomize the AI movements a bit to not always play the same.

Why do you not have another choice?

Maybe a strange question, but ..

Why does the Scirra site have a tutorial section?

I'd rather you'd share your capx in another way, because I'm not going to install software to be able to download.

Placing the pieces should be no problem. Just use drag and drop.

Use a global variable and set it to 3,9 or 12 to determine how many sprites must be created.

For moving I would create a boolean for selected and if selected set possible locations to move to visible.

AI will be your biggest problem as is usually the case in strategic games. You will have to create events to make the computer choose the best move in the given situation.

If you get into more trouble with instances be sure to read the topics about Picking/selecting instance(s) in the FAQ

I don't know how you have your events set up, but add a variable to the object. Once moved change the variable and add a condition to the moving so the sprite can only be moved if the variable isn't changed.

In the 8-direction behaviour settings set default controls to NO.

Add keyboard to layout.

Add event:

on keyboard W pressed - simulate 8 direction - up

tulamide,

You're right, slight miscalculation there.

Was aiming for your last one.

Added the 1 because I thought the 0 was unwanted, your explanation is much clearer.

set number to floor(random(1,24))*32

that just leaves out 1, I guess..

Have you checked your collision polygon? Did you try changing it in your physics behaviour settings?

You could always apply force or impulse at collision if needed.

create object: x - sprite.imagepointX(1)

               y - sprite.imagepointY(1)

where 1 is the number of the imagepoint

I don't know how you have your events and/or variables set up, so I really can't answer that question without guessing.

To make it easier just do a system compare two values: variable > 0