I figured it out. What I did was make them not collide, then set a rule to move the dot to the center of the paddle when they overlap and then change its motion once it gets there. Forces it to stay c

Hey @CodeWizard , Sorry for bothering you but can you confirm if this is something you guys are aware of? Also, isn't this an issue with the publishing side and not the creator?

I couldn't agree more. I WISH there were less games but more that were worth actually paying money to play.

Very very limited if you try to do anything it's not directly designed to do.

BuildBox is what I heard. You've proved how doable it is in GameSalad, though!

What did he make it in (if you can tell us?) It's a super frustrating, yet rewarding game. I love it. (Also...Tomb of the Mask is super cool if you haven't tried that)

Hi, I am working on a remake of orc attack (you have to defend a castle by throwing rocks down onto orcs who climb the walls on ladders). my problem: i have three ladders standing on the castle wall a

@iKandy: After you updated your app you have to delete the warning for the old version. So far I've updated 11 apps and all are published and the error is gone.

When is version 1.25 going to be release? Thank you......

No, images have to be imported as before. wow. You pulled that from 2013.

Depending on if you want the actors to move or not when the game is over it may be a good idea to make a game playing Boolean. Then place all the actor attributes inside of a if game playing is true r

My experience with this issue has been that rules you create/move/paste/edit with 1.24 will experience this bug, but ones created before the bug was introduced will work - so long as you don't move or

@luke2125 You can check this thread for answers

It sounds like you've got one Actor displaying text and you're using the same actor on both layers. When you change the prototype of an actor all copies of it take on that change, unless you unlock an

How to fix apps containing an unsafe implementation of TrustManager

The latest version of gamesalad has got issues with tables cell value and when update your game using 1.24.2, ur release game have a high possiblitly encountering these issues. (I tried adhoc n experi

For situations like this I usually make an interruptible interpolate using a constrain like this:

So Gamesalad Pro is not worth it as presumably I can still publish to these stores and save money by going through different OS directly whilst making my game in the basic version of Gamesalad?

Is there a way to maybe add a timer here or possibly make it change an attribute that once it collides it will wait till another collision?

@7brownjack it might stutter and the performance might drop , but id say try it first , publish an apk and test it if the performance is really affecting your game , wait for the next release , you ha