This is most likely due to the fact that game attributes do not reset when you use a Change Scene (or Reset Scene) behavior. You have to manually reset their values using one or more Change Attribute

Hold on, I know what to do - I think. I've been going about this the wrong way, because I started with the actual weapon actor having a health attribute, and that being lowered with collision, I was s

(weapon or enemy) and its that that determines collisions. When a collision occurs I have figured out how to relay that it's happened back to the original actor, but I can't figure out how to determi

You could also constrain linear velocity Y to max("a",linear velocity Y) which will always pick the larger of the two values.

Unless I'm misunderstanding, there are generic button mappings in the attribute list. These apply to most controllers. The Fire TV remote isn't a standard controller, though, so the GS team just map

if attribute linear velocity Y < "a" => change attribute linear velocity to "a"?

@AsOfLatte Anything that works with text will also work with images since you can use text in a Change/Constrain Attribute self.Image expression.

Ah! I wasn't thinking straight, I hadn't quite grasped that a change attribute action placed at the start of an actor's rule list, but not in a rule, would only occur once. It's late, I evidently need

I admit I didn't read all of this but in terms of connecting two actors, right before you spawn them, increase an integer game attribute called game.spawnID by 1. In your spawned actors, change an in

I think your problem is a global attribute.

(Quote)

are spawned from prototypes, I don't have an attribute that links them together and am not sure how to manage it. I've been trying to figure out some kind of indexing system so that every weapon and

(Quote)

@jonmulcahy @BlackCloakGS I changed my buttons to change scenes with attributes but I'm still having problems. All the scenes work fine but when I go back to the menu it is frozen.

(Quote)

Ok, that makes sense, to make it work you would need render a 3D sphere turing through a whole cycle (360°) and constrain it to the direction and speed of the actor within GameSalad.

http://forums.gamesalad.com/discussion/75220/fast-constrain-linkmachine-v2

That's probably one of the most confusing descriptions I've ever read of wanting to constrain two objects together so they both move and rotate as a single object ! (Image)

In more concrete terms, Object B constrains to Object A's rotation 64 pixels away. Object A can rotate anywhere and Object B will always stay 64 pixels away from Object A at Object A's rotation.

     Change Attribute game.paused to true