Wow, this kind of blows my mind, honestly. I had read a few things on how to do this and came back to see if any tips had been posted before I got into it, but this example project not only eclipses my math skills but also is written far more beautifully and efficiently than I have ever done. I feel like a caveman on multiple fronts, haha.

I am looking inside of it now to see what I didn't know that I didn't know. I didn't even know "Pick by Evaluate" existed.

End goal is to have the AI begin play overconfident and sloppy and then tighten up over a few lost rounds til it plays perfectly.

In that case I feel it's better to understand the math and create the perfect play, then engineer mistakes into it.

Do I like... I dunno, get a math tutor to explain it? Or a professor?

If you're using bullets for enemies, couldn't you use the solid behavior on the enemies to keep them from overlapping?

That is a lot of work on my end and it won't help you learn!

Look, start with something small.

Try making an AI that will move towards you or away from you. Use a timer and a random number inside of an instance variable to set AI patterns for your AI.

Give it a try on your own before you read the next part here. I'll explain it, but you should try at least to figure it out on your own.

You can do it like this.

On start of layout -> Start AI Fighter "Random Picker" timer, regular 2 seconds.

This starts a timer on our AI fighter when the layout begins. This timer repeats because it's regular.

On "Random Picker" Timer -> set AI_Fighter "Behavior" number to int(random(3))

Random will set the number randomly between 0 and 1 less than the number you put in, so in this case, randomly from 0 to 2. The int part rounds the number to a whole number. That means it can be 0, 1, or 2.

Now, make your code do this.

If "Behavior" is 0, don't simulate control.

If "Behavior" is 1, simulate control left.

If "Behavior" is 2, simulate control right.

This will make an AI that sits still or moves left or right ever 2 seconds.

Oh, did you try Layout Scale like peter568 mentioned up above?

Well, essentially you have everything you need. Basically, when you are not right clicking, it does the zoom between two objects. When you are right clicking, it only zooms to the crosshair.

If you're doing the "scroll to" method, you can just set the behavior disabled on the player while you are right clicking and enabled when you aren't.

Here, I grabbed some quick screenshots from my own code.

Ok, so I have a sprite with the solid behavior. I go to that behavior and add a tag, like this. This is done in the properties bar of whatever you added solid to. It could be a sprite, tilemap, tiled background, whatever you need. I tagged my solid "house" in my project.

Then, we write a piece of code that sets our exceptions for us. In this screenshot, I wanted my player to be able to walk through the house solid, and so I create an action from my player using "set solid collision filter". This action lets you include or exclude, and since I want my player to pass through, I picked "exclude".

Now my player can walk through any solid tagged as "house".

Good to hear! You were destroying the coin as soon as you made it.

Ok, so looking at the gameplay of the video, I think a simple way to do this might be to do the following...

Make a crosshair sprite and use "every tick" to set the crosshair at mouse.x and mouse.y.

Then, add the "scroll-to" behavior to both the player and the crosshair.

What "scroll-to" does is attempt to center the viewpoint on whatever object it has on it. If you add "scroll-to" to multiple objects, it does a quick version of what oosyrag has described. However, using Scroll To like this means that you can't do little cutscenes where the camera focuses on another object.

Although oosyrag's version is a bit more complicated, you can do more things with it once you know how.

The way you have your code set up to mirror and unmirror the sprite looks correct. That's the way I teach my students to do it. I don't think I quite understand what you're asking.