I think everyone is using AI and no one cares about the human factor here (or C2) anymore. :(

My current fade routine is the one above. It works well, HOWEVER, it makes the enemy (zombie) first turn white and only then darken. Does anyone know how to fade directly to black?

Try using the Tween behavior on the Color property:

https://www.construct.net/en/make-games/manuals/construct-3/behavior-reference/tween

Thanks, dude, but I'm using Construct 2. :)

Hi guys!

Does anyone here have a working routine (CAPX example) for fading an object to black?

I tried several times using some effects (Tint, for example) and failed every time (even using AI). :(

Thanks in advance!

It’s short enough and simple enough you can try changing it and see. I thought defining the paths with sprites was simpler. I won’t be making an array version.

No problem, man. I'm already testing it here using Array. Thanks again. :)

I mean, the last post was instructions of a way to do it. If I made a capx it would only follow those instructions. I’ll defer to other people’s solutions in the meantime. There’s a lot of other things vying for my time currently.

I tried, but unfortunately it didn't work. I tried a few variations, with the help of an AI, and it still didn't work. That's why I kindly asked for an example in CAPX, because I honestly couldn't get this code to run. :(

There isn’t a best way. There are many different ways like I roughly listed in the previous post, each with pros and cons. But realistically you’d just pick one.

Create a sprite and call it node. Give it two instance variables: path and index. You’d then place instances of node on the layout in the shape of the path you want. Next you’d set the instance variable values. You’d set index to 1 for the first node, 2 for the second, and so on. You’d then set path to the same value 1 for all of them. You can create more paths later by just having different values of path.

Next you need something to follow the path. Create a sprite and call it mover. Give it two instance variables: path and target. Also give it the bullet behavior.

In events you’d then do something like

Start of layout 
— mover: destroy

On click
Node: path=1
Node: index=1
Repeat 10 times
— create mover at (node.x-loopindex*32, node.y)
— mover: set path to 1
— mover: set target to 1

For each mover
Node: path=mover.path
Node: index= mover.target
— mover: rotate 100*dt degrees toward (node.x,node.y)

Mover: on collision with node
Node: path=mover.path
Node: index= mover.target
— mover: add 1 to target

You can change the rotation speed by changing 100*dt. You probably want to change the bullet speed too. Too fast with too slow of turning will prevent it from being able to reach the next node, but that’s easy to tweak. You can change the amount and spacing of the movers in the event that creates them. You probably want to delete the movers once they reach the end of the path somehow.

As an exercise you could also stretch a sprite between consecutive movers to avoid visual gaps.

Edit:

Third party plugins are useful, but users seem to avoid them because they don’t like that the people that made them don’t usually stick around till the end of time to fix possible issues that come up from browser or construct change. You’re already using c2 that could possibly break from a browser change although that’s not very common. As to if third party plugins make it harder to port? That’s a question for those who do the porting.

Dude, I tried to adapt your code to my routine (which procedurally generates a wind particle every 2 seconds on the right side of the screen, making it go to the left side), but I just couldn't do it. Maybe it's tiredness and/or inability to program, but now I couldn't do it. :(

I tried to use AI to help me with the routine, but it only made the situation worse. If it's not too much trouble, could you create a CAPX example for me with this context?

There isn’t a best way. There are many different ways like I roughly listed in the previous post, each with pros and cons. But realistically you’d just pick one.

Create a sprite and call it node. Give it two instance variables: path and index. You’d then place instances of node on the layout in the shape of the path you want. Next you’d set the instance variable values. You’d set index to 1 for the first node, 2 for the second, and so on. You’d then set path to the same value 1 for all of them. You can create more paths later by just having different values of path.

Next you need something to follow the path. Create a sprite and call it mover. Give it two instance variables: path and target. Also give it the bullet behavior.

In events you’d then do something like

Start of layout 
— mover: destroy

On click
Node: path=1
Node: index=1
Repeat 10 times
— create mover at (node.x-loopindex*32, node.y)
— mover: set path to 1
— mover: set target to 1

For each mover
Node: path=mover.path
Node: index= mover.target
— mover: rotate 100*dt degrees toward (node.x,node.y)

Mover: on collision with node
Node: path=mover.path
Node: index= mover.target
— mover: add 1 to target

You can change the rotation speed by changing 100*dt. You probably want to change the bullet speed too. Too fast with too slow of turning will prevent it from being able to reach the next node, but that’s easy to tweak. You can change the amount and spacing of the movers in the event that creates them. You probably want to delete the movers once they reach the end of the path somehow.

As an exercise you could also stretch a sprite between consecutive movers to avoid visual gaps.

Edit:

Third party plugins are useful, but users seem to avoid them because they don’t like that the people that made them don’t usually stick around till the end of time to fix possible issues that come up from browser or construct change. You’re already using c2 that could possibly break from a browser change although that’s not very common. As to if third party plugins make it harder to port? That’s a question for those who do the porting.

Thanks again, dude. You're awesome!

I'm testing here using a procedural routine. :)

> without the need for plugins?

u have to use plugins for that ofc

anyway i dont see the problem as c2 has the plugin needed-pathfinding-as rojohound said

also that yt vid probaly used addons no?

Actually I prefer to don't use plugins, since I had problems before with them.

Also, my game will be ported to home consoles and I believe that using external plugins could cause problems in the conversion, right R0J0hound?