... or top ranking for one of your apps on Google searches for GS Salad,

Place the controls on a seperate layer and switch off 'scrollable' for this layer.

I do agree with @AlchimiaStudios about the changes to font alignment being a problem though, I had to do a lot of work repositioning the text being displayed based on how many lines of text it was cal

In the past alignment was from the top of the first line down, now it seems to be center line of whole text body.

Aliens have kidnapped children from Earth, for slave labor. Families have been destroyed, there is no hope…..Nevertheless, a star is born, and being just a kid, he has promised the families of Earth,

this can't be right? how could you control a player actor that needs split second timed jumps etc when there is an unavoidable half second (at absolute best - without ANY game logic whatsoever) delay

Good to know, fixing the table references to 0's wasn't so bad. Re-ordering logic/layers sounds like a small price to pay for a very stable build.

past builds you could get away with improperly layered logic and not having to pay attention to how the code in your actors reads code related to other actors code and where they are in the layer ord

... Destroy

(Quote)

(Quote)

One level in my game goes from right to left. On this level the HUD items that should move with the player actor disappear when playing the game. The camera follows the player the same way it normally

Something to keep in mind with what @jamie_c said, it's possible that using that method you can see a flick for one frame of the actor existing before its destroyed. A way to fix that is to make sure

to edit it) if there are more than a couple of layers of "if/else" rules in one block (if this condition do that thing else if another condition do another thing else if a third con

Especially agree with No.5. It's kind of stupid that I didn't put them on a separate layer. Must fix in the next update.

(Quote)

There is no real need to destroy them . . . but if you want to or need to destroy them then you can create a rule that checks their position in relation to the camera's position.

I'm making an infinite runner-like game, but the obstacles are hand placed in the scene, they never move. The camera scrolls to the right along with the player actor.

i got achievements working using Greenworks. Right now you can really only trigger achievements on scene changes, the rest of the HTML5 APIs don't really lend themselves properly. In the screenshot be

(Quote)