You can use a loop (system command) "For each [object]"

For each Object

--- Object.value = XYZ

------------> Do stuff

~Sol

Hey sorry for the late reply, I've been busy with my new job... I can see what I can put together but it may not be until the weekend.

~Sol

There are no bugs that I am aware of.

I also added Line Of Sight behaviour to the "ghost" objects (because my boids objects are following a moving player) - then if LoS is lost, the "ghosts" position are simply set to the player position - then the boids flocking takes over again to create a nice spread pattern for the pathfinding destination.

If you want to avoid solids accurately, I would also recommend using "custom movement" behaviour on your ghost objects and tell them to push out of solid if they overlap. This will ensure your units will always find a path since the ghost will never trap itself directly inside of a solid.

I do have a capx file, but it's my current prototype/project and is probably way more complicated for showing this method.

If you have trouble getting a good result let me know and I will see what I can do. I start a new job on Monday so my free time is greatly impacted - but I can perhaps share my project with you if you keep it to yourself and don't share

~Sol

I don't use Google Drive, so I'm not sure about that.

I use a hosting account on my domain to upload tests and things like that.

You can buy a domain and hosting package from places like GoDaddy for a very cheap price if you only need basic options.

~Sol

You can add a value then multiply it by -1.

Set variable to self+object.speed*-1

~Sol

You need to add the boolean value to the condition of the click...

Mouse clicked on button

Boolean value = true

---- do stuff

Mouse clicked on button

Boolean value = false

---- do nothing

You will need to upload your capx or make a simple version of what you're trying to do, so I can edit it to work. I'm not exactly sure about the method or placement of your buttons, so making an example probably won't help if I don't make it the same way you have it set up.

~Sol

You can add an instance variable to each button that uses boolean value - then toggle on/off for the button to be enabled or disabled.

~Sol

If drop shadow effect doesn't do the job (sometimes your shadow might not be at the angle or position you want, depending on how you draw your sprites) - you can make a separate object for the shadow and add it to a CONTAINER with your main sprite. Using a container will always make sure the shadow is following the correct instance of the sprite without having to do any UID (or similar) comparisons.

Similarly, you can just draw your shadow onto the actual sprite using a 50% opacity brush or something - which is usually what I do - but again it really depends on how you draw your sprites if that way will work for you or not.

~Sol

If you want to use a single image for your map then you will still need to either make some separate "overlay" images to detect where the mouse is.... or make some events to define the areas where you want your mouse detection to be.

Honestly, it's probably easier to just cut the map up into individual territories and use them to detect mouse position.

~Sol

Dropbox has changed and doesn't allow public/live linking anymore:

As noted here

Unless you are an existing paid/premium user... then the live linking will finish on 27 September this year. If you are a free user then they stopped that from working already.

~Sol

Making objects avoid each other while using pathfinding is an interesting problem. You can make each object as an obstacle to each other, but this causes a lot of issues on itself - like poor performance - and still they will pile up on top of each other frequently.

I made a nice solution to this, but it might or might not work for you... I used the BOIDS plugin to help.

For each of my "units" I made a "ghost unit" that was the pathfinding guide for the actual unit that the ghost unit is assigned to. I made a 'container' with the unit and the ghost together, and set the ghost to "flock" to the destination using the boids behaviour... then set the actual unit to pathfind to the ghost if it's distance was more than say 10-20 pixels.

In this way, the boids behaviour takes care of the avoidance/steering of the destination and the pathfinding will travel to the ghost/boid.

There are a couple of boids plugins available - I used the old/original one (I found Rex's boids was a little too much for what I needed and the old version worked exactly how I wanted without anything too difficult).

In short it goes a little like this:

[UNIT] ----pathfinding to----> [GHOST] -----flock/boid to-----> [DESTINATION]

I hope this sheds some light on the method.

~Sol

Yeah sorry, text or input fields... also iframe plugin... really anything that resembles "form data" or anything like that will always be drawn on top.

You have to be clever with making things turn invisible or move off-screen when not being used - or make something using spritefont and custom text field entry. This is not a limitation of Construct 2, it's just how HTML5 works in general. Unfortunately, there's not any "super easy" answer to solve the problem. In the past when I had this issue, I came up with clever ways to simply hide the input fields when they don't need to be used, then display them only when the user has to interact with them.

~Sol