That chain is not that difficult.

This is using a family, hope you are licensed.

https://www.dropbox.com/s/uwqn54ogqj7zq ... .capx?dl=0

Notice that also the hook has now physics.

Event 6 is rough raytracer.

I have no idea where you go from there.

Setting the oldX/oldY should be done every tick.

Now they only get set (and therefor change) when the conditions are met.

Bring the sub in a root event.

Share a simplyfied capx.

Use only 1 trigger.

https://www.dropbox.com/s/fufbh5vkb2ite ... .capx?dl=0

Got to place them relative to the last one.

They are probaly the same instance.

So (pseudo) Using a Family containing 'Sprite'

Sprite < Sprite X < -1024

Family > position of right most

____ Sprite > set position ... x = Family.x + 1024 (i suppuse they are 1024 width)

I think that the comments from tunepunk & ErekT about 'Where to start tho.....' are the best advise that can be given.

I can add a personal view if you want (and wanna accept that). But that defies the meaning of their comments: "Keep from existing games (genres) only what you like". But i think that a shmup is about fast reactions and the player memorizing levels and enemy attack patterns.

Maybe this needs a new perspective. Roguelike today is not Rogue from 1980.

Roguelike today (i think) is in the first place BIG MAPS. And all the other things perceived as typical roguelike are just solutions to be able to offer BIG MAPS.

Procedural (random) generation is way more easy then storing big maps in arrays. Ever tried to make an array that can represent a big map ? You will be surprised by the limits. Random (seeded) is an endless mathematical world that can be calculated on the fly and therefor does not need to be stored anywhere. Not in memory, not in the designs.

With procedural generation there is not need to design each little corner in a big map.

Procedural generation is the way to go when it is about 'only render what you see'.

It is tilebased, because tiles prune probability's.

Permadeath is just a solution to the problem that rises with storing all progress.

endless runner & reposition one object behind the other if theyre outside the screen

Endless means that those objects start outside the screen (on 1 side) and move off screen (on the other side) ?

Do they flip each pass ? Or is it a 1 time operation ?

https://www.dropbox.com/s/500ksvozsn4ib ... .capx?dl=0

Is this what you need ?

https://www.dropbox.com/s/fv9rhivgm7v9n ... .capx?dl=0

I dont under stand the 'Pick All',

currently it picks all and the sets LocalX and Y to the instance with IID=zero

Loopindex("x") * 20 = relative to LocalX

... means it should be ... LocalX + Loopindex("x")

The conditon = System > Pick overlapping point > with ... x = LocalX + Loopindex("x") and y = LocalY + Loopindex("y")