you are correct except it is not colliding with anything…
the bullets themselves do not collide with players only ground/walls/etc. and then explode doing damage to players.
therefore i dont think that is the problem…
you are correct except it is not colliding with anything…
the bullets themselves do not collide with players only ground/walls/etc. and then explode doing damage to players.
therefore i dont think that is the problem…
All right, then you’ve got to put in some print lines and find out the root of the problem!
seems to work after changing this statement…
while (locx != destinationX && locy != destinationY)
to
while (locx != destinationX || locy != destinationY)
does that seem right?
Ah, yup, you’re right! My fault.
Very well done fixing that bug though. Basically it originally said that it would only continue as long as both components were wrong, but you want it to continue as long as either is wrong.
Glad it’s working now!
is there a certain case where this would still fail? every now and again the ball will stop at the height of its path.
i think i fixed it. it had something to do with my data type conversions.