5 While I can't help you make a map, I can help you get it listed in the menu and working in the maplist. :p The central object is the .mapcfg file, but there's much more available.
\r
9 I Map Lists & Scripts
\r
10 (get your map listed and working)
\r
15 (get the picture and info to show)
\r
23 Appendix A Advanced mapcfgs
\r
27 Appendix B Helpful extras
\r
32 ========================
\r
33 =I. Map Lists & Scripts=
\r
34 ========================
\r
37 There are actually 3 script/cfg options available to you, each serving a different purpose and being executed at a different time during the map's life cycle:
\r
40 3. exit cfg (explained in Appendix A)
\r
42 Of these, the mapcfg is the only one that's truely required.
\r
50 The mapcfg file is basically what gets your map listed in the menu, and sets up the options needed to change to it. This file is basically required in order for your map to work, though in a pinch you could say "map mymap" in the console.
\r
51 The simplest mapcfg is simply a changelevel command, but you should usually add a timelimit and/or fraglimit to make sure your map will eventually change to the next map in the list.
\r
53 As an example, let's say I make a map called "wazat1.bsp". As long as I'm fantasizing, I might as well say this map is so well done I'm actually willing to release it for friends, neighbors, fellow forum visitors and other people who like me to judge me by.
\r
54 Let's also assume that I want domination, deathmatch/team deathmatch and runematch to all be playable on my map.
\r
56 This is very easy. Let's start with domination. I should make a file called "dom_wazat1.mapcfg" (and put it inside of the maps directory) and write the following inside of it:
\r
58 set g_domination 1 // turn on domination
\r
59 set fraglimit 100 // 100 points to win
\r
60 set timelimit 15 // 15 minute max round time
\r
61 changelevel wazat1 // now change level
\r
63 Likewise, runematch is easy:
\r
64 filename: "rune_wazat1.mapcfg"
\r
66 set g_runematch 1 // turn on rune match
\r
67 set fraglimit 1000 // points to win
\r
68 set timelimit 25 // round time
\r
69 changelevel wazat1 // now change level
\r
72 At this point I should say "okay, now it gets hard", but deathmatch and team deathmatch are easy (I skipped the comments in this one since they're fairly self-explanatory):
\r
74 filename: "dm_wazat1.mapcfg"
\r
80 Team Deathmatch is turned on automatically if the server sets the "Force Teamplay" option and plays a deathmatch map, but you can add TDM as an option for your map too:
\r
82 set g_tdm 1 // play team deathmatch
\r
83 set fraglimit 50 // how many kills to win
\r
84 //set timelimit 25 // disabled: don't bother setting a time limit
\r
85 changelevel wazat1 // now change level
\r
88 There's much more power in a mapcfg file. See Appendix A for more details.
\r
94 Unlike the mapcfg, which happens before the map loads (and is responsible for loading it), the mapname.cfg file doesn't exec until the map has mostly loaded. This file is *usually* used to set values such as what music to play.
\r
96 Another difference from the mapcfg file is that mapname.cfg is global, meaning it doesn't matter if you're playing domination, deathmatch, or capture the flag, and it doesn't care what mapcfg was loaded. It does the same thing every time this bsp file is loaded. For that reason, this file should usually be used sparingly.
\r
98 To make the mapname.cfg, make a file with the same name as your map's .bsp file, except with a .cfg extension instead of .bsp. For example, my "wazat1.bsp" map would use "wazat1.cfg". It uses the same name as your map, thus the term mapname.cfg.
\r
101 ======================
\r
102 =II. Map Descriptions=
\r
103 ======================
\r
106 So, you've got your map listed in the menu and it plays properly, but the menu isn't showing your description and picture! What manner of man would create such an accursed abomination?!
\r
108 Well... That sounds like something I'd do. :D
\r
110 Luckily getting this to work is easy. Just like you can have different mapcfgs for each map, you can have different descriptions. In fact, those descriptions now match up with the mapcfgs, instead of the bsp files.
\r
111 So, all you need to do is make a description for each mapcfg file. Simple copy-pasting will fulfil this need, though a bit of modification between versions is prefered.
\r
113 There is one crucial difference in this map's format. Like the old style, the first like is what appears in the title bar. However, the second line is the map's image file. This means you can have a separate image for each game mode your map supports, if you want: one for domination, one for ctf, one for regular dm, and so on. Or you can use the same image for all of them.
\r
115 So how to do this? Easy, just create a .txt file with the same name as the .mapcfg file. For example, my wazat1.bsp has 4 mapcfgs:
\r
121 I would then make 4 .txt files:
\r
127 Each of these files can have the same content, but I recommend you change at least a little bit of it (such as the title bar).
\r
128 Here is an example of what rune_wazat1.txt would look like (note that when you make your real file, you shouldn't tab it in):
\r
130 Wibble (rune_wazat1)
\r
133 The only map I've ever
\r
138 Weapons: Machinegun, Mortar,
\r
139 Crylink, Nex, Rocket Launcher,
\r
151 Notice the first line has the map's title (Wibble... what was I thinking?), and the filename of the mapcfg for the user to see (which from the player's point of view is essentially the map's filename).
\r
153 The second line defines where the image is that should be displayed. This can be different for each game mode, but it doesn't have to be. Note that you need to provide the right path (maps/), but you don't need to give an extension.
\r
155 The rest of the file is just plain text to print out as-is.
\r
163 In order to get Domination working well in your map, you need to place dom_team and dom_controlpoint entites. You *must* have at least 3 dom_team entities - 2 minimum teams and one blank one (empty netname and no team). You can have up to 4 teams (5 dom_team entities).
\r
168 netname name of team (Red Team). Set to "" or don't define for the required blank team.
\r
169 cnt color of the team. See the "Helpful Extras" section for info.
\r
170 model When this team captures control points, the points turn to this model. If this is the neutral team, points start out as this model.
\r
171 noise Sound to be played on the control point when it's captured. Only players nearby will hear it.
\r
172 noise1 Sound to be played to all players when the control point is captured. Also good for an annoncer voice ("Red Team has captured a control point")
\r
176 classname dom_controlpoint
\r
177 message message to be displayed to all players when this point is captured, preceded by the team's name. This defaults to " has captured a control point". You can specify different names for each point, for example " has captured the Lava Room".
\r
178 origin where in the map this point is
\r
179 wait How often this point gives its controlling team frags.
\r
180 frags How many frags this point gives each wait cycle.
\r
183 Here is an example entry in a .ent file that includes colored text and 3 teams:
\r
186 "classname" "dom_team"
\r
188 "model" "models/domination/dom_unclaimed.md3"
\r
191 "classname" "dom_team"
\r
192 "netname" "^4Blue Team"
\r
195 "noise1" "domination/claim.wav"
\r
196 "model" "models/domination/dom_blue.md3"
\r
199 "classname" "dom_team"
\r
200 "netname" "^1Red Team"
\r
203 "noise1" "domination/claim.wav"
\r
204 "model" "models/domination/dom_red.md3"
\r
207 "classname" "dom_team"
\r
208 "netname" "^2Green Team"
\r
211 "noise1" "domination/claim.wav"
\r
212 "model" "models/domination/dom_green.md3"
\r
215 "classname" "dom_controlpoint"
\r
216 "message" " ^3has captured the ^1Hallways"
\r
217 "origin" "-206.0 -488.8 -150.0"
\r
223 "classname" "dom_controlpoint"
\r
224 "message" " ^3has captured the ^1Lavaroom"
\r
225 "origin" "1457.1 19.9 -110.0"
\r
230 "classname" "dom_controlpoint"
\r
231 "message" " ^3controls the ^1Nex & Strength"
\r
232 "origin" "-259.8 299.3 5"
\r
237 "classname" "dom_controlpoint"
\r
238 "message" " ^3has captured the ^1Upper Platform"
\r
239 "origin" "539.7 1206.0 182.0"
\r
244 "classname" "dom_controlpoint"
\r
245 "message" " ^3has captured the ^1Teleport Room"
\r
246 "origin" "-1000.0 636.2 -16.0"
\r
252 As you can see in the example, there are 4 dom_team ents: one blank and then Red, Green & Blue. Each control point has a different message (giving it a special name), and the one in the hallways gives 3 frags every 5 seconds instead of just one, making it more valuable.
\r
260 Capture the flag needs at least 1 CTF flag per team, and can also make use of team spawnpoints.
\r
264 classname item_flag_team1 or item_flag_team2
\r
265 angle direction the flag will point
\r
266 model model of the flag (default: models/ctf/flag_red.md3 or models/ctf/flag_blue.md3)
\r
267 noise sound played when flag is stolen (default: "ctf/take.wav")
\r
268 noise1 sound played when flag is returned by a teammate (default: "ctf/return.wav")
\r
269 noise2 sound played when flag is captured (default: "ctf/capture.wav")
\r
270 noise3 sound played when flag returns itself (default: "ctf/respawn.wav")
\r
274 classname info_player_team1 or info_player_team2
\r
275 *note: These function just like info_player_deathmatch, but for one team only. If you don't make team spawnpoints, info_player_deathmatch is used instead.
\r
283 Runematch needs only one type of entity to work: rune spawn points. You will need at least one for each rune (5 minimum at the time of this writing), though you should probably have more than that in the map. Just give the points a classname and origin.
\r
287 classname runematch_spawn_point
\r
291 =================================
\r
292 =Appendix A - Advanced Mapcfgs =
\r
293 =================================
\r
295 ---------------------
\r
296 -i. mapcfg revisited-
\r
297 ---------------------
\r
299 You now know how to make a basic, bare-bones mapcfg to set up a couple options and load your map. However, there's much more you can do! Consider these senarios:
\r
301 1. I want to play different music in ctf and domination
\r
302 2. The laser has too high of a force for laser jumps and ruins CTF
\r
303 3. I want to create fog in my map
\r
305 Each of these situations can be resolved with ease with a little work in the mapcfg file.
\r
307 You're already creating different settings between game modes with your gamecfgs, since you can choose different fraglimits. You can also play different music. The mapname.cfg file is global to all uses of your map, so instead of using it, we'll use the mapinfos. You'll need to remove the music entry from the mapname.cfg file, and paste it into each of your mapname.cfg files *after* the changelevel command.
\r
308 So, dom_wazat1.mapcfg would look like this:
\r
310 set g_domination 1 // turn on domination
\r
311 set fraglimit 100 // 100 points to win
\r
312 set timelimit 15 // 15 minute max round time
\r
313 set changelevel wazat1 // now change level
\r
314 cd loop "8" // play music
\r
316 You can choose different music for each of your game modes by changing that last line. Just make sure your map.cfg file doesn't have a cd loop command in it, or it'll overwrite what you've done.
\r
322 In order to solve our laser jumping problem, we need to call upon another feature of mapcfgs -- map exit scripts or "exit cfgs". These are called when the map is changing, before the next map's mapcfg is run. You can use them to clean up any special changes you've made so they won't affect the next map.
\r
324 For our laser jumping example, we could do something like this:
\r
326 // set up the exit cfg so we can reset values to what they were before
\r
327 set exit_cfg "maps/dom_wazat1_exit.cfg"
\r
329 set BACKUP_g_balance_laser_force $g_balance_laser_force
\r
330 // map-customized values here
\r
331 set g_balance_laser_force 100
\r
332 // and on with the rest of the config
\r
333 set g_domination 1 // turn on domination
\r
334 set fraglimit 100 // 100 points to win
\r
335 set timelimit 15 // 15 minute max round time
\r
336 set changelevel wazat1 // now change level
\r
337 cd loop "8" // play music
\r
339 Then we would make the exit cfg, named "dom_wazat1_exit.cfg":
\r
341 // reset laser damage
\r
342 set g_balance_laser_force $BACKUP_g_balance_laser_force
\r
345 When my wazat1 map is run in domination, the laser's force will only be 100. However, before the map changes, it gets set back to what it was before. This is because the original value was stored in BACKUP_g_balance_laser_force, then BACKUP_g_balance_laser_force was copied back into g_balance_laser_force when the exit cfg ran.
\r
348 You can set all kinds of values like this, including fog and gameplay options.
\r
353 ===============================
\r
354 =Appendix B - Helpful Extras =
\r
355 ===============================
\r
360 When you need to set an entity's color or team, use these values:
\r
387 Occasionally you may want to print text in color, such as team names. Here are your options:
\r
projects / divverent / nexuiz.git / blob