Sign In Register

How can we help you today?

Start a new topic
Answered

Matchmaking Drop In/Drop Out

Hello,


I could not find any information in the API regarding the use of the Drop In/Drop Out option using the normal matchmaking system (not manual matchmaking). How would one drop out of a currently matched game, and does GameSparks inform the remaining user that a drop out has occurred? If so, how?


We are trying to support the idea of entering into matchmaking, and then leaving a match if a player in the match doesn't want to play their opponent. Is normal matchmaking the way to do this?


Thanks,

Ryan

MobilityWare


Best Answer
Hey Ryan,

Drop-in/drop-out was initially intended to provide Real-Time players to re-join a match if they lose connection and have their auth-details preserved with the RT server.
It also frees up a slot in the match-size limit (so you can have a lobby or map system with the RT service).

If you are not using the RT service you can manually remove players using the SparkMatch.removePlayers() function. You can see the API for Sparkmatch here.

Does that help?
Sean

 


Hey Sean,


That helps. I wasn't aware this was for the RT system, so it's usage makes more sense now.


To speak more to the feature we want to support, we have a flow using matchmaking where, 10 seconds after a pair of users has been matched, we start a challenge between these two users. Either of the users can decline the match during this time, in which case we do not start the challenge and the clients would continue trying to matchmake.


Is there any mechanism in GameSparks that informs the participants in a match that a match has been declined/invalidated? Or is this just something we'll have to create using ScriptEvents + listeners on the client?


Thanks,

Ryan

 Hey Ryan,

Yes, if a player wants to decline the challenge they can preform a DeclineChallengeRequest. When this is done all players in the challenge will get a ChallengeDeclinedMessage. You can then decide what happens on the client when this message is received. If you need to, you can also put custom code in these scripts so that the creator of the challenge can re-enter matchmaking if a challenge is declined and start the process again.

I think this will allow you to achieve the process you are looking for, but let us know if you need any more info.
Thanks,
Sean

Answer
Hey Ryan,

Drop-in/drop-out was initially intended to provide Real-Time players to re-join a match if they lose connection and have their auth-details preserved with the RT server.
It also frees up a slot in the match-size limit (so you can have a lobby or map system with the RT service).

If you are not using the RT service you can manually remove players using the SparkMatch.removePlayers() function. You can see the API for Sparkmatch here.

Does that help?
Sean

 

Login to post a comment