Would you be able to share more of your code (more context around where you are calling this console.log and your subscription to the playerExits event)? I’m not aware of any issues with the players object not being updated.
Just as a second hand up, I also noticed this issue.
I might be able to pin down when it happened if I look back at my logs, but not until tomorrow.
I noticed a tracking program I run on one of our spaces was reading a very high population in the middle of the night, despite me only seeing a fraction of that amount on the /app side of things.
I was tracking both player count and # of uuids in the space.
Hopefully this describes more of what had happened.
@eli@Bill_Uncork-It I found the problem. I didn’t notice that when connecting with the Websocket API, it insert your player account into the space and it never leave until your process is disconnected.
I was opening the browser and logging with my account at the same time. So, it’s hard to tell the different at that time. If you use another account for connecting to Websocket API, then you will see it works as expected.
But I was wondering if the API player can be hidden to the space. It would be a little strange to insert a API player into the space.
@jcyh Hm. Good catch, but that isn’t the same issue I am having. On the idea of hiding the API character, you could always add an exception for that characters UUID, which is the same across all spaces.