(Quote)

I am using 'accelerate' as gravity. 'Change Attribute : linear.Velocity.y = 400'

I am using change attribute linear.Velocity.y

2 attributes:

In your ball actor make an integer attribute, let's call it 'DavidHasselhoff'

Here´s the problem. I have an actor that spawns balls at random directions. The speed of the ball comes from an integer attribute i call BallSpeed. The value of this attribute increases when the playe

tatiang mentioned something about checking when the loop index is maxed out before firing other actions. I see Loop over table which has a store index in attribute. Not sure how to use this. Sorry for

Lets assume that your game contains 100 collectable items. Then create a blank table with 100 rows and an index attribute (tbl_Index) set to 0.

went into it. This isn't a question of which attribute to put where or even which function to use. Ultimately, the solution depends on how many columns (or rows) you have. If you have five, the be

You could make a straight branch that could randomly spawn other vertical branches off of it and get the desired collisions. This would also mean the branches could be different each time the player r

Yes, game.a is the attribute.

No, custom collisions in GS is not possible right now. Youd have to do a work around and drag more actors on the scene to position them to look like branches. They can be invisible, and just have your

You can think of each row and column as an attribute, because that's what they are. Tables are extremely poweful. They can be searched, organized and more. I use tables in almost each project. You can

so put the game.a under the "change the ffollowing attribute" ? Or under "which prompts user with"?

Replace the "Change Attribute" action with a "Keyboard Input" action.

* global attribute (index)

Create an integer game attribute called game.bossStatus. Set it to 0. In the boss actor, have rule that says When attribute game.bossStatus=0 and inside of that rule have a Timer set to every few se

@Armelline Like I don't know if to use change attribute or constrain it! That's where I get confused.. I know its going to be something like "game.oldx" to "self.position.x&

@armlline would I use a change attribute or constrain attribute? I was asking if you could tell me the coding to put in

@Armelline‌ so it would be change attribute game.oldX to self.position.x and in the timer it'll put change attribute game.newX to self.position.x?