03-04-2017, 02:43 AM
03-04-2017, 07:16 AM
Gametypes are a tough place to start if you're just getting used to the language and our codebase (both of which are large tasks). They have bits and pieces in a few places, not very organized yet.
CA in particular has a lot of weird hacks throughout the codebase to support what it does (keeping players as spectators but keeping their score and team). the .caplayer field for example tells other code not to change the player in too many ways.
The part that blocks joining though, would be in the CA mutator file, in the PutClientInServer hook. It transmutes the player back into an observer when they try to join.
CA in particular has a lot of weird hacks throughout the codebase to support what it does (keeping players as spectators but keeping their score and team). the .caplayer field for example tells other code not to change the player in too many ways.
The part that blocks joining though, would be in the CA mutator file, in the PutClientInServer hook. It transmutes the player back into an observer when they try to join.