Attempting a simple set-up where players can run around and pick up items in the map. If a player is killed, they re-spawn and retain all the items they’ve picked up.
My first attempt was to store these variables in the Player State, then, on re-spawn of a client, grab all the data from the Player State. Apparently Player State doesn’t work in a replicated environment. The cast to the Player State references a player index (default is 0) only the first player in the game gets saved data. So this system works perfectly for one player but no other players get data.
So my question is, how/where should I store player specific variables that survive a re-spawn in a replicated environment? Anyone have any thoughts/tutorials/videos that might help me out?
A new player state is created when a player enters the game (LogIn). It is a replicated variable, owned by a Player Controller (you can get the player controller reference by using Get Owner and casting to the controller).
You can grab all player states inside the Game State class from the “Player Array”. Once the player LogOut from the server, the player state is destroyed (afaik). You can store persistent information inside GameState, too. But try working with the Player Array to grab all the player states and save all of them in a for loop.
Don’t suppose you know of a tutorial or video that shows this?
You’ll have to forgive me, your explanation is a bit over my head. So are you saying that I SHOULD store player specific variables in Player State? I tried putting them in Game State and only the server would access it properly.
