We are really excited about this improvement and we hope it helps make logging in to play a better experience for you! For more details, we have a help page available. Queue dodging is a phrase that you can often hear from popular streamers who play PvP games on Twitch or YouTube. In that case, you will know what’s happening, know your place in the queue and be able to decide for yourself your next move. Remember, most servers have lots of space for you to join whenever you want! But some servers tend to be popular, so if you really want to get into one of those at a busy time, you may see the queue. If it looks like a long wait and you are eager to play, you can decide to try another server. You will then see your place in line while you wait your turn to join the server. If it is full, you will see a message that you are placed in a queue. With this new system, you will know if you are not able to log in because your chosen server is full. Until now, when a server was full, you have simply been unable to login and have been bounced with no explanation or message. “I don’t want to wait in line!”īut fear not, our new login queue system will make it smoother to get it into the game! “Queue? That doesn't sound fun!” you might say. If a pool contains multiple filters, all the filters must pass in order for a ticket to be accepted in this pool.Our new login queue now available for all servers! The matchmaker supports two types of values: text and numbers and the filters currently support four operations =, !=. These attribute values are the ones used in pool filters. When a client creates a matchmaking ticket, custom values can be added under the Attributes section. Filters #Ī filter is a way for pools to decide which tickets it will process. If we take our example with pools for each region, the default pool would be used to put players in a fallback region. Similarly to queues, the default pool serves as a fallback to make sure you can still process tickets that are not compatible with any other pool. You can also use pools to target regions, such as North America, the European Union, or Asia. In this way, you can separate pools by platform by using filters to target the specific platforms, such as a console or PC. If the ticket is not compatible with any of the pools, it uses the default pool of that queue.įor each pool, it is possible to specify hosting information as well as the matchmaking logic to use when building matches with the tickets within the pool. The matchmaker assigns tickets that do not match the filters of a pool to a subsequent pool. Pools contain filters that indicate which tickets the pool will process. Pools #Ī pool represents a dynamic separation of tickets within a queue. Therefore you do not need to update your game client to include a queue name when migrating your services. This ability to fall back to the default queue also supports legacy versions of Matchmaker where the game clients do not specify queue names. This fallback method allows you to dynamically switch to the default queue after the game goes live without changing the game client. The default queue serves as a fallback queue if the ticket created does not specify the name of the queue. It’s also useful in a game where the type of game is different, such as a competitive game with Ranked and Unranked modes. This behavior is useful when building a game with discrete game modes that don't overlap, such as Team Deathmatch, Free-For-All, and Capture the Flag. Tickets in a queue will not be matched with tickets found in another queue. A queue contains a mutually exclusive set of tickets that you can match together.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |