In almost all projects I do, I can't help but make objects abstract to save on the amount of code I have to write because of inheritance; however, I can't stop the feeling that this is a bad practice in some way.
For example, for a game I am currently working on, it needs dynamic coding. When the player stands or clicks on a tile, some action occurs, but I think it would be silly to create a class for every block in the game, so instead I created an abstract Action class with an abstract run() method which the tile will run on trigger.
Am I using abstraction correctly, or would there be consequences such as performance for making too many things too abstract?
I know what abstract classes are for. This question is about keeping it under control in both cases of the program's readability and debugging and also to not slow down the program (if that's possible). Also this question is aimed at all OOP languages, I just don't know their specific keywords for things such as abstract.
A very simple answer about when to use abstraction is when you want to have a default implementation, use abstract class.
So any class extending it will have to implement only the abstract methods and members, and will have some default implementation of the other methods of the abstract class, which you may override if you want.