This is a pretty complicated idea to try to tackle, but I figure I can take a small shot at it. The short answer is that you're going to have to figure it out on your own, but I can provide a few examples to get you started.

Ok, so when you're creating AI, you need your AI to be able to sense things. For example, I once created an enemy that would duck if it sensed oncoming player bullets. I did this with the "is overlapping at offset" condition. I also changed my condition from an "AND" condition to an "OR" condition and made it check both the left and right side of the enemy. Then, when my player shot at the enemy on either side, the enemy would "sense" the oncoming bullet and duck. The trick in that instance was that if the player got very close, the enemy couldn't duck fast enough.

When you do attacks, you can make your code set boolean variables on the player. So while the player is doing a high punch, you might have a variable on your player called "highAttack". When the attack is finished, turn "highAttack" off. This would let you send information to your AI that a high attack is happening and they then could have a chance to block it. This is also how I make my character stop moving when I do attacks in some of my games, and it works that way in Street Fighter as well. If you have any of your attacking variables on, you can set your code to not allow the player to move.

Lastly, since you're making a street fighter game, you are probably using the Platform behavior. Behaviors let you do certain conditions, and for platform, you can check if the player is on the floor or not. This is useful for things like jumping attacks.

Does this help you at all? I hope so!

This person is using a different movement behavior, but the same idea applies. Basically, you need to set tags on your sprites and then use an event to tell it to ignore the tags.

https://www.oneminutevideotutorials.com/2021/10/20/how-to-use-solid-collision-filtering-with-tile-movement-in-construct-3/

Can I see a screenshot of your events?

Sounds like you need to write some new controls for the player!

The first question might be "do I still want my player to be able to jump using the up arrow?". If you don't mind it, then you're all good! The above advice works just fine. Add a mouse object first!

If you don't want the player to be able to jump with the arrow keys at all, you would select your player object and check under the properties for the "default controls" section. Turn off the default controls. Then, you will program in your new controls for jump, left, and right.

Howdy, everyone. I'm working on my first project that is heavily using 3D. The concept mirrors Jurassic Park for the SNES, which features isometric 2D movement outside of buildings and 3D classic Doom-style movement inside.

I've looked at several examples which seem to rely on heavily repeating 3D cube shapes, which looks a bit samey. I could increase the number of cube shapes to get variety, but I always get this feeling that if I am just repeating something over and over in a program, then I am not using all of the tools available to me.

So I did some digging and I saw a few people bending sprites with meshes in order to get interesting 3D shapes. I would still need to create individual sprites for every chunk of wall inside a building. It seems like a less efficient version of a 3D shape, honestly.

And finally, I figured, "well, what if I could bend a tilemap? That would solve the need to create new sprites all the time. I could create the assets and then draw all of my interiors with ease!" but it seems combing a mesh with a tilemap is technically impossible.

So... are there any methods I might be missing? Is the repeating cube truly my best option?

I tried out my standard method of applying solids and jump thrus, which was to decorate my level with tilemaps and then use a separate layer for all solids and jump thrus... and it works fine.

What's this weird interaction? Has anyone had this problem but me?

Also, jumping while on the Jump Thru platform next to the Solid wall seems to launch you into the sky... what?

That was something that I was concerned about to start with: all these examples create cone-shaped lights rather than straight beams. I suppose I could sort of add invisible "blinders" to block the ray into a straight line....

I feel like I want the beam firer to remain still while shooting for the sake of fairness. However, If I can figure out how to update the beam, then I'll give it a shot.

I'm not totally new to C3, but I'm learning new things every day. Let me see if I can sort of piece together the idea.

So the concept that I believe I am reading **** that the drawing canvas is what will visually and physically represent the beam, and we are using line of sight to use raycasting in order to figure out what the shape of that beam that we are drawing into the drawing canvas will be, right?

Very nice! Glad I could help out a little bit. I completely forgot about For Each, haha.