When move and velocity are used the actor becomes unstable. To see this use a text display to display self.position.y. It jumps around causing unintended collisions with the other actors.

It sounds like you're changing the value of one or more attributes and you have rules that destroy the tabs actors based on the value of those attributes. If you don't want the tabs to be destroyed,

I have noticed I am collecting a large amount of game attributes starting to build up in my new game, can you put attributes in groups yet or no? If no, will it ever be added?

condition for spawning is that the actor's row attribute is less than the max number of rows in the table. So if there are 2 rows of actors and 2 rows in the table, nothing happens. But once a new

You can use multiple actors. Use one as the main actor, and constrain the other actors to the main actor's location.

Yes I can make a game level attribute of gravity...in a platform style game...but geez then I have to go and click every other actor I dont want to have gavity but not allowing it to move....but what

check that value. They also each have a column attribute (self.column) that contains their placement in the grid. So the first on the left would be 1, the second from the left would be 2, etc. The

(Quote)

Unless (through an attribute) you trigger an actor on another layer to spawn - so a collision on a scrollable layer could spawn (via > attribute > spawner on the target layer) an actor o

(Quote)

The new attributes involved, narrowed the entire thing down to a single rule, as well as giving the player the ability to modify their attack and defense levels with the gem and self powering systems{

just a constrain attribute and collision and delete after going down the screen

was that it was taking way too many actors for collisions and slowed down the game. And if they were to increase the price of yearly/monthly subscription, and speed up their process of implementing f

You didn't say I have to make any attributes, is that true?

(Quote)

Change attribute self.random to random(tableCellValue(tableName,1,3),tableCellValue(tableName,1,4))

As for trial and error, I spend a lot of time setting up Display Text to act as debug tools that let me see what each function is doing, but even still I sometimes spend 45 minutes out of every hour t

it seems to require adding an "Object Attribute [Visible] = True" type rule on top of the mouse-inside and mouse-down rules for every button, and then finishing each instruction set

change attribute

change attribute