The bullet does not get destroyed unless you tell it to be destroyed, so it's fine?
It's not possible to help with this without seeing the file or at least a screenshot of your events.
Looking good, but possible FPS issues there?
What you're looking to use is 'set bullet angle of motion' instead of 'set angle'. I assume you bumped up the speed on the balls which don't have stepping. 1500 speed is good for the ballstep objects.
Just saying you may have saved it on a beta on one device and now you are on stable, what version is it showing? I didn't see that error before so I am just going off that. You can bring Ashley to the post, he might be able to recover something. Also it's a full game and you don't have back ups?
Develop games in your browser. Powerful, performant & highly capable.
You should make back ups. Do you definitely have the latest version of C3 installed, if so what version? Also there's a chance it's not properly installed due to browser or cache issues. Share the file maybe someone can open it. Worst case maybe Ashley can attempt to recover it.
It is like this by default. If you said bullet on collision with object A > destroy, why would it be destroyed on collision with object B?
Yeah not instance variable, it is a condition on the object you can 'set y' every tick, so you can set y to current y + or - a value which moves it. For clarity.
Are you sure that's a screenshot of your code? :) You use an instance variable on the platform and depending what it's set to, you do object set Y to self.Y+value to move it down the screen, or object set Y to self.Y-value to move it up.
If you are making a top down tank game then you should really make use of the Pathfinding behaviour. Check it out!
If you use the event above running every tick then it should be setting position to the enemy constantly as it moves.
To keep locking on in general you say 'pick nearest' enemy to player (a condition on the enemy object), set black box position to enemy.
Member since 5 Aug, 2013