to get the turning done you could use torque or apply impulse or force to an offcenter point. Using none physics behaviours will give unwanted results as yoy have noticed.

system every tick - system scrollto player.x, 350 (or whatever other y suits you)

Have a look in the tools/resources part of this forum, there are multiple threads about this.

Are you turning using physics?

If you are not, that will be the issue..

You can use:

round()

ceil()

floor()

put the expression between the brackets.

https://www.scirra.com/forum/viewtopic.php?f=147&t=94133&p=731518&hilit=angle#p731518

I made an example for this on the forum not too long ago.

I will have to search the forum to find it.

there's an old example in the arcade, which I adjusted to recognizing the slope angle as explained in the above posts.

You were saving your highscore to webstorage every tick, even when score wasn't higher than highscore.

Highscore is 0 when the layout starts, so 0 was saved to webstorage.

Instead of saving your highscore to webstorage every tick without any conditions you could try this:

<img src="https://dl.dropboxusercontent.com/u/48563442/highscore.jpg" border="0" />

Everything is working just fine here..

You are just not setting the text of the modomode every tick, but the rest is working just fine.

I understand what you are trying to do.

I'm just saying the second event will not trigger if the first event is triggered, because after the first event highscore is the same as global.score, but maybe you aren't explaining your events right.

Could you please upload a screenshot of your eventsheet so we can look for where the events are flawed?

In the gameover layout, If Global,Score > highscore

highscore set to Score.

t2 set to highscore

So I want to save the high score in local.

So this is the event above.

If Global,Score > highscore

   -highscore set to Score.

   -Set key"savescore" to highscore   

   -t2 set to webstorage.localkey("savescore")

I guess this could be the issue..

first you set highscore to score, so global.score isn't bigger than highscore for the second event.

It's not clear to me why you are using two events for this anyway.