Back in my original project I slightly moved a "Change Attribute self.Graphics.Visible = true" and suddenly the problem went away... Now the text is displayed on top of the actor eve

So in my game I have a scene where when the player dies you can reset the scene. I have music playing, but every time the scene resets, so does the music, and it gets annoying having the song reset ev

In the actors you want moved, make a new angle attribute called angle and a real or integer attribute called distance.

Obviously, moving the line actor to the bottom of the layer is not a solution if you want the line to appear BEHIND the squares, as I imagine one would in most situations. The only thing I can think t

@Hopscotch I have zero experience with web pages and database interaction. I meant for the actual game idea itself I think I would be able to make it in Gamesalad I was just unsure about the usernames

In respect of scrollable / non-scrollable layers - and the way collisions interacts with them, I'd say it does produce consistent and expected results (although I'd agree with you that it might not be

and expected, documented results. Detecting collisions where there are clearly no visible collisions, while not detecting them where there are clearly visible collisions is unexpected and inconsisten

Advantage attributes have over tables: when an attribute is changed, rules that use that attribute are notified. When a table cell changes, rules that use any cell in the table are notified, whether t

an actor at the top of the scene that detects collisions ? (it would be invisible of course, so not visually interfere with your HUD element) It seems odd to try and force the non-scrollable layer /

Constrain MobX to MainX - ( MouseX - MainX )

where the mouse is clicked. I would like to constrain an actor, "Mob", to the opposite side of the Main Char actor from the mouse. Please see the attached graphic.

3) Place one constrain behaviour into the HUD element and set it to . . .

But In other words, actor A, the Hero, is on a scrollable layer and trying to detect collisions with Actor B. If Actor B is also on a scrollable layer everything is fine. But if Actor B is on a non-sc

detectee + detector + detection + collides + overlapping or colliding + collisions = my mind gets lost in paragraphs like this, I'm all for clarity of communication : ) - Whatever happened to naming a

when programming) In a sense I definitely attribute my love for programming to my roots as a Gamesalad developer. I am not sure if I would have fallen in love with programming if it weren't for this

scrollable and unscrollable layers. It detects collisions fine when the layers are scrollable, but doesn't work properly with actors on un-scrollable layers. The detection occurs only at the original

-new Global Attribute: ActorDied - true

Change attribute, linear velocity x to -300

(Quote)

(Quote)