@ CS...
no tirts allowed in my pool CS... simply instantiate a new tGameObject instance and name it's class as anything but PLAYER... name it PLAYER2 class... ( i guess i should've called the class field subclass... easy enough to change)...
then give it the functionality player2 requires... there should be no problemos... i even envision network clients being added in much the same way farther down the line...
you can even expand the functionality of the view 'subclass' to have each player own half the screen...
hey thanks for asking this... subClass does seem like a better field description, as each tGameObject will have an entry in the subClass field to identify it's actually functional class...
--Mike
Say uhm, I don't want to drop a tirt in your swimmingpool but what about 2-player-games-on-one-keyboard where player2 uses A D W S (or any config'ed keys!) to move his player? :P
no tirts allowed in my pool CS... simply instantiate a new tGameObject instance and name it's class as anything but PLAYER... name it PLAYER2 class... ( i guess i should've called the class field subclass... easy enough to change)...
then give it the functionality player2 requires... there should be no problemos... i even envision network clients being added in much the same way farther down the line...
you can even expand the functionality of the view 'subclass' to have each player own half the screen...
hey thanks for asking this... subClass does seem like a better field description, as each tGameObject will have an entry in the subClass field to identify it's actually functional class...
--Mike