Oh, that explains a lot

(jk )

Sweet Home pretty much is Alabama. Just with more rain.

Living in the city I often forget that the rest of Oregon is pretty backwards and retarded.

Maybe it is after all then. I'll defer to your expert analysis

I don't think it's a bug, and I'm pretty sure I've figured out what's happening.

Likewise, it's not the speed, I slowed it down to 200px and it will still do it. It just does it faster when it's fast.

Here's what's happening:

On Collision only registers once when objects overlap. If they continue to overlap, they will register nothing for On Collision after the first tick of overlap.

Your sprites are all Per Pixel collision. On Collision only triggers when the very front corner of Mega Man's shoulder touches the black portion of your barrier. Then the angle flips.

Sometimes the Mega Man sprite can be in a position where it will trigger an On Collision with a barrier and flip... but flipping triggers On Collision with the back corner of Mega Man on the barrier behind him, so he flips again.

Since he's triggered On Collision in the previous tick with the first barrier, it will no longer trigger because Mega Man has moved into the barrier by then.

So in other words, it's a flaw with your design... not with Construct. You need to make a more refined design that will do what you expect it to.

I wasn't going to say anything but SuperV is right. Except for the snake, I can't even tell what those graphics are supposed to be

Also, I don't recommend you get into a "very big project" without at least making some small ones first. But that's just my advice, do what you want I guess.

Awesome, thanks guys

Would it be possible to implement a sorting system into the object pickers? Options to sort alphabetically by name or object type would do the trick I think.

Apologies if this has been suggested before, I can't recall if it has or not.

Yep, looks like it's working fine from here.

Awesome, thanks for the new update Ashley

Working okay so far (except for the center view thing, of course )

No problem

Yes, that's what I meant. Sorry, I'm used to people understanding the whole pseudocode thing.

The proper way to type it out in the editor would be:

(angle(Sprite.Value('lastX'), Sprite.Value('lastY'), MouseX, MouseY)
[/code:xtw1yy8h]

But that's a lot to type, so I used pseudocode

In the 'Angle' category of the Sprite's actions, there's a few actions like 'Set angle towards position' and 'Rotate towards position'. For example, Set angle towards MouseX, MouseY will make the object look at the mouse.

Ash, if he's got the Mouse behavior on the object, then it can't point towards MouseX, MouseY

What you could try is this:

Make two variables for your object called "lastX" and "lastY."

+Always
  -Sprite: Set angle to (angle(lastX, lastY, MouseX, MouseY)
  -Sprite: Set sprite.value('lastX') to MouseX
  -Sprite: Set sprite.value('lastY') to MouseY
[/code:19h3iw34]

I think that should work.