(Quote)

by shaking the device wouldn't you just be tilting really quick? if so you just flag an attribute in that direction and make the player move

create attribute score count=0

Right - after a lot of head scratching I've got a possible solution. I can't see the constrain attribute behaviour working for this for reasons mentioned in my previous post.

Another member posted (I can't remember where) if you spawn the health bar either in front of or behind the actor (I can't remember which) you can use the same game level attribute to constrain x and

Hi Socks - yes, that is in essence what I want to do. I can understand the constrain command if I had a singular character, but I'm dealing with an enemy and a collision detection actor are being spaw

Could you sum up your post as "how do I link two objects together so that one always follows the other?", if that is the question then you can simply constrain one actor to another a

I sorted that out in the end, weapon gets generated, as does an additional, smaller actor that acts as collision detector. They are linked by a common id attribute number and conditions that destroy t

gun for instance... I know how to do this using attributes but I'm a novice with tables... With attributes it looks like this

@GamingtilDawn, the attribute name and number I used were for a general idea, not specifically for use with your code. Now that you have said exactly how you are creating your powerup adjust what I sa

Change Attribute : game.bubblekidsrandom To random (1,2 )

(Quote)

(Quote)

Great post, very detail. I would like to know if its possible to put a Text along with an Attribute.

If collide then change attribute to skill+13 and powerups+1

Also, an actor can have a fixed rotation attribute; it's a checkbox under "Attributes".

(Quote)

I've read in some threads that "constrain attribute" is more likely to affect performance; I haven't come up on booleans doing that.

Don't have it change on a button press. Have the button press change an attribute and have that attribute change the scene and turn it off.

Sometimes one rule is too many. Sometimes 20 rules are just fine. It all depends on things like Constrain Attribute behaviors, Timers, Loops, etc. There's no set number that indicates a problem.