I've hit upon an interesting issue with my top-down maze/Gauntlet-esque type game I'm working on.

* Overscan - The sides (or top/bottom) will be cut off and Apple will probably reject your game

Thanks, I will have to try the last option, but I did try the first option and it also destroyed the platform immediately.

You can leave that part of the rule blank and just use the otherwise to destroy.

It's constraining because I didn't know how to tell GS to not destroy the actor when the player is standing on it. I wanted to make sure it stays in place. I just assumed a constraint was what is need

I'm guessing the platform with the rule in is below the hero in the layer?

I have two actors, a player and a platform.

The actors at the top of the list are drifting more than 500 pixels beyond the top edge of your screen.

I'm hitting a very odd issue. I'm trying to make a top-down dungeon/quest type game, a bit like Gauntlet (retro is cool right now, right?!)

I tried combining @RThurman kinetic scroll with @Socks fast constrain and @jamie_c button list. However, for some reason when I scroll the button list to the very top and then back down, buttons from

Rotate to Position stops once it faces that exact direction, so it's better to do what he said:

If you do a search in youtube, or at least when I do a search in youtube for gamesalad tutorial, at the top of the list is this great 1 hour video. It looks like an official GS tutorial. Theres not mu

I have a button which the player should press if the random value equals the button value (1). The player has one second to perform this, otherwise he fails this attempt, and gets another (and so on)

(Quote)

280 is the self.Position.Y value for the top barrier actor. If you double-click on the top barrier actor, you can check it's position. This, of course, could be any value you like.

* Creator will sometimes crash when moving an actor from one layer to another.

Hi tatiang, I thought I had it working, but it's not. All I wanted was the actor to spawn In between two actors one at the top of the screen and one at the bottom of the screen. Both actors cover the

One way might be to just check for a collision when the actor is spawned, if it is colliding with another actor it shouldn't, destroy it and re-spawn it in a new spot. Then repeat the check...

then build the rest of the functionality/game on top of that..

Maybe the drawn out delay of the new marketplace is nothing to do with an actual code implementation... Maybe it's that ugly old GS issue of internal company politics holding it up. Maybe Mr Felter ca