Lets say I shot a fireball from a dragon, and when it hit another dragon, I told the fireball to be "Destroyed". It doesnt seem to honor this.
It seems to apply to all actions as long as an object is shot. For example, if I shot a ball that bounced of all edges, it would not bounce, but the original object that is used as a template (e.g. the one outside the arena), does work.
This is rather counterintuitive but I wouldn't call it a bug - shot objects have behaved differently from created ones throughout the Click range, and I've always considered them more separate objects that travel in straight lines and happen to share animations with the original objects.
I'm surprised that destroying doesn't work, though - that's one of the actions that has an effect on shot objects.
Destroying objects DOES work. If you cannot make it work, send me your application and explain to me where to find the problem.
Oops, my bad! Didn't notice that I didn't code that bit. On the other hand though, maybe there should be away to control shot objects regardless of anything, in the case of a game where lets say something shoots a ball that must bounce around the level (as original post). Maybe another qualifier (Group.Shot)?
The way to control the shot is to to it manually thru the events and not with the "shoot an object" command.
I do agree it would be nice to get some control on the shot objects but thats something for the future. Today you will need to shoot your object differently if you want to control it and not just shoot it.
"shoot differently" means that you must create your object, change its movement to "bouncing ball", set its speed and set its direction.
(maybe the shoot action should do that instead of give a strange behavior to shots)
The easiest way to do this is with a vector movement and the use of the clickteam movement controller.
Ok, thanks for the help everyone
Posting Permissions
Reply With Quote