AGameSession PostLogin and PostSeamlessTravel events seem like a good place to implement generic handling for the players loging onto the server, except they seem to be fired in the wrong place during the login sequence. PostLogin is fired right before a player pawn is spawned, which is not so bad. However, the PostSeamlessTravel method is fired before any New Player controllers are created for the new world. This makes this event particularly useless. Question for Epic: can we make these fire as the last step in the PostLogin and PostSeamlessTravel sequence of GameMode? Any issues with that you can think of?
Did you try using the GenericPlayerInitaliaztion callback?
Thanks, that’s probably what I need.