Kapman frequently (if not always) gets killed, when eating an energizer at about the same time Kapman is caught by a ghost. Nonetheless, the energizer is gone. If Kapman gets killed, why is the energizer gone? To make matters worse, sometimes the ghosts have even turned color (blue, using the retro theme), but still, Kapman dies. This makes for some pretty horrible, not to mention ridiculous, game play. Come on guys, Kapman has been around for several years now. The framework is here to allow for what could be a decent Pacman clone. As it is, however, it is probably the worst I've ever seen. This is especially true, if you combine the facts that Kapman sometimes still slips through walls, and that the only way in which the game gets more 'challenging' is by going faster and faster. Reproducible: Always Steps to Reproduce: Have Kapman eat an energizer, at exactly the same time he is met by a ghost. Actual Results: Kapman dies. Expected Results: Kapman eats ghost, and does not die.
sometimes after 10 seconds the picture stop 2 second and every 10 seconds the picture stop again 2 second
So far, I have not managed to reproduce the bug, but looking at the code, I think it is still there: I do not see any synchronisation in KapmanItem::manageCollision() for depending events in the same round. So, depending on the order in the collidingList, it may happen that first the collision of Kapman with a ghost kills Kapman and then the collision of Kapman with the energizer makes Kapman eat it, turning the ghosts from HUNTER state into PREY state, although Kapman is already dead. (Afterwards, undefined behaviour is plausible.)
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.
(In reply to Justin Zobel from comment #3) > Thank you for the bug report. > > As this report hasn't seen any changes in 5 years or more, we ask if you can > please confirm that the issue still persists. > > If this bug is no longer persisting or relevant please change the status to > resolved. Still present in 21.08.3.