Change attribute "self.physics.movable to true"

I may have missed something but it seems like you're overthinking this. Create a boolean attribute called game.carrying and set it to false. Create a boolean attribute in the roaming actor called se

If X or Y is attribute, the rule will behave as if it is turned off. Occasionally, it will TRY to run correctly, but after a second or two it will crash with no warning and without BugSplatter.

if Att scene.pickup=2 do not constrain to main actor. This kills all constrains on roaming actors dropping everyone.

Hey folks we are working on a game which uses a pick up mechanic and we are a bit stuck on constraining.

By any chance do you have an actor that is controlling when the dragonfly is spawning? And by any chance are there constrain behaviors in that spawner that are messing with the values of 'game.Dragon

demo that Armelline posted. It involves an actor attribute (StartingY) which is used to spawn the dragonfly.

Other than that better physics and custom collisions are more vital to game makers.

That's because the value is less than 1 for your row/column value. You can't access a row/column that doesn't exist and there is no zero. To avoid this you wrap those rule that say when attribute or a

Every time I try to use tablecellvalue in a rule (ex. if attribute = tablecellvalue(table,y,x)) and hit the previewer, it just goes crazy? like I don't even know how to describe it, it just doesn't wo

Maybe when you "jump"...make a Boolean that becomes true...then make a rule in your fire button to include an attribute that when "jump" is true plus what ever ithe

I'm guessing the issue is with your rule conditions but without seeing your actual rules I can't really answer that question. In general, tables work great. But as I'm sure you know, a misplaced par

is more of a starting point. Take a look at the Collisions with Tables template and see if you can figure out how one of the scenes works. If you have questions about it, post here and someone may

OK, thanks, I'll make sure it is one rule and not using an outer rule. Also, could there be any issues with the condition checking TableCellValue(table, row, col) rather than game.credits attribute?

The link in that thread isn't working so here's the Collisions with Tables template I used to make mine: https://www.dropbox.com/s/h2xqn142i9wtey7/Collision_With_Tables.zip?dl=0.

     When attribute game.credit ≥ 100

Scenario #3 (NOT WORKING) - I have an actor which checks a game attribute, then based on the game attribute will change it's image. First time through, this works, however when the game attribute chan

Any chance you can strip out everything but those rules and upload the zipped project file? The only odd thing about your rules is that you are constraining attribute values to random values instead

constrain "die1" to random(1,6)

* constrain it to the actor you want to collide to