It would have to be each instance's self attribute though. I don't think it would help much to have access to another prototype but NOT its instances.

@adent42 I could be wrong but I think what @Twayne2 is suggesting is that you could access another actor's self attributes without unlocking the actor.

Then you could use the loop over table behavior, some rules and some change attribute actions to calculate the value of the expression.

could do with a few more features and tweaks, but i think it’s still a great 2d engine for people to learn on, or make good projects on when they have developed skills. it’s significantly better than

this does not happen when constrain is used in an actor moved with the keyboard but as we know on smartphones the keyboard is not used and this seems to me a very large defect precludes the possibilit

I see what you mean and I don't know how to fix that. There is a lag when dragging an actor and having another actor constrain its position to the dragged actor. So they aren't perfectly lined up whil

(Quote)

(Quote)

I can't open your files. They just get converted to how constrain.zip.cpgz.

I can't open your files. They just get converted to how constrain.zip.cpgz.

(Quote)

So, I recently got a new computer. It is a windows computer. My old computer was a MacBook Pro. I transferred my game I was working on onto my new computer, and played through the game. Everything was

Sorry maybe I will schizophrenic but I sang victory too quickly. the method I used brings me problems, so I go back to the first question, how can I constrain 2 actors so that they stick together with

Hi guys I used Constrain Attribute to join 2 actors then I put the rule to move them with the touch.

Here's another way to do it (demo attached). You don't even need the first column of your table if you use an attribute for the game number.

I have an int attribute called ScoreRow that raises by one after every game and saves the points in the table.

     Change game attribute to item's self attribute ID #

change attribute game.object to its number taken from a table

Noooo... don't spawn actors for an inventory system. Instead, just place an actor for each slot and then update the contents using a self attribute.

just at a quick glance at that thread (i’m on my phone not at my machine right now), is that using a constrain behaviour to lock to an actor to an image? good way to do things if you have a heap of im