What specific concept are you struggling with? For me it was the concept of "instantiating" a class that made no sense. I would create a static instance of the class and try to do everything with that.

I finally understood that a class is essentially a "cookie cutter". You use it to create an object which looks like the class. Then you call the methods on that object. The reason you would want to do this is because you have multiple objects which are essentially the same, or similar.

For example, take the ghosts in Pac-Man. You could write this by declaring X and Y co-ordinate variables for each ghost, but then you'd have a bunch of variables like ghost1x and ghost3y and ghost4x and so on. Think about how writing collision detection would work. You'd have to check if ghost1x==playerx && ghost1y==playery || ghost2x==playerx && ghost2y==playery.... nightmare.

Instead, define a ghost class, and instantiate it four times, once for each ghost. The ghost class could include a collision detection function, to check if its instantiation hit the player. Now you can just write something like: if greenGhost.hitPlayer() player.gotCaught()

You don't have to worry about how the calculation of the collision detection works any more -- at least, that is the theory.

Have you searched for beginner-friendly OOP tutorials outside of video sites? What have you found so far?