UBM Tech - Game Network

My Shopping Cart

[ 0 ] items in cart

View Cart | Checkout

Game Developer Research

Research Reports

Gamasutra

Contractor Listings

GDC Vault

Individual Subscription

GDC Audio Recordings

App Developers Conference 2013

GDC Next 2013

GDC Europe 2013

	GDC 2013
	GDC Online 2012
	GDC Europe 2012
	GDC 2012
	GDC 2011
	GDC 10
	GDC 09
	GDC Austin 08
	GDC Mobile 08
	GDC 08
	GDC Austin 07
	GDC Mobile 07
	GDC 07
	GDC 06
	GDC 05
	GDC 04
	GDC 03
	GDC 01
	GDC 2000 & Before

Newest Item(s)

Why Now Is the Best Time Ever to Be a Game Developer

Ingress: Design Principles Behind Google's Massively Multiplayer Geo Game

Playing with 'Game'

Gathering Your Party with Project Eternity (GDC Next 10)

D4: Dawn of the Dreaming Director's Drama (GDC Next 10)

Using Plot Devices to Create Gameplay in Storyteller (GDC Next 10)

How I Learned to Stop Worrying and Love Making CounterSpy (GDC Next 10)

Luck and Skill in Games

Minimalist Game Design for Mobile Devices

Broken Age: Rethinking a Classic Genre for the Modern Era (GDC Next 10)

Storefront > GDC Vault Store - Audio Recordings > GDC 2010

View larger image

QTY:

Design in Detail: Changing the Time Between Shots for the Sniper Rifle from 0.5 to 0.7 Seconds for Halo 3
Price	$3.95
Adjustment
Type
Stock	Unlimited
Status
Weight	0 lb, 0 oz
SKU	GDC10-10438
Statistics

Description

Design in Detail: Changing the Time Between Shots for the Sniper Rifle from 0.5 to 0.7 Seconds for Halo 3
Speaker: Jaime Griesemer (Gameplay Designer, Bungie Studios)
Date/Time: Thursday (March 11, 2010) 1:30pm — 2:30pm
Location (room): Room 130, North Hall
Track: Game Design
Format: 60-minute Lecture
Experience Level: All

Session Description
Halo's multiplayer is balanced across over 1000 objects, more than 40 of which are unique weapons including the Sniper Rifle, which has over 200 functional fields including one that determines the minimum time between shots. In Halo 3, that time changed from 0.5 seconds to 0.7 seconds, changing less than 0.00001th of the overall game data, an immeasurably tiny balance tweak that should not have been noticeable, let alone significant.

This session will address this design decision in exhaustive detail. Why 0.7 seconds? Why that particular field? What processes and design principles lead to that change? How was it proposed, tested, and evaluated? What were its effects on the game's balance? How were those effects evaluated to the effects of the infinite number of other changes that could have been made? What were the external considerations, such as community reaction or target demographics, that influenced it? And what can be learned from that change to improve our ability to make changes in the future?

Please leave this field blank.