hplayer | A multi-screen player using Qt + FFmpeg | Build Tool library

Try this, I have introduced a new boolean variable this.winner as false and I checked it in the checkTie() function. and in gameOver() function I made that variable true

Your issue is about the second declaration the signature didn't match to the interface : this compile :

Your problem is that you are breaking all the laws of game collisions.

_{Note this is all a little tongue in cheek but nevertheless valuable advice}

1. Never ever move to a position inside an obstacle... ever!
2. To move from here to there you move over all the points between.
3. You can only hit one thing at a time, and it will always be the closest to where you are.
4. Every collision creates a new direction with a new destination.
5. A journey takes time, always complete the journey.

If the object ends up inside something you are in an impossible situation, there is no mathematical solution, you can not move through solid mater. You must never break this law, all the other laws can be bent a little, but break the first law and you have a bug in the game.

Think of the real world, when you move you move along a path. If something is in your way you can not move through it. In a game you render the scene as a sequence of frames, and when you move the character from one point to the next, you are using teleportation. You can't do that, you must create a path and test if that path intersects any obstacles, if you skip an obstacle you may end up breaking the first law (you can't do that).

The obstacle closest to the start of the path is the one you will always hit first.

When you hit an obstacle you will bounce off of it, that will change the direction and the path you are traveling along. In the game you are animating at 60 frames a second. That means that the journey is 16,667 millisecond long, if you hit something it will be at some time between the frames. You must move to that point in time.

So now you have hit an obstacle at some time between the frames and have a new direction and a new destination. You also have the remaining time till the next frame. To complete the journey you must do it all again. To complete the journey you must do every collision until you have traveled the 16,667 millisecond in time to the next frame.

From one frame to the next you can have many collisions, if you don't do every one of them, in the correct order, you will end up getting stuck, or moving unnaturally, or worse and break the first law.

Some posts with examples on collisions. The first two are what I think you are looking for.

• AABB platform character collisions
• AABB rectangle finding the first collision along a path to use the demo follow the instructions, but draw a small box at the start or there is no room to move.
• Rectangle Or Ball basic collisions

• Balls and slopes

• Basic box collision physics

• Quick test is point inside rotated rectangle
• Breaking the first law Unstoppable force meets unbreakable object. Though not applicable the demo can be used to illustrate how breaking the first law destroys the illusion that objects are solid.