I am working on a collaborative realtime web platform,
and have a working prototype using AWS gamelift realtime server as a backend.
For the record, I basically reimplemented the realtime client SDK in JS, but that’s not the topic here.
My question is, from AWS gamelift point of view, do I need to create playerSessionId ?
I am for now correctly creating the gameSession and for each player a playerSession, but I don’t have any need related to matchmaking or to limit the number of players in my game, or even storing data along side the user. So I was thinking I could skip that part.
Am I safe by just not using playerSession, or should I except some side effects ?
For example, will a gameSession expires no playerSession is attached to it ?