Difference between revisions of "Quickplay"
m (link to main menu) |
GrampaSwood (talk | contribs) m (→Using Quickplay: mc) |
||
(24 intermediate revisions by 15 users not shown) | |||
Line 1: | Line 1: | ||
− | [[Image:Quickplay.png|thumb| | + | {{Removed content}} |
− | Quickplay | + | {{Quotation|'''The Engineer''' on jumping into servers|The hand is '''quicker''' than the eye!|sound=Engineer_dominationdemoman05.wav}} |
+ | [[Image:Quickplay.png|thumb|300px|The "random gamemode" Quickplay illustration.]] | ||
+ | '''Quickplay''' was an automated game-connection system in ''Team Fortress 2''. It allowed players to leave finding a server to the computer; it was most notable for permitting "ad-hoc" connections to servers, as well as shining a ''de facto'' spotlight on [[community servers]]. It was ultimately replaced in the [[Meet Your Match Update]] with [[Casual Mode]]. | ||
− | == Using | + | == Using Quickplay == |
− | Quickplay | + | Quickplay was accessed from the [[main menu]] of the game. The button "Start Playing" would open the quickplay dialog. The quickplay dialog allowed the player to specify roughly what they are looking for by selecting the game mode they wanted to play. |
− | + | Additionally, there was the option to filter based on server owner; [[Valve]] and/or the community. Valve servers provided a more vanilla game experience, while community servers usually run some sort of set of [[modifications]], ranging from custom [[maps]] to new game modes. | |
− | + | Finally, there was the option to play community maps from the [[workshop]] as well as [[beta]] maps. | |
− | + | == The Quickplay algorithm == | |
− | + | Valve has not officially documented the exact game-connection algorithm. However, they have noted that it involved servers building up a reputation from how long players are connected to them on average. In general, the system took into account a variety of factors such as: the latency of the player, the player’s number of hours played, map, current number of players, maximum number of players, and the server reputation score. | |
− | == The | ||
− | Valve | ||
=== Requirements === | === Requirements === | ||
− | + | Servers had to satisfy several requirements in order to qualify for quickplay, although there may have been more unknown criteria: | |
− | Servers | ||
* {{cvar|sv_cheats}} must be off. | * {{cvar|sv_cheats}} must be off. | ||
− | * The map must be one of the approved quickplay maps. | + | * The map must be one of [[:Category:Quickplay maps|the approved quickplay maps]]. |
* [[Friendly fire]] must be disabled. | * [[Friendly fire]] must be disabled. | ||
* Random crits must be enabled. | * Random crits must be enabled. | ||
* The {{cvar|maxplayers}} setting must be 24, the default setting. 32 always makes the server ineligible, while values in between apply a gradual penalty. | * The {{cvar|maxplayers}} setting must be 24, the default setting. 32 always makes the server ineligible, while values in between apply a gradual penalty. | ||
* The server must have a registered server account. | * The server must have a registered server account. | ||
− | * [[Highlander]] mode must be disabled | + | * [[Highlander]] mode must be disabled. |
− | * [[VAC]] must be enabled | + | * [[VAC]] must be enabled. |
* The server must not require a password. | * The server must not require a password. | ||
+ | * No messing with the [[MotD]] such as forcing players to view it, forcing HTML on and so on. | ||
+ | * No selling of gameplay advantages. | ||
+ | * The server must not attempt to disguise its [[Bots]] as human players, as in giving the bots a ping and/or custom avatar on the scoreboard. | ||
− | === | + | == Policy of Truth == |
− | + | Quickplay servers were required to be honest about metadata. Player counts, players being identified as bots and server tags must have had accurately reflected the server configuration. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | == | + | == See also == |
− | * [[ | + | * [[Casual Mode]] |
− | * [ | + | * [https://web.archive.org/web/20210302211648/https://support.steampowered.com/kb_article.php?ref=2825-AFGJ-3513 TF2 Quickplay Overview] on the Steam support website (archived). |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | [[Category:Gameplay]] | |
− | + | [[Category:GUI]] | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |
Revision as of 23:05, 2 March 2024
“Ok guys, bad news: we lost that last one.” This article documents content for Team Fortress 2 that was removed from the game. It may contain speculation, broken links or errors. |
“ | The hand is quicker than the eye!
Click to listen
— The Engineer on jumping into servers
|
” |
Quickplay was an automated game-connection system in Team Fortress 2. It allowed players to leave finding a server to the computer; it was most notable for permitting "ad-hoc" connections to servers, as well as shining a de facto spotlight on community servers. It was ultimately replaced in the Meet Your Match Update with Casual Mode.
Using Quickplay
Quickplay was accessed from the main menu of the game. The button "Start Playing" would open the quickplay dialog. The quickplay dialog allowed the player to specify roughly what they are looking for by selecting the game mode they wanted to play.
Additionally, there was the option to filter based on server owner; Valve and/or the community. Valve servers provided a more vanilla game experience, while community servers usually run some sort of set of modifications, ranging from custom maps to new game modes.
Finally, there was the option to play community maps from the workshop as well as beta maps.
The Quickplay algorithm
Valve has not officially documented the exact game-connection algorithm. However, they have noted that it involved servers building up a reputation from how long players are connected to them on average. In general, the system took into account a variety of factors such as: the latency of the player, the player’s number of hours played, map, current number of players, maximum number of players, and the server reputation score.
Requirements
Servers had to satisfy several requirements in order to qualify for quickplay, although there may have been more unknown criteria:
sv_cheats
must be off.- The map must be one of the approved quickplay maps.
- Friendly fire must be disabled.
- Random crits must be enabled.
- The
maxplayers
setting must be 24, the default setting. 32 always makes the server ineligible, while values in between apply a gradual penalty. - The server must have a registered server account.
- Highlander mode must be disabled.
- VAC must be enabled.
- The server must not require a password.
- No messing with the MotD such as forcing players to view it, forcing HTML on and so on.
- No selling of gameplay advantages.
- The server must not attempt to disguise its Bots as human players, as in giving the bots a ping and/or custom avatar on the scoreboard.
Policy of Truth
Quickplay servers were required to be honest about metadata. Player counts, players being identified as bots and server tags must have had accurately reflected the server configuration.
See also
- Casual Mode
- TF2 Quickplay Overview on the Steam support website (archived).