...particulary making PlayerPawn child of Actor which is in common progs now (as well as PlayerPawn itlsef).
While this change keeps everything in original game logic, it may cause a separation of two class branches - custom game Actor and custom game Player Pawn. Since Player's MO is still, after all, an actor and a game object, it might have to share some behavior with custom game Actor; and in whole this becomes a bit complicated, one have to either duplicate behavior code for both custom Actor and PP, or derive custom PP from custom Actor (derived from common Actor) and duplicate common PP's behavior fully in custom PP class.
Not that I am complaining <!-- s:roll: --><img src="{SMILIES_PATH}/icon_rolleyes.gif" alt=":roll:" title="Rolling Eyes" /><!-- s:roll: --> , but was this really necessary to make things be like that?