~ubuntu-branches/debian/squeeze/assaultcube-data/squeeze

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"><html lang="en" xml:lang="en" xmlns:h="http://www.w3.org/1999/xhtml" xmlns="http://www.w3.org/1999/xhtml">

<head>

<title>Map editing: Tips, tricks and advice</title>

</head>

<body>

</div>

<h1>

AssaultCube: Map editing: Tips, tricks and advice</h1>

</div>

<h1>Map editing: Tips, tricks and advice</h1>

<p>Covered in this article:</p>

<ul>

<li>

<a href="#size">Size matters!</a>

<ul>

<li>

<a href="#wqd">World quads (WQD)</a>

</li>

</ul>

<li>

<a href="#layout">Layout and design</a>

</li>

<ul>

<li>

<a href="#2ndfloor">Second floors</a>

</li>

</ul>

<li>

<a href="#texture">Texture use</a>

</li>

<li>

<a href="#models">Mapmodel usage</a>

</li>

<li>

<a href="#lights">Lighting</a>

</li>

<li>

<a href="#items">Item placement</a>

</li>

<li>

<a href="#spawns">Spawn points</a>

</li>

<li>

<a href="#co-op">Co-operative map editing</a>

</li>

</ul>

<h2 id="size">Size Matters!</h2>

<p>

Size DOES matter in AssaultCube! Don't make fanatically huge maps as they will lag players down.

Not to mention, it will take forever for players to find/frag each other, in what's supposed to be a fast paced game.

Due to the restrictions of the cube engine, it is generally a BAD idea to try and rebuild your favourite map from

a different game, as most engines allow for larger rooms and bigger lines-of-sight than the Cube engine does!

</p>

<p>

<h3 id="wqd">World Quads (WQD)</h3>

The WQD count can be found by typing <b>/hidestats 0</b>. Some figures will appear at the right of

your screen, one of them will be <i>WQD</i>...

</p>

<p>

WQD is a good way to measure how good your map will or won't lag. Maps should ideally

average a maximum of 5000 WQD (less is better). It's okay for your map to exceed this if it's only a

little bit more in a short area. Keep in mind that lights and details will raise the WQD counts, so a rough layout

won't really represent the final WQD values of a map. In an empty map (layout is the only completed part)

which only has corridors and basic geometry, WQD shouldn't be above 1000. This leaves enough overhang for details, lightning and mapmodels.

</p>

<p>

The key to getting a good WQD count is by using occluders or "solids" (press <b>F</b>). These are full-sized walls

that block the view, and it allows the engine to know that it can stop rendering whatever is behind it.<br clear="none"/>

To undersand the concept of occluding, do the following:

</p>

<ol>

<li>

Load one of the official AssaultCube maps.

</li>

<li>

Enter edit-mode (Press <b>E</b>).

</li>

<li>

Fly above the map (beyond the skymap).

</li>

<li>

You will now see occlusion at work. The blacked out parts of the map are where solids exist,

and the engine has decided not to render past them. Parts you can see have, of course, not been occluded.

</li>

</ol>

<p>

You can toggle occlusion on and off by using the <b>F5</b> key (<b>Warning: This may be very laggy!</b>).

Viewing occlusion at work will give you an idea on where to place solid cubes while creating the layout for your map.

</p>

Keep in mind, the better your map runs, the more people will want to play it. If your map looks awesome, but

can only be run on a decent, new computer, then people won't play it as their computer simply won't be able to

100

handle it. Many AssaultCube players are still using quite old hardware!

101

</p>

102

<h2 id="layout">Layout and design</h2>

103

<p>

104

When creating a map, make sure not to make areas far too small. Six or more cubes wide is a good dimension for

105

doorways, to allow people to pass through them easily. Take reality as your guide. If you're unsure

106

about how large your door/window/stairs should be, look at those in your house or outside somewhere.

107

If players block a doorway for teammates, just because the doorway is only 4 cubes wide, people won't like

108

the map very much. Another up-side to allowing enough space in the map, is that it also gives room to plays to

109

<i>"<a href="maneuvers.html#straferunning">strafe-run</a>"</i>.

110

</p>

111

<p>

112

When you build your map, use more than one level. Flat maps are boring. By adding vertical variety, you also

113

make the gameplay more intresting. Even small alterations in floor height usually makes things more diverse.

114

</p>

115

<p>

116

Be sure that players aren't <i>"fighting the map"</i> too much. They should be fighting each other after all.

117

Also make sure that players aren't constantly bumping

118

their heads, especially against the skymap, as it can be annoying, and unrealistic.

119

</p>

120

<p>

121

Try to keep wall sizes about 3-4 cubes thick, to allow for detail and realism.

122

</p>

123

<h3 id="2ndfloor">Second floors</h3>

124

Due to the limitations of the Cube engine, it's simply not possible to build a second floor out of geometry.

125

You can however use architectural <a href="mapediting3.html#models">mapmodels</a>

126

to create them... but don't try to build a 5-storey building with them, otherwise it will be impossible to make it look

127

right, especially with lighting, since lights in the Cube engine are circular (not spherical), meaning you can't change

128

the lighting on each level of the platform.

129

By creative use of levels, you can make maps that very well give the impression of multiple floors!

