Platform game - Doubt over several enemies

Hey Ls2! I know exactly what you're saying and struggled in the beginning with that same problem. I whipped up a quick example for you to look at using the ForEach object. make sure you have it from the download manager otherwise, I don't think this will open.

The example is really generic with just some balls bouncing up and down using gravity fastloops and the ForEach object so they can all bounce correctly without affecting each other. I wish I could explain things in more detail but sometimes I don't even always know "how" things work, but that they just do lol. Hope this helps you though.

Here is an example of making enemies move with for each loops and platform movement object: Please login to see this attachment.

My example here shows how each individual object can get a platform movement object and make it act individually. It also shows how you can link two objects together by writing a fixed value of an object into an alterable value. Then scoping them out with "Alt value = Fixed value" or "Fixed value = alt value" to scope the "child" (who has fixed value of object written inside it) or the "parent" (Who has its fixed value written somewhere else) respectively. Note: those two conditions given AREN'T "Compare two general values"

For having fast loops inside for each loops, you can insert a "On each one of this object" below a "On loop" condition, though that fast loop will need to be ran inside the for each loop. If you have a fast loop that calls a for each loop inside, then a regular "On for each of object" alone will do the trick (You can still call LoopIndex("LoopName") inside the for each loop).

Yes, all enemies/squares will have an individual PMO.

In the condition:
Please login to see this picture.

The first object is what you're picking, and the second object is the object you already have picked (Have one of, either in for each loop or a special event.)

This is because Fusion only scopes the object that you click on in this window:
Please login to see this picture.

So for your example, if you have player in a for each loop, you'd use Fixed value of PMO equals PMO("Player") (Note: You only need this if you need to communicate between player and PMO)
You won't need this if you have one player and one PMO specific for the player movement.

I have used this for my game/s for a while, however I ditched PMO cause it isn't good with multiplayer (can't force position of things/gets buggy), so I use the same method for NPCs and "PMO"s written in events which works practically the same way. There isn't any performance issues atm.