I would say yes, mostly. If all you want to do is "blueprint" though, that's more aptly done with an Interface. Abstract classes should be used when you want to provide partial implementation and/or support to those future methods.
Joined: May 15, 2001
The reason for blueprinting with an abstract class. Is that I can use the same class regardless of the networking method I chose.