Home
Halo 2 Editing Kit Tutorial Prev Page Prev Page
Welcome
Introduction
About the Halo 2 Map Editor and its Tools
What's new in Halo 2 Editing
Technology Overview
The Halo 2 for Windows Vista Engine
System Requirements
Definitions & Terms
Definitions & Terms
The Development Environment
Map Editor Contents
Map Editor Installation
Additional Tools and Utilities
Development Tools Overview
.ass Exporter
Halo 2 Tool
Halo 2 Guerilla
Halo 2 Sapien
Halo 2 Map Editor Launcher
Using .ass Exporter
Using .ass Exporter
Using Halo 2 Sapien
Asset Manipulation Gizmo
Halo 2 Sapien Game Window
Halo 2 Sapien Menus
Placing Objects
Placing Lights
Spawn Zones
Decorator Brush
World Ruler
Reset Object Z Height
Gravity Lifts
Teleporters
Sound Effects
Kill Trigger Volumes
Adding Extra Vehicles & Turrets
Game Types
Game Types
Assault
Capture The Flag
Juggernaut
King of the Hill
Oddball
Slayer
Territories
Using Halo 2 Guerilla
Sky Boxes
Sky Light Values
Starting Equipment
The Object Palette
Description Text
Location Text
Map Shots
Using Halo 2 Map Editor Launcher
Using Halo 2 Map Editor Launcher
Halo 2 Tool Level Creation
Halo 2 Level Creation
Import Structure
Generate Lightmaps
Import Descriptions
Creating Unicode Strings
Building Cache Files
Halo 2 Tool Texture Creation
Import Bitmaps
General Level Design Information
Design Style Guidelines
Technical Design Rules
Design Suggestions
Player Statistics and Metrics
Equipment List
Weapons
Vehicles
Multiplayer Level Design
Getting Started
Tutorial 1: Creating an Environment in 3ds Max
Tutorial 2: Exporting an Environment from 3ds Max
Tutorial 3: Importing an Environment to Tag Format
Tutorial 4: Placing Spawn Points Using Halo 2Sapien
Tutorial 5: Creating and Editing Environment Tags Using Halo 2 Guerilla
Tutorial 6: Synching Tags and Launching into the Game Environment
Portals
Additional Resources
Links
Console Command List
File Specifications
.ass File Specification
Credits
Appendix
Sample .ass file

Technical Design Rules and Tips for Multiplayer Levels

Previous Topic  Next Topic 

·        Halo 2 levels must support all seven multiplayer game types (Capture the Flag, Slayer (Deathmatch), King of the Hill, Oddball, Juggernaut, Assault, and Territories) to function properly. Missing netgame flags for necessary elements like objectives, player spawns, and so forth can cause the game or server to crash.

·        Supporting all the game modes in each level ensures consistency when playing multiplayer games.

·        Each level must have a minimum of 16 player spawns per team for each game type. Player spawns can be set up for use in more than one game type.

·        Adequate spawn points keep the game and player spawning behavior working.

·        Minimum distance between player spawns should be 20 units or greater for nonteam game types and 2.5 units or greater for team-based game types. If two or more spawn points are within these minimum distances, it’s possible that a player would not be allowed to spawn until there are no other players within the minimum distance.

·        Halo 2 has robust physics that must be considered for their impact on level design.

·        Avoid thin geometry in level design. Thin geometry is more likely to suffer from collision problems, as players and vehicles can pass through it. Manually created collision models should be simple and robust.