Ive got a small 3 second countdown timer before my game starts, it goes 3,2,1, Play! but it appears using the change image behaviour has a restricted image size? Basically even though i have the Play

I can answer 1: Make a global, real attribute, cranex. In the magnet/crane's rules, use constrain attribute: game.cranex to self.x. Then in the car's rules, have it only accelerate if self.x is less t

3.) the magnet is part of a bigger structure, is it possible to have a "compound actor" made of multiple actors using constrain attributes, however still respecting rotation pivots?

create self attribute

make global attributes

Well it sounds like you are using one of TSB's templates to be honest. But either way. you need to place a control actor in the scene and unlock it so you can access the scene attributes. Then create

My game space is 960 px tall x 320 px wide. I have an arrow actor that is constrained to the x & y position of the mouse when pressed and it points in the direction that the player will move.

Create a game attribute called enemies.

which is an attribute already being set by the joysticks position

I have a game I am working on right now where I actually constrain the maxspeed to the distance between the actor and the mouse so that the farther away you are the faster it can go and everything wor

yea I'm sure if I will serve, but do not quite understand = /, how can show me display the left and right attribute?? Thanks for you help..

Has anyone used actor tags for anything useful other than collisions?

make a boolean game attribute called touchallowed

Set up an attribute as integer. Then make a rule in the joystick actor, that when it shows 'left' then change attribute to 2, and when it goes "right" set attribute to 3, and when yo

destroy is a bit final and resource heavy - an alternative would be to play with the self attribute alpha (found under color) - 1 is max opacity, 0 is not visible at all. you can interpolate for a smo

Has anyone used actor tags for anything useful other than collisions?

I'm not sure what you're saying for #2. For the destroying two linked actors at the same time, you could just create an attribute called destroy. Both actors would have a rule in it that checks if t

For #1, create an attribute called platform. Every time the player jumps on a platform, it gets incremented by one. Then put a rule in each platform that checks if the platform attribute is X, chang

I have a rule - Attribute - gamescore = 25 - change scene - level 2

Make a master platform actor. Give him an attribute, not game, not scene, the player. Call it like player.leave