If you want multiple zoom points, then create invisible hotspots with data for the camera attribute changes.

another suggestion would be to make an invisible actor on the same layer as the collidable object and constrain invis actor's position to the HUD actor on a different layer.

From my experience you should have any actors that you want to collide be on the same layer...I don't know if you can detect collisions across layers but why would you want to?

Can collisions be detected properly on actors that are on scrollable and non-scrollable layers?

How would I go about adding a different amount of spawned actors in a new level so level 1 = 7 level 2 = 14 level 3 = 21 ect, I have tried making a new spawner and integer attribute for the new level

(Actor touch released OR Actor touch outside) AND (attribute X is true AND attribute Y is true AND attribute Z is true)

.....Change Attribute: self.alpha To 0

i solved the affection by gravity part i did a constrain attribute and constrained the position.y to the y i want on each platform but what about the other part?

the self graphics visible attribute cant be changed in game

Game attribute:

Unfortunately no, at this time you cannot really even mimic something like touch only affecting non transparent areas with the technique rob has mentioned. What he mentions is for actor collisions and

yep like slick said, you just want to make sure to have and your save attribute behaviors saving the attributes right after a change happens, and have all your load attribute behaviors on the first sc

You use the behaviors "Save Attribute" and "Load Attribute" on the data you want to keep track of and display at a later time. This stores the information from any

That would be polygon collision and it is on the roadmap, you can get creative with very thin/small invisible actors defining the collisions for your visible actor. (Image)

What you are describing here Is basically how attributes work in GameSalad. There is a wiki page that will describe all the different types of attributes, and what they are for, and a lot of other inf

Thanks so much! I'm learning all this as I go...is an "attribute" in game salad akin to a variable? Can they be matrices? I'm so grounded in OOP I'm having a hard time switching over

That would be a behavior not an attribute

Thanks but on No. 1) I can only use an attribute if I put it on scene, isn't it ?

route you simple need to add a couple self attributes start.x and start.y

When attribute self.rotation equals 0