You can store the original value in an attribute before you change the size. And then set the width and height to that attribute later.

what i did to make it grow is I used change attribute ( self.size ) to (self.size.width) +100 then repeated with heigt, works GREAT, but I can't do the reverse.

Yeah maybe constrain X and Y?

change attribute self.randomRow to random(1,tableRowCount(tableName)). change attribute game.NumberToPlace to tableCellValue(tableName,self.randomRow,1) Add/Remove Table Row [remove] [at index: self.r

I actually haven't used the tool in a long while, but I'm pretty sure there isn't a way yet to adjust Actors' collision borders. One way (which is slightly a bit more costly) is to make use of 2 Actor

Thanks. The Y constrain makes sense and works. Yes, there is extra spaces so do I just need to trim/close the actors as close as possible? Or, is there a way to place an offset on their collide?

I have tried particles, but get very patchy lines, not a solid straight line. The only thing I can think of is to make a "line" actor and constrain it to the position of the initial

The instructions that I have found include the CHANGE ATTRIBUTE: Current scene.

Example: When device.screen.size.width is 480 change attribute self.position.y to 10.

This weekend i finished the code for a complete 11 touch multitouch system. Those new multitouch attributes allowed me to slim it down to two actors with 11 rules each and one game level attribute and

If you log or display the value of self.CompanionValue, what shows up? Is it the value you're expecting from the table?

I have a "main hero" the is controlled by the player. His X,Y is being a relayed to a global attribute lets call "Hero Value X and Hero Value Y".

@colander hey bro! I came up with this new idea uh if game.score = 5 then change attribute to game.spawn to game.spawn0 . does that make sense?

A few notes due to cut offs. The first change attribute is a %(row count) to keep the table looping through rows.

"By the way, you can interpolate the camera origin without using a moving actor. You just interpolate the camera origin attribute directly._"

By the way, you can interpolate the camera origin without using a moving actor. You just interpolate the camera origin attribute directly.

However, there is an issue with getting it to spawn more than one object per Row automatically. I have an attribute that tracks what column it just read, and then advances to the next Angle column at

Ok, I've got this scene 320x4800, it's a puzzle game where you solve a puzzle and the camera pans up Y to the next puzzle. I have an invisible mover with a constrain camera rule that when the score re

Change Attribute moveDirection to Random (1,4)

You don't need to make double graphics just use the screen size attribute like this binary or just put this code inside every actor you have and it will convert it to iphone 5 screen size