130

If you use the bridge mapmodels, use it with care!

131

132

<h2 id="texture">Texture use</h2>

133

<p>

134

Take your time in chosing textures. Don't just decide by "how it looks", consider reality to be your guide.<br clear="none"/>

135

Don't put a floor texture on the ceiling, or wall textures on the floor (although there are exeptions). Try to use

136

some common sense. A nice wooden structure will probably not support a concrete roof too well, or your factory

137

will probably not have a wooden flooring. Brickwalls on the ground are very uncommon... etc, etc.

138

</p>

139

<p>

140

At the end of the texture list is a texture imprinted with the words "missing content". <b>DON'T</b> use it, it's not a texture,

141

in-fact, it's lack of a texture. It looks ugly and shouldn't be used in any map, because it's actually there to show if

142

textures and skins did not load properly.

143

</p>

144

<h2 id="models">Mapmodel usage</h2>

145

<p>

146

Though they can add some nice and neccesary detail to your map, don't heavily rely on them! It is advised to add

147

mapmodels at a late stage in mapping. Think of them more like the icing on the cake.

148

A boring room won't look better if you add lots of mapmodels.

149

When you add them, less is often more. If every square metre has a cigarette and a leaflet on the ground, the

150

effect will be lost.

151

</p>

152

<h2 id="lights">Lighting</h2>

153

<p>

154

Careful placing of lights can produce different effects. Contrast in lighting is what makes a map look atmospheric.

155

Be sure to take time placing lights correctly, don't use very bright lights to light the whole map, instead, use

156

medium-sized, mid-brightness, ambient style lights instead. <br clear="none"/>

157

A good approach is to imagine that the map is real, and then use what is appropriate for the situation!<br clear="none"/>

158

Small, bright lights (i.e. 255 brightness, 4 radius) should be used as highlights for actual light sources,

159

such as lamps and lightbulbs.

160

</p>

161

<p>

162

<b>Coloured lights:</b><br clear="none"/>

163

When adding coloured lights, be careful. Some textures can become bland if exposed to certain colours.

164

Also make sure you keep a consistent colour theme. Don't add a red, a blue and a yellow light to the same area...

165

</p>

166

<h2 id="items">Item placement</h2>

167

<p>

168

Pickups must be placed strategically through maps and do take some time to position

169

correctly. Powerful pickups should be few and not be too close to each other (unless

170

there is a good risk involved) and pickups should be well spread and not be too

171

high in number, this encourages players to move around.

172

Try to keep powerful pickups away from the spawn area so players

173

are encouraged to leave their bases. Strategy is key! A good idea to keep in mind

174

when mapping is "<i>what would I need here to help me pwn?</i>"

175

</p>

176

<p>

177

If you want a spot to have grenades for when players are playing the mode <i>Last Swiss Standing</i>, but not for other

178

modes, be advised, that pistol magazines turn into grenades during <i>Last Swiss Standing</i> mode... so if you want,

179

you can strategically place pistol magazines with this thought in mind.

180

</p>

181

<p>

182

It's a good idea to put powerful pickups in risky areas, this helps keep balance and makes it harder for

183

players to hog them.

184

</p>

185

<h2 id="spawns">Spawn points</h2>

186

<p>

187

Rule of thumb: The more, the better. Try to add as many as you can.

188

Avoid creating spawnpoints that are in the middle of a room, or a corridor. Spawning and being instantly killed

189

just because you're in the line of fire of some other players is frustrating.

190

</p>

191

It's a common mistake to new map editors to place spawn points with an incorrect orientation. If you want to add a spawn

192

in a corner, select the cube you want the spawn to be and fly over it, then add the entity while looking in the desired direction!

193

</p>

194

<p>

195

Be sure not to use too many models. Mapmodels slow down the gamespeed and that's a problem on older machines, so

196

a map that's heavily laden with models just isn't good for those players.

197

</p>

198

<h2 id="co-op">Co-operative map editing</h2>

199

<p>

200

If you'd like to create a map with friends, you can use co-operative map editing to let you build and modify maps with others online easily.

201

This mode allows you to edit maps online with other players

202

who could help speed up repetitive or boring tasks, bring in fresh ideas or spot errors you may have missed.

203

</p>

204

<p>

205

To start co-operative map editing, when in a server, type: <i>/mode 1</i> and then type: <i>/map</i> and then your mapnames name and press ENTER.

206

You will have to of made a "newmap" previous to entering the server to be able to co-op edit it. Alternatively, you can type: <i>/coop MAP</i>

207

(replace <b>MAP</b> with your maps name).

208

</p>

209

<p>

210

You will then need to <b>send</b> the map. You can do this by typing: <i>/sendmap</i> and then your mapnames name and press ENTER. Note: Custom

211

materials can't be sent, they will have to be downloaded another way if you are using them. If you are using a custom "cfg" file, it will automatically

212

be sent with the map, if there is a cfg file present.

213

</p>

214

<p>

215

Note: Some useful editing commands can't be used in co-op editing, such as: copy, paste, slope, arch, undo, etc.

216

</p>

217

</div>

218

219

Rabid Viper Productions

220

</div>

221

</div>

222

</body>

223

</html>

Older »