Surely many actions in Construct can be tedious but it's by far the most intuitive and easy to figure out game making tool I've ever seen. Again I'm very new to game making though I'm no stranger to programming, but game programming gets very complicated right at the basics. I've seen Construct to mostly skip the basics chores thanks to behaviors that actually work as intended.

So far I think when some feature is lacking it seems it's more in the spirit of keeping everything super easy to use, and yes, that makes some simple things harder to make. But so far I think every compromise I had to make was acceptable enough.

I don't know about them not paying attention to suggestions. I see there's an update every week with some small announced functionality so I guess they do look at suggestions, and the more straightforward the better. What you described seems straightforward enough.

I think I got it. Instead of moving at an angle, I added behavior 8-direction. I was using ranges of angles to change the animations (for example if stick was pulled from 45º to 135º the player was changed to sprite looking down). Those same ranges can Simulate 8 Direction. For diagonals, all I needed to do was to widen the ranges some 30º each.

Now it acts exactly as I intended, the control stick works and the player won't be completely blocked by solids, it slowly slides around them when moving diagonally. I feel like I leveled up!

Player coordinates are relative.

Hmmm are you saying I could convert angle to a position in the same angle? That could work! I don't know how to do it but it seems like a proper workaround.

Also Los has raycasting.

What is raycasting?

By the way, before moving further into line of sight, I'd be worried about the fact that your suggestion included pathfinding, something I found to be very erratic in real time/every tick.

I would suggest something like Line Of Sight in conjunction with Pathfinding.

Bool variable "canmove" =1

>- player has Los to touchx,touchy, move to touchx,touchy.

>-else set "canmove" to 0,player find path to touchx,touchy.

Player on path finished, set "canmove" to 1

It can only be as smart as you make it.

Thanks for the reply. That could be one way to make it with TouchXY, but it kinda kills the idea of moving with the stick.

Do you know if there's a way to use MoveTo in an angle maybe?

I only started using Construct recently so I'm not the best source of info for this, but the way I see it, there's not a native menu object or function, you'd need to manually create text boxes for the top menu options, then sprites for dropdowns that open when you hover said options, each with more text boxes on top of them. You can divide them in families and layers to make it more manageable and maybe a function to open and light up on hover. On Windows menus the formatting is simple enough but you'd need to do it manually too, there's no native styling of fonts that I know of.

Hello!

I'm trying my hand at a simple touch-based mobile dungeon crawler. I got to a point where any option seems to lack something so basic and yet I'm so close to nailing it. Maybe someone can give me an idea.

I tried more than one way top solve this so skip the next two paragraphs if you want to get straight to the point.

So first I thought grid-based movement would be easier to manage, but was I wrong. It's pretty easy to move the player with the keyboard, but using touch to select one of 4 directions is so clunky.

So I started using behavior MoveTo - to Touch Position XY. That works as intended mostly. The player moves towards the coordinates where I'm touching the screen, and stops at solids. I wasn't happy though that the player would completely stop when reaching a solid instead of kind of sliding around it. Looking for a solution for that, I came across a touch stick tutorial, straightforward enough, so I added that too. (in case anyone's interested, this what I used construct.net/en/tutorials/touch-stick-controllers-241/page-4 ).

Ok, now my problem is, I can move the player by detecting the angle the stick is pulled to, but it won't stop on solids.

I suspect this is because I'm moving the player by "Size/Position>Move at angle" instead of actually "MoveTo>Move to position", which seems to comply with collisions. However, how can use MoveTo to go to a certain direction then and not toward a position?

Here's my project. 1drv.ms/u/s!AlBF-Ft-T2VNsIYWv9-Bx4zTJGY8Ug

Here's my event sheet.

Thanks for any help.