7 In **Domination**, 2-4 teams try to dominate the map by capturing and keeping control points on the map and fragging the enemy teams. Each control point that a team has captured will generate points over time.
14 | Kill an opponent | +1 |
15 | Own a control point for a few seconds | +1 |
16 | Kill yourself | -1 |
17 | Kill team mate | -1 |
19 As of 0.8.2, owning a control point gives your team 1 point every 5 seconds by default. The frequency at which points are awarded can be changed by a [CVar](CVar) (`g_domination_point_rate`).
21 The first team to reach the score limit (default: 50) will win the match.
25 Each map has its own number of control points. Many official maps have 3 control points, while some other maps have more.
27 All control points start neutral and are owned by nobody. To capture a control point, simply walk into it. It will now start to generate points. But beware: Your enemies can capture your control point just as easily, all it takes is just a touch.
29 Round-based Domination
30 ----------------------
31 Round-based Domination is a variant of Domination. In round-based Domination, the goal is to capture all control points to win a round. The first team to win 5 rounds will win the match. If no team manages to win in 2 minutes, the round will end in a draw and another round will start.
33 Round-based Domination can be activated with a cvar (`g_domination_roundbased`).
38 A domination map must have at the very least 4 entities.
42 dom\_team entites declare the teams available in the game and what models are shown when they take a control point. To create it, right click and go to “domination\>dom\_team”. There must be at least 3 per map: Two teams and one empty team (for when the control point is not taken).
46 "classname" "dom_team"
47 "origin" "-24.000000 0.000000 96.000000"
48 "message" "Blue team has captured a control point"
49 "model" "models/domination/dom_blue.md3"
50 "netname" "^4Blue Team^3"
51 "noise" "domination/claim.wav"
52 "noise1" "domination/claim.wav"
57 "classname" "dom_team"
58 "origin" "16.000000 0.000000 96.000000"
60 "message" "Red team has captured a control point"
61 "model" "models/domination/dom_red.md3"
62 "netname" "^1Red Team^3"
63 "noise" "domination/claim.wav"
64 "noise1" "domination/claim.wav"
68 "classname" "dom_team"
69 "origin" "-8.000000 0.000000 128.000000"
70 "model" "models/domination/dom_unclaimed.md3"
73 These are the three dom\_team entites you must have on your map. It does not matter where they are placed. The first two examples here declare two dom teams: blue and red. The third declares the “empty team”. It is best to copy these verbatim into your map, as their structure does not change (of course, the coordinates do change depending on where you placed them).
77 These are the actual control points that players will capture. They do not have any required fields, but it is often useful to name them. Here is an example of a declaration of a dom\_controlpoint entity in the .map file.
79 "classname" "dom_controlpoint"
80 "origin" "0.000000 2240.000000 608.000000"
81 "message" " has captured ^1Red Base^3"
83 The key here is the “message” field, which allows you to set the message shown when a controlpoint is captured. Generally, the format of this is " has captured CONTROLPOINTNAME". You can also use color codes in these messages, as shown in the above example.
85 Helpful Hints and Tips
86 ----------------------
88 - _(Insert Hints Here)_