Queues

Each queue pairs a name with a kit. Players can join only after the queue has been finalized and enabled.

Create a queue

/queue create <name> <kit>
/queue set-flags <name> [flags...]
/queue finalize <name>
/queue toggle <name>

For example:

/queue create ranked classic
/queue set-flags ranked --weight ELO --team-size 1
/queue finalize ranked
/queue toggle ranked

New queues start disabled. finalize writes the current queue definition to queues.yml; toggle turns it on or off. Only enabled queues accept players.

Queue flags

Flag	Values / purpose	Default
--weight	ELO or None; ELO enables rating updates for queue matches	None
--team-size	Players on each side; a match starts with twice this many queued players	1
--allow-parties	Stored party-queue setting	false
--min-rating	Stored minimum-rating setting	0
--permission	Stored permission node	empty
--min-party-size	Stored minimum-party-size setting	0
--max-party-size	Stored maximum-party-size setting	0 in a default record; -1 for the command flag

The current queue service uses team-size to form two teams and weight to determine whether to update ratings. The other listed flags are saved and exposed through the API, but the current join and match-start code does not enforce them.

When weight is ELO, Solar updates each player’s queue rating after a completed queue match. The default rating is 1000 and the default K-factor is 32; both can be changed in config.yml. Wins and losses are tracked by kit.

Players use:

/queue join <name>
/queue leave <name>

The action bar displays time spent waiting and the queue names the player has joined. /queue does not currently display a help page; use this guide or the command reference.