Hi Lee, Apologies for the issue. As you mention - it appears that the issue was due to a Redis failure - and some fail-over handling in our API Servers that didn't seem to work properly for all servers. This resulted in some RTT errors for some apps. The issue has since been addressed (by rebooting the failing servers). We're going to do a post-mortem on the Redis fail-over code to see if we can find the offending code-path - and we've added additional monitoring alerts that will look for just this sort of error in the future so that we can act upon it immediately. Thanks for reporting it! Paul.

@Paul-Winterhalder said in Matchmaking: Search Multiple Lobby Types: that Thanks Paul, I don't think I could do the different lobby info option as I would like the players to choose specifically which game mode and if I understand correctly, I can only do that by having the players search for a lobby of that game mode. It's not too much of an urgent issue, I just wanted to put it out there and see how realistic it was. I talked to Greg a bit and we discussed joining multiple lobby types at once. For now, I plan to search for multiple lobbies at once and cancel matchmaking for any possible 2nd joined lobbies.

Thanks @Paul-Winterhalder

WOW, Thank you Paul

Hi @Alexandru , We've just officially added the Segment call you're looking for to brainCloud 4.55 - which is targeted for release in the next ~30 days... Updated Roadmap here - https://portal.productboard.com/braincloud/1-braincloud-baas-roadmap Paul.

@Paul-Winterhalder Thanks Paul, looking forward to any possible solutions.

Hi Bigzer, We aren't aware of any issues running our javascript client lib under Edge - and haven't been able to repro your issue. I'm not a javascript guy - but I'm noticing other warnings / errors there - do those also happen in Chrome? Paul.

@David-St-Louis-0 @Paul-Winterhalder Hi again. I would like to debug my server locally, in Unity. I have the _S2S stuff all hooked up as described in the walk through. But then I tried to do the following (actual numbers redacted) #if UNITY_EDITOR var appId = "00000"; var serverName = "MyServerName"; var secret = "00000000-0000-0000-0000-000000000000"; _lobbyId = "00000:myLobbyTypeId:00"; #else // Load environment variables passed in by brainCloud to our container var appId = Environment.GetEnvironmentVariable("APP_ID"); var serverName = Environment.GetEnvironmentVariable("SERVER_NAME"); var secret = Environment.GetEnvironmentVariable("SERVER_SECRET"); _lobbyId = Environment.GetEnvironmentVariable("LOBBY_ID"); #endif However, I am getting a perpetual error: #S2S S2S Failed: {"packetId":1,"messageResponses":[{"reason_code":40613,"status_message":"Processing exception: Unrecognized lobby: 00000:myLobbyTypeId:00","status":400}]} I even signed up for a Dev+ subscription, just in case that was the problem, per this thread. No luck. How can I test my server code locally, while still planning for the full-on S2S Docker container deployment? Thanks

Hi Chris, User entities are primarily indexed by profileId + entityType - so the singleton API will scale well no matter how many players you have. That said, if your use case gets more complicated, with say hundreds of entities of a particular type per user (say maybe you are modelling user created towns, that sort of thing) - you could consider using Owned Custom Entities instead. You can define addition, custom indexes for those... keeps those lookups fast and efficient. In addition, if you end up having >1000 Global Entities, you should definitely look at switching to Unowned Custom Entities. Same deal - you can define your own custom indexes... Hope that helps! Paul.

Hi Madallin, Just send a message into our Support Chat bubble and we'll delete the team for you. Cheers! Paul.

Hi Henry, Yes the data received is in JSON. And brainCloud expects a JSON when you update the entity. What you can do is create a serialize and a deserialize method inside your custom type.

Edit . you can get all custom entities for the current user with the query { "entityType": "[entitytype]", "ownerId": "[profileId]", "context": { "pagination": { "rowsPerPage": 50, "pageNumber": 1 }, "searchCriteria": { // other search criteria here }, "sortCriteria": { "createdAt": 1 } } }

With the new include functionality I have been able to drop my script sizes by 60-90%! This cleans up the code dramatically and promotes code reuse. Excellent work to the BC team!