You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we expand the capabilities of the team matchmaker we will need the ability to configure game options from the server. For example in larger matchmaker games (3v3, 4v4+) we may want to disable fullshare (which is currently hardcoded to always be enabled because we wanted it for 2v2).
We should add a new game launch option called game_options that is a dictionary mapping option names to values. For example:
Hardcoding them based on team size is not a good option, because we probably want to have two different 4v4 queues, one with fullshare and one without.
As we expand the capabilities of the team matchmaker we will need the ability to configure game options from the server. For example in larger matchmaker games (3v3, 4v4+) we may want to disable fullshare (which is currently hardcoded to always be enabled because we wanted it for 2v2).
We should add a new game launch option called
game_options
that is a dictionary mapping option names to values. For example:Ideally we would pull these from the queue definition in the database, but for now it might be OK to hardcode them in based on team size.
The game launch options are defined here:
server/server/types.py
Lines 22 to 30 in 716717f
And they are set here:
server/server/ladder_service.py
Lines 437 to 440 in 716717f
The text was updated successfully, but these errors were encountered: