12-27-2013, 07:55 AM
I meant specific component classes, not actual component classes.
For example, the cFallingBlock needs a unique interaction with the world - when it hits a solid block, it either reintegrates as a block or drops as a cPickup. The cPickup needs a unique interaction with pawns - it can be picked up by them (this might be useful, though, as cExpOrb uses the same code for collection)
I think it might be best to componentize cPawn for now (and keep the cPlayer descendant), and if we ever want to componentize anything more, we'll move it "under" the cPawn.
For example, the cFallingBlock needs a unique interaction with the world - when it hits a solid block, it either reintegrates as a block or drops as a cPickup. The cPickup needs a unique interaction with pawns - it can be picked up by them (this might be useful, though, as cExpOrb uses the same code for collection)
I think it might be best to componentize cPawn for now (and keep the cPlayer descendant), and if we ever want to componentize anything more, we'll move it "under" the cPawn.