Fixed the horizontal check and improved vertical check.

I was just thinking too complicated, trying to make smart loops, but could have instead just used brute-force conditions.

Which I did now, inspired by alextro .

Same link, different file: Download here

One last thing that I need to figure out is, why the dictionary with the supposed check results always contains only one key when moving to the "win" layout.

But that's not important.

Important is that the main engine runs now.

Fixed.

Did you try the debug mode and see whether any object count is rising or falling onto abnormal levels?

rexrainbow

Hey, got a little bit of a problem here that got me frustrated for quite some time now.

I got this event+actions:

Ignore the upper events, the "For each key" condition is the most important one.

For some reason, there don't appear any markers whatsoever on my map.

• Yes, the "Put on map" event trigger, cause there is a "test" in the console log.
• Yes, the coordinates that I use exist

(I would normally use the content of the dictionary, so it's just for testing purposes that I use static coordinates. There is only one key in the dictionary at the moment)

Is there any known issue in the plugin that I should know about that prevents this from working?

I tried out a loop without anything, that worked, but this just doesn't work, no matter what I do.

Apart from that, you can also try to set the scaling in the project properties to "Point", doesn't work well on all objects, but works fine with rectangles.

Note though that "Point" uses more CPU than "Linear".

To be honest, I don't know a direct solution to this.

But can you try replacing the system random generator by this or this plugin and see whether that changes anything.

Is that a

"Yeah, I found it!" ?

Is this solved then?

You'll have to use the NW.js plugin and its action Run file for this.

(Easy to use)

Are you sure that you didn't just miss it while reading the actions?

And are you sure that you are in the actions menu, not in the conditions menu?

(If in doubt, check the window title)

I changed all colors to white, but the border still remains.

So I'm afraid, but you can't change the color.

Might be one of the "border" settings that you can't change.

Adding to R0J0hound :

The only (unlikely, but maybe applicable) exception to the disability to access collision polygon points would be if your obstacles (i.e. Shadow Casters) are rectangular and not rotated.

You would now be able to get the X and Y of a collision polygon point by combining the object expressions BBoxLeft, BBoxRight and so on.