Okay, that works! Thanks!

Win 10, 265 stable version seems to work as intended on my end.

But the levels aren't added, they're calculated every tick. Here's how I have it done. Scores, levels and spawners. They're all under 'every tick'.

That works on the simulation capx, but not in the real game. In the real game the level is counted every tick against the score which is updated every tick based on how far the player is traveled.

Since the level is updated every tick, so the horns are also updated every tick, causing them to grow full lenght in the first level. I'm starting to think that instead of tying it to the level, I could just spawn invisible barrier every level as checkpoints that'd grow the horns when passed.

Unless you have a better idea?

It happens to my every post, code symbols or not. Real annoying tbh, especially when asking for help. I understand it's an anti-spam measure, but it goes too far if it starts working against paying customers.

Okay, I'm not really following you.

If I put it to start on layout, the horn stops growing altogether. That event is there that keeps the horn growing, if you run it once it only gets run once.

Of course that is the problem. I need a way around it.

I have been wrecking my brain with this problem for three days now, so I think I give in and ask for help.

In my game, you play as a sheep with horns that grow when you level up. Wrecking stones and things with your horns make them break a bit, regressing a tick. I can't get the latter part to work.

Clearly the problem is that the horn growth is tied to the level. So even when I decrease the horn growth variable, it grows back up in the second because of the level. I'm just too dumb to see a way around it.

Here's the capx link that illustrates the problem.

https://mega.nz/#!DVdwDAAA!ncdLV3k8pi1VFrQEmC-lJpLodfIO6lju392kQ8dsHhs

Just click to try to break off the horn.

I think you mean layout, not layers.

Add event -> System -> Go to layout

Okay, I figured it out.

Physics behaviour doesn't follow the "rotate by origin point" rule. Seems fitting for the physics behaviour's DIY approach so I dunno if this is a bug or not.

I know it's supposed to do it automatically, but for some reason it seems like the origin point resets.

I made the game by editing the jumper demo, maybe that's it, maybe the demo was made before origin point. I have no idea.

CAPX here: mega.nz

Arrow keys to pivot. It's supposed to pivot by the bottom, but it does it by the middle. The little ball I attached to the origin point to find out where the game thinks it is.

Right click on top bar and uncheck "minimize Ribbon"