Confirmed, being in 4.21.0. Pretty reproducable, using PlayerState right in OnRep_PlayerState() itself. So I decided to handle every PlayerState-related thing on Server from there on, which works and throwing a log there to remind me that “sometimes” PlayerState is invalid on Client.