* Can't copy and paste rules and behaviors from one project to another without breaking the links to the attributes- even if you create attributes of the same name ahead of time. So all those tutoria

**With a universal damage calculator, it would just come down to editing a table or expression, basically, I want to implement this formula: (target.hp-{user.attack/target.defense}) with attack's f

One is to make a new text attribute, put a space in it, and then use that in your search term - for example:

1 as I put together rules and constraints on actors in creator.. I notice a tremendous slow down in GS creator. More than I would 'expect'. Is there a fix or maybe a way to increase RAM allocated to G

I do know of two ways to "move" the actor up, but requires I replace an older actor up top with the new actors behaviors via the behavior attribute section{putting all attributes in

change attribute: self.counter to game.spawnorder

I just added a game attribute called show_help

If that's the case maybe you can set a game attribute when you change your screen color like if your screen is "green" set a game attribute to 1 or "green" or anyth

An ellipse (an oval) is not too difficult, but an egg shape (wider bottom / narrower top) would take a little more work - for an oval you just need to constrain the height of the egg (how far it is ab

I see. So make the timer it's own actor and give it attributes as apposed to having the timer a game attribute?

----change attribute game.score to (game.score+1)

Save attribute is generally used for when you want to save the attributes for next time you load up the game, you can load attribute. Generally it isn't used for from scene to scene saving, for that

Can everybody know how to use "save attribute" for this video timer?

@satoshiwakata i don't mind giving you a template but it takes time to simplify it for you cause it may be confusing...the only thing you need to add to what i said before is add another attribute nam

Another way would be to constrain a large (invisible) rectangle (let's call it RangeDetector) to the player (who I assume is controlling the camera) . . . then in the windmill actor . .

I noticed than when you use a rectangle collision shape in a classic platform the actor "stop" randomly when he walk over a line of blocks. The only solution is a circle collision sh

@satoshiwakata i think it's pretty much like the concept that i used in one of my apps...what you can do is to define an attribute for each of your objects say a1,a2,a3=0 and another 2 attributes like

Socks' fast constrain method looks like it would be useful.

define an attribute (like x)as boolean..when actor 1 is pressed change it to true... in actor 2 set a rule that checks if x is true then change image

Reset scene behavior reloads a scene really quickly or instantly. If you had behaviors to build rebuild the level based on a attribute that goes from 1 to 100, you could have all 100 levels in a singl