You should find a path once for each location you want to move to, then use the "On path found" trigger to start movement. See the manual for how pathfinding works.

In the new project dialog, search for "pathfinding" -- there's a demo in there that you can look at.

The Browser object has an "Open URL in new window" action.

Tiled backgrounds don't support custom collision polygons or image points. You'll need to use sprites to get those.

Modified version of eli0s's example using a loop: Loop Spread. This will avoid any picking issues that may or may not be causing the problem in the first place. Also, it's a great way to reduce redundancy.

You should make more of an effort to understand containers. They'll save you a lot of headaches here. I'd suggest reading the manual entry for them.

Alternatively, using math. You could also have platforms move in an oval this way. You can also set timeAngle however you want, such as an incrementing/decrementing value.

As MadSpy said, the expression LayoutName will return the name of the current layout, which you can see in the manual.

The events are automatically run once per frame. There's no need to setup an explicit game loop.

I wouldn't recommend using dt in a lerp function like that, as it's likely not doing what you think it is. If your FPS -- and by association, the value of dt -- starts to fluctuate, you'll find your camera jumping around. If you want smooth camera movement with dt, you should be lerping the camera position toward a fixed point between the player and mouse.

Alternatively, you could look at my Magicam plugin, which does motion smoothing and multi-object following.

Just set your camera's position to the average position between your player and the mouse. Something like:

X = (Player.X + Mouse.X) / 2

Y = (Player.Y + Mouse.Y) / 2

If you want to get fancy and control where in between the two your camera lies, you can use lerp:

X = lerp(Player.X, Mouse.X, 0.25)

Y = lerp(Player.Y, Mouse.Y, 0.25)

This specific example would place the camera 25 percent of the way from the player to the mouse.

Strings(text) need to be enclosed in double quotes, so you would put "NINJA" instead of NINJA.

Running in debug mode comes with additional overhead, which can result in decreased performance. When you export your game, it won't be running in debug mode, so you'll be fine.