I have been trying to use the larger hitbox method that TSB made, but for some reason I can't get it to work. I create an index attribute called how far from mouse and set it to whatever pixel radius

@BasGoodboy‌ -- OK, you can adjust the speed by going into the 'invisible camera control' actor and modifying the constrain behavior. Currently it reads:

Ok, so what I would do is this. 1 create an actor. 2 Go in and drag a constrain attribute in. 3 constrain the actors x position to the fingers position.( click the first field and select the actors na

Are you constraining your X,Y during touch ? if so change it to a change attribute so you will have to release and touch again to update X,Y position.

Constrain self.position.x to

Create an attribute "stopOtherAction" boolean create a rule in the walls

Change attribute game.Attribute to game.Attribute-1

connect to my server. I'm checking the callback attribute and it's always a 0, it's not inserting anything in the DB but it's not showing errors either (The game continues as expected, it just doesn'

Use either change like jamie_c says or constrain. (constrain if the image needs to be updated constantly)

In case you use a move behaviour to make it move you can use the following constrained behaviour:

I think if you name your images the actual numbers (1, 2, 3, etc..). You could place a dummy image on screen and then use a Change Attribute to change the image to the value of the random number.

currently target retina during development. I attribute this to the fact that Brian probably focusses on the device side implementation for the individual operating systems currently. Prepping for re

There are any number of ways to do this here is one. You will need to create a rule and use the Numeric Expression for the condition "When mod(your.Death.Attribute+1,5) = 4. The mod expressio

I have a bounding box actor that I use for collision and an image actor that actually has the image. I connect the two through constrain.

To set the limit for the level can be done in many ways, maybe create a chunkCount attribute that will increase everytime a new chunk is spawned and create a rule that tells the spawned only to spawn

I already have an attribute which is "Distance from Spot 1" (using the magnitude formula) which calculates how far away Spot 1 is at all times.

I have tried creating real self attributes like you said (this was also suggested in another thread), but no luck. I'm obviously doing something wrong.

Are you interpolating position.x to position.x+100 or something similar? If so, the actor will zoom off like it has somewhere vitally important to be. Make a self attribute, ideally a real attribute,

4 change if you got it, the attribute referred to the x and y position to the new resolution

In your "spawner" control, whatever actor creates units/towers/whatever for you, you need to add a row to a table that stores all the actor's attributes. The trick is to use the X or