You dont see any amount of segments in the debugger ?

Seems to me that fresh created segments are all on 1 place, following exactly the same path.

In event 79, the head is unreferenced. The segments get the speed of the first head + 4. But that is not the problem. They all get created on the same place and get the same first waypoint.

No idea why 80 is needed. They have a waypoint allready, just need a new one when there is a change.

I have no idea whats more in event 80.

I have no idea when you destroy the segments.

Just rattling, never mind me.

I wonderd if those data are usefull, but all are accessable in the expressions.

Yes Sir !

(you have no idea how impressed that i am that you see that)

Lets say i have the following JSON string of a simple object.

{"c2":true,"w":{"x":7093.726399997016,"y":204,"w":151,"h":151,"l":8722530541249526,"zi":0,"hX":0.503311276435852,"hY":0.503311276435852},"behs":{"8274350867031877":{"acc":0,"g":0,"dx":400,"dy":0,"lx":7087.059999998659,"ly":204,"lka":0,"t":6879.726399997016,"e":true},"4769858671535691":{"r":10000,"c":6.283185307179586,"t":[]}},"data":{"a":5940657200540929,"f":0,"cas":5,"fs":0,"ar":0,"at":0,"rt":0}}

What do al those tags mean ? What info do they give ?

I looked for a reference doc. Cant find it.

Ty.

6000 Pixels/seconds is really a BIG speed. Lets assume that the enemy is a big 50 pixels wide thing. Then the overlap rest only 0.013 seconds. That is dedectable at 100 ticks/seconds, but i would not count on that. So even in overlap, it will miss once in a while. Collissions at that speed is out of the question.

Also, i have no idea at what rate you fire, but i can imagine that you have like 30 bullets when the enemy is 100 pixels away. So you have to detect 100 overlaps a second, kinda. A system that can all do that is awesome.

The best chances to solve this you have with a 'is greater then' or 'is smaller then' comparisation. To give it room to decide. On top it needs to fast-pick the right bullet. And it should be in the form of kinda a trigger.

To do this, i used the 'line of sight' behaviour. Add the right enemy as obstacle on creation of the bullet. Give it a small range and a small cone (i think that would be 20 in youre case, but you have to find that youre self)

If you now use the condition 'Has LOS too object', the right bullet gets picked (but also the right enemy), and in a fast way. If you destroy the bullet then, you can even have a copy of this event running to have even higher dedection rates.

I would like to see that CapX. It looks awesome.

Okay, so you want the bullet to change direction towards a moving player, so it wil always hit. Kinda like a heat-seaking-bullet.

Wel you have the bullet action 'set angle of motion'. That wil ask you for an angle.

The needed angle you get with an expression. Assuming that the name of the bullet = "bullet' and the name of the player = "player" it is:

angle(bullet.X,bullet.Y,player.X,player.Y)

Just fill that in the 'set angle of motion' action.

Basecaly you use the same tool to change angle as you use to do the motion. If you use 'rotate toward position' (by instance) you rotate the physics world, while you need to rotate things IN that physics world. You will make things go stuck by pushing them into solids, the paths will go erratic, in fact you just break the physics world.

A little warning; if the bullets always hit, the player goes erratic too.

Hope i helped.

Nopes, that does not work. Save it as Single File (= .capX).

Is that 'projectile' moved by a bullet behaviour or in another way?

How do you shoot it?

Is that 'another object' moving ? Is the 'projectile' allowed to mis ?

Is that 'projectile' allowed to align to its path or does it needs to keep the same angle ?

Most behaviours have a 'set angle' no/yes switch.

Can you confirm that those are not distorted:

https://

drive.google.com/open?id=0B1SSuCVV8v74U1BUT3NVenhvNE0

If they are not distorted in this capX, you do not have an additonal problem. You are just calling the play actions more times then you expect. Look my cap how i solved that.

If the animation speed is slower then the actual Frames/second. An actual frame will be showed in more then one tick. Therfor: youre condition is true for several ticks in a row.

Lets say the animation runs at 25 frames/second. & The game runs at 50 frames/second. Then each frame will be showed 2 ticks. And your conditions is true for 2 ticks. & then it farts, eh.

Read this and that.

https://www.scirra.com/tutorials/1112/p ... elike-game

https://www.scirra.com/tutorials/1123/s ... ke-dungeon

There is also a plugin, i did't use it myself.

plugin-random-dungeon-generator_t108708

— Here you go sir.

https://

drive.google.com/open?id=0B1SSuCVV8v74WFVYWDYwRVZVd3M

But you may have to pick the nearest, instead of in creation order, to aclompis wat you want.