search

gbusto / BrickBreak

An attempt to make a game like "Ballz" or "Bricks and Balls".
1 stars 0 forks source link

Balls Sometimes Won't Move to the Origin Point After Hitting the Ground #578

Open gbusto opened 5 years ago

gbusto commented 5 years ago

The reason for this might be because in the BallItem.stop() function, we removeAllActions from the node when it might be in the process of being moved to the origin point.

gbusto commented 5 years ago

Could also be due to the function BallItem.resetBall() node!.removeAllActions()

gbusto commented 5 years ago

Moving this to a future release.

gbusto commented 5 years ago

I think the solution is separating the .stop() functionality and .moveBallTo() functionality. Maybe in BallItem.swift at line 144, the action timer ends before the ball made it back to its specified location.

gbusto commented 5 years ago

I've seen this issue again. Need to fix it.

gbusto commented 5 years ago

Balls sometimes even end up off screen somewhere and get stuck. This needs to be fixed this time around. One way to test this is to add code that forces the balls to move to a particular spot "pretending" that that's the new, unfettered origin point decided by the game and my code for moving the balls to back onto the game floor should be able to fix it and work.

gbusto commented 5 years ago

Still happening...

gbusto commented 4 years ago

This still happens occasionally. Need to reopen and attempt to fix this.

New branch is here: i578_balls_still_dont_return_to_origin_sometimes. It's not happening at all now... but it still does. Going to leave this be for now.