- Video game development
Part of a series on: Video game industry
Game development is the software development process by which a video game is developed. Development is undertaken by a game developer, which may range from a single person to a large business. Mainstream games are normally funded by a publisher and take several years to develop. Indie games can take less time and can be produced cheaply by individuals and small developers. The indie game industry has seen a rise in recent years with the growth of new online distribution systems and the mobile game market.
The first video games were developed in 1960s, but required mainframe computers and were not available to general public. Commercial game development began in 1970s with the advent of first generation video game consoles and home computers. Due to low costs and low capabilities of computers, a lone programmer could develop a full game. However, approaching the 21st century, ever-increasing computer processing power and heightened consumer expectations made it impossible for a single developer to produce a mainstream game. The average price of game production slowly rose from US$1M–4M in 2000 to over 5M in 2006 to over 20M in 2010.
Mainstream games are generally developed in phases. First, in pre-production, pitches, prototypes, and game design documents are written. If the idea is approved and the developer receives funding, a full-scale development begins. This usually involves a 20–100 man team of various responsibilities, such as designers, artists, programmers, testers, etc. The games go through development, alpha, and beta stages until finally being released. Modern games are advertised, marketed, and showcased at trade show demos. Even so, many games do not turn a profit.
- 1 Overview
- 2 History
- 3 Roles
- 4 Development process
- 4.1 Pre-production
- 4.2 Production
- 4.3 Milestones
- 4.4 Post-production
- 5 Outsourcing
- 6 Marketing
- 7 Indie development
- 8 Game industry
- 9 See also
- 10 Notes
- 11 References
- 12 External links
Game development is the software development process by which a video game is produced. Games are developed as a creative outlet and to generate profit. Development is normally funded by a publisher. Well-made games bring profit more readily. However, it is important to estimate a game's financial requirements, such as development costs of individual features. Often game projects developed with "heart and soul" turn no profit. Failing to provide clear implications of game's expectations may result in exceeding allocated budget. In fact, the majority of commercial games do not produce profit.[r 1] Developers such as BioWare, Blizzard Entertainment, and id Software are renowned for releasing quality games on completion, rather than being constrained by financial limitations. However, most developers cannot afford changing development schedule and require estimating their capabilities with available resources before production.
The game industry requires innovations, as publishers cannot profit from constant release of sequels and imitations. Every year new independent development companies open and some manage to develop hit titles. Similarly, many developers close down because they cannot find a publishing contract or their production is not profitable. It is difficult to start a new company due to high initial investment required. Nevertheless, growth of casual and mobile game market has allowed developers with smaller teams to enter the market. Once the companies become financially stable, they may expand to develop larger games. Most developers start small and gradually expand their business. A developer receiving profit from a successful title may store up a capital to expand and re-factor their company, as well as tolerate more failed deadlines.
In the early era of home computers and video game consoles in the early 1980s, a single programmer could handle almost all the tasks of developing a game — programming, graphical design, sound effects, etc.[r 3] It could take as little as six weeks to develop a game. However, the high user expectations and requirements of modern commercial games far exceed the capabilities of a single developer and require the splitting of responsibilities. A team of over a hundred people can be employed full-time for a single project.[r 3]
Game development, production, or design is a process that starts from an idea or concept. Often the idea is based on a modification of an existing game concept. The game idea may fall within one or several genres. Designers often experiment with different combinations of genres. Game designer usually produces initial game proposal document, that contains the concept, gameplay, feature list, setting and story, target audience, requirements and schedule, staff and budget estimates. Different companies have different formal procedures and philosophies regarding game design and development. There is no standardized development method; however commonalities exist.
Game development is undertaken by a game developer—ranging from an individual to a large company. There can be independent or publisher-owned studios. Independent developers rely on financial support from a game publishers. They usually have to develop a game from concept to prototype without external funding. The formal game proposal is then submitted to publishers, who may finance the game development from several months to years. The publisher would retain exclusive rights to distribute and market the game and would often own the intellectual property for the game franchise. Publisher's company may also own the developer's company, or it may have internal development studio(s). Generally the publisher is the one who owns the game's intellectual property.[r 1]
All but the smallest developer companies work on several titles at once. This is necessary because of the time taken between shipping a game and receiving royalty payments, which may be between 6 to 18 months. Small companies may structure contracts, ask for advances on royalties, use shareware distribution, employ part-time workers and use other methods to meet payroll demands.
Console manufacturers, such as Microsoft, Nintendo, or Sony, have a standard set of technical requirements that a game must confirm to in order to be approved. Additionally, the game concept must be approved by the manufacturer, who may refuse to approve certain titles.
Most modern games take from one to three years to complete. The length of development is influenced by a number of factors, such as genre, scale, development platform and amount of assets.
Some games can take much longer than the average time frame to complete. An infamous example is 3D Realms' Duke Nukem Forever, announced to be in production in April 1997 and released fourteen years later in June 2011.[r 4] Planning for Maxis' game Spore began in late 1999 and was released nine years later in September 2008. The game Prey was briefly profiled in a 1997 issue of PC Gamer, but was not released until 2006, and only then in highly altered form.
The game revenue from retails is divided among the parties along the distribution chain, such as — developer, publisher, retail, manufacturer and console royalty. Many developers fail to profit from this and go bankrupt. Some developers seek alternative economic models through Internet marketing and distribution channels to improve returns.
The history of game making begins with the development of the first video games, although which video game is the first depends on the definition of video game. The first games created had little entertainment value, and their development focus was separate from user experience—in fact, these games required mainframe computers to play them. OXO, written by Alexander S. Douglas in 1952, was the first computer game to use a digital display. In 1958, a game called Tennis for Two, which displayed its output on an oscilloscope, was made by Willy Higinbotham, a physicist working at the Brookhaven National Laboratory.[r 6] In 1961, a mainframe computer game called Spacewar! was developed by a group of Massachusetts Institute of Technology students led by Steve Russell.
True commercial design and development of games began when first generation consoles were marketed in 1970s. In 1972, the first home console system was released called Magnavox Odyssey, developed by Ralph H. Baer.[r 7] Programmers worked within the big companies to produce games for these devices. The industry did not see huge innovation in game design and large number of consoles had very similar games. At the same time home computers appeared on the market and individual programmers and hobbyist could develop games. This allowed hardware manufacturer and software manufacturers to act separately. A very large amount of games could be produced by single individuals, as games were easy to make because graphical and memory limitation did not allow for much content. Larger companies developed, who focused selected teams to work on a title. Similarly, console manufacturers started to produce consoles that were able to play independently developed games.
With the ever-increasing processing and graphical capabilities of computers and console products, along with an increase in user expectations, game design moved beyond the scope of a single developer to produce a marketable game in a reasonable time. This sparked the beginning of team-based development.
In broad terms, in 1980s pre-production involved sketches and test routines of the only developer. In 1990s pre-production consisted of by large game art previews. In early 2000s pre-production usually produced a playable demo.
In 2001 over 3000 games were released for PC; and from about 100 games turning profit only about 50 made significant profit.
In 2006 the profit from a console game sold at retail was divided among parties of distribution chain as follows: developer (13%), publisher (32%), retail (32%), manufacturer (5%), console royalty (18%). In 2008 a developer would retain around 17% of retail price and around 85% if sold online.[r 1]
The game industry has constantly increased and expanded. The industry revenue has increased at least fivefold since the 1990s. In 2007 the software portion of video game revenue was $9.5 billion, exceeding that of movies industry.
In 2009 games market annual value is estimated between $7–30 billion, depending on which sales figures are included. This is on par with films box office market. A publisher would typically fund an independent developer for $500k-$5M for a development of a title.
In the past several years, many developers opened and many closed down. Each year a number of developers are acquired by larger companies or merge with existing companies. For example, in 2007 Blizzard Entertainment's parent company, Vivendi Games merged with Activision. In 2008 Electronic Arts nearly acquired Take-Two Interactive. In 2009 Midway Games was acquired by Time-Warner and Eidos merged with Square Enix.
Development is overseen by internal and external producers. The producer working for the developer is known as the internal producer and manages the development team, schedules, reports progress, hires and assigns staff, and so on. The producer working for the publisher is known as the external producer and oversees developer progress and budget. Producer's responsibilities include PR, contract negotiation, liaising between the staff and stakeholders, schedule and budget maintenance, quality assurance, beta test management, and localization. This role may also be referred to as project manager, project lead, or director.
Developer and publisher are often separate companies.
Developers can range in size from small groups making casual games to housing hundreds of employees and producing several large titles.  Companies divide their subtasks of game's development. Individual job titles may vary; however, roles are the same within the industry. The development team consists of several members. Some members of the team may handle more than one role; similarly more than one task may be handled by the same member. Team size can vary from 20 to 100 or more members, depending on the game's scope. The most represented are artists, followed by programmers, then designers, and finally, audio specialists, with two to three producers in management. These positions are employed full-time. Other positions, such as testers, may be employed only part-time.
A development team includes these roles or disciplines:
A game designer is a person who designs gameplay, conceiving and designing the rules and structure of a game. Development teams usually have a lead designer who coordinates the work of other designers. He is the main visionary of the game. One of the roles of a designer is being a writer, often employed part-time to conceive game's narrative, dialogue, commentary, cutscene narrative, journals, video game packaging content, hint system, etc. In larger projects, there are often separate designer for various parts of the game, such as, game mechanics, user interface, characters, dialogue, etc.
A game artist is a visual artist who creates video game art. The art production is usually overseen by an art director or art lead, making sure his vision is followed. The art director manages the art team, scheduling and coordinating within the development team.
The artist's job may be 2D oriented or 3D oriented. 2D artists may produce concept art, sprites, textures, environmental backdrops or terrain images, and user interface. 3D artists may produce models or meshes, animation, 3D environment, and cinematics. Artists sometimes occupy both roles.
A game programmer is a software engineer who primarily develops video games or related software (such as game development tools). The game's codebase development is handled by programmers. There are usually one to several lead programmers, who implement the game's starting codebase and overview future development and programmer allocation on individual modules.
Individual programming disciplines roles include:
- Physics – the programming of the game engine, including simulating physics, collision, object movement, etc.;
- AI – producing computer agents using game AI techniques, such as scripting, planning, rule-based decisions, etc.
- Graphics – the managing of graphical content utilization and memory considerations; the production of graphics engine, integration of models, textures to work along the physics engine.
- Sound – integration of music, speech, effect sounds into the proper locations and times.
- Gameplay – implementation of various games rules and features (sometimes called a generalist);
- Scripting – development and maintenance of high-level command system for various in-game tasks, such as AI, level editor triggers, etc.
- UI – production of user interface elements, like option menus, HUDs, help and feedback systems, etc.
- Input processing – processing and compatibility correlation of various input devices, such as keyboard, mouse, gamepad, etc.
- Network communications – the managing of data inputs and outputs for local and internet gameplay.
- Game tools – the production of tools to accompany the development of the game, especially for designers and scripters.
A level designer is a person who creates levels, challenges or missions for computer and/or video games using a specific set of programs. These programs may be commonly available commercial 3D or 2D design programs, or specially designed and tailored level editors made for a specific game.
Level designers work with both incomplete and complete versions of the game. Game programmers usually produce level editors and design tools for the designers to use. This eliminates the need for designers to access or modify game code. Level editors may involve custom high-level scripting languages for interactive environments or AIs. As opposed to the level editing tools sometimes available to the community, level designers often work with placeholders and prototypes aiming for consistency and clear layout before required artwork is completed.
Sound engineers are technical professionals responsible for sound effects and sound positioning. They sometimes oversee voice acting and other sound asset creation. Composers who create a game's musical score also comprise a game's sound team, though often this work is outsourced.
The quality assurance is carried out by game testers. A game tester analyzes video games to document software defects as part of a quality control. Testing is a highly technical field requiring computing expertise, and analytic competence.
The testers ensure that the game falls within the proposed design: it both works and is entertaining.This involves testing of all features, compatibility, localization, etc. Although, necessary throughout the whole development process, testing is expensive and is often actively utilized only towards the completion of the project.
Game development is a software development process, as a video game is software with art, audio, and gameplay. Formal software development methods are often overlooked. Games with poor development methodology are likely to run over budget and time estimates, as well as contain a large number of bugs. Planning is important for individual and group projects alike.
One method employed for game development is agile development. It is based on iterative prototyping, a subset of software prototyping. Agile development depends on feedback and refinement of game's iterations with gradually increasing feature set. This method is effective because most projects do not start with a clear requirement outline. A popular method of agile software development is Scrum.
Another successful method is Personal Software Process (PSP) requiring additional training for staff to increase awareness of project's planning. This method is more expensive and requires commitment of team members. PSP can be extended to Team Software Process, where the whole team is self-directing.
Game development usually involves an overlap of these methods. For example, asset creation may be done via waterfall model, because requirements and specification are clear,  but gameplay design might be done using iterative prototyping.
Pre-production or design phase is a planning phase of the project focused on idea and concept development and production of initial design documents. The goal of concept development is to produce clear and easy to understand documentation, which describes all the tasks, schedules and estimates for the development team. The suite of documents produced in this phase is called production plan. This phase is usually not funded by a publisher, however good publishers may require developers to produce plans during pre-production.
The concept documentation can be separated into three stages or documents—high concept, pitch and concept; however, there is no industry standard naming convention, for example, both Bethke (2003) and Bates (2004) refer to pitch document as "game proposal", yet Moore, Novak (2010) refers to concept document as "game proposal".
Publishers have started to expect broader game proposals even featuring playable prototypes.
A pitch, concept document,, proposal document, or game proposal is a short summary document intended to present the game's selling points and detail why the game would be profitable to develop.
Verbal pitches may be made to management within the developer company, and then presented to publishers. A written document may need to be shown to publishers before funding is approved. A game proposal may undergo one to several green-light meetings with publisher executives who determine if the game is to be developed. The presentation of the project is often given by the game designers. Demos may be created for the pitch; however may be unnecessary for established developers with good track records.
If the developer acts as its own publisher, or both companies are subsidiaries of a single company, then only the upper management needs to give approval.
Concept document,, game proposal, or game plan is a more detailed document than the pitch document. This includes all the information produced about the game. This includes the high concept, game's genre, gameplay description, features, setting, story, target audience, hardware platforms, estimated schedule, marketing analysis, team requirements, and risk analysis.
Before an approved design is completed, a skeleton crew of programmers and artists usually begins work. Programmers may develop quick-and-dirty prototypes showcasing one or more features that stakeholders would like to see incorporated in the final product. Artists may develop concept art and asset sketches as a springboard for developing real game assets. Producers may work part-time on the game at this point, scaling up for full time commitment as development progresses. Game producers work during pre-production is related to planning the schedule, budget and estimating tasks with the team. The producer aims to create a solid production plan so that no delays are experienced at the start of the production.
Game design document
Before a full-scale production can begin, the development team produces the first version of a game design document incorporating all or most of the material from the initial pitch. The design document describes the game's concept and major gameplay elements in detail. It may also include preliminary sketches of various aspects of the game. Design document is sometimes accompanied by functional prototypes of some sections of the game. Design document remains a living document throughout the development—often changed weekly or even daily.
Compiling a list of game's needs is called "requirement capture".
Writing prototypes of gameplay ideas and features is an important activity that allows programmers and game designers to experiment with different algorithms and usability scenarios for a game. A great deal of prototyping may take place during pre-production before the design document is complete and may, in fact, help determine what features the design specifies. Prototyping may also take place during active development to test new ideas as the game emerges.
Prototypes are often meant only to act as a proof of concept or to test ideas, by adding, modifying or removing some of the features. Most algorithms and features debuted in a prototype may be ported to the game once they have been completed.
Often prototypes need to be developed quickly with very little time for up-front design. Therefore usually very prolific programmers are called upon to quickly code these testbed tools. RAD tools may be used to aid in the quick development of these programs.
Mainstream production is usually defined as the period of time when the project is fully staffed. Programmers write new source code, artists develop game assets, such as, sprites or 3D models. Sound engineers develop sound effects and composers develop music for the game. Level designers create levels, and writers write dialogue for cutscenes and NPCs.[original research?] Game designers continue to develop the game's design throughout production.
All the while, the game designer implements and modifies the game design to reflect the current vision of the game. Features and levels are often removed or added. The art treatment may evolve and the backstory may change. A new platform may be targeted as well as a new demographic. All these changes need to be documented and dispersed to the rest of the team. Most changes occur as updates to the design document.
From a time standpoint, the game's first level takes the longest to develop. As level designers and artists use the tools for level building, they request features and changes to the in-house tools that allow for quicker and higher quality development. Newly introduced features may cause old levels to become obsolete, so the levels developed early on may be repeatedly developed and discarded. Because of the dynamic environment of game development, the design of early levels may also change over time. It is not uncommon to spend upwards of twelve months on one level of a game developed over the course of three years. Later levels can be developed much more quickly as the feature set is more complete and the game vision is clearer and more stable.
Game audio may be separated into three categories—sound effects, music, and voice-over.
Sound effect production is the production of sounds by either tweaking a sample to a desired effect or replicating it with real objects. Sound effects are important and impact the game's delivery.
Music may be synthesized or performed live.
There are several ways in which music is presented in a game.
- Music may be ambient, especially for slow periods of game, where the music aims to reinforce the aesthetic mood and game setting.
- Music may be triggered by in-game events. For example, in such games as Pac-man or Mario, player picking up power-ups trigerred respective musical scores.
- Action music, such as chase, battle or hunting sequences is fast-paced, hard-changing score.
- Menu music, similar to credits music, creates aural impact while relatively little action is taking place.
A game title with 20 hours of single-player gameplay may feature around 60 minutes of music.
At the end[original research?] of the project quality assurance plays a significant role. Testers start work once anything is playable. This may be one level or subset of the game software that can be used to any reasonable extent. Early on, testing a game occupies a relatively small amount of time. Testers may work on several games at once. As development draws to a close, a single game usually employs many testers full time (and often with overtime). They strive to test new features and regression test existing ones. Testing is vital for modern, complex games as single changes may lead to catastrophic consequences.
At this time features and levels are being finished at the highest rate and there is more new material to be tested than during any other time in the project. Testers need to carry out regression testing to make sure that features that have been in place for months still operate correctly. Regression testing is one of the vital tasks required for effective software development. As new features are added, subtle changes to the codebase can produce unexpected changes in different portions of the game. This task is often overlooked, for several reasons. Sometimes, when a feature is implemented and tested, it is considered "working" for the rest of the project and little attention is given to repeated testing. Also, features that are added late in development are prioritized and existing features often receive insufficient testing time. Proper regression testing is also increasingly expensive as the number of features increases and is often not scheduled correctly.
Despite the dangers of overlooking regression testing, some game developers and publishers fail to test the full feature suite of the game and ship a game with bugs. This can result in customers dissatisfaction and failure to meet sales goals. When this does happen, most developers and publishers quickly release patches that fix the bugs and make the game fully playable again.
Commercial game development projects may be required to meet milestones set by publisher. Milestones mark major events during game development and are used to track game's progress. Such milestones may be, for example, first playable, alpha, or beta game versions. Project milestones depend on the developer schedules.
The first playable is the game version containing representative gameplay and assets, this is the first version with functional major gameplay elements. It is often based on the prototype created in pre-production. Alpha and first playable are sometimes used to refer to a single milestone, however large projects require first playable before feature complete alpha. First playable occurs 12 to 18 months before code release.
Alpha is the stage when key gameplay functionality is implemented, and assets are partially finished. A game in alpha is feature complete, that is, game is playable and contains all the major features. These features may be further revised based on testing and feedback. Additional small, new features may be added, similarly planned, but unimplemented features may be dropped. Programmers focus mainly on finishing the codebase, rather than implementing additions. Alpha occurs eight to ten months before code release.
Code freeze is the stage when new code is no longer added to the game and only bugs are being corrected. Code freeze occurs three to four months before code release.
Beta is feature and asset complete version of the game, when only bugs are being fixed. This version contains no bugs that prevent the game from being shippable. No changes are made to the game features, assets, or code. Beta occurs two to three months before code release.
Code release is the stage when all bugs are fixed and game is ready to be shipped or submitted for console manufacturer review. This version is tested against QA test plan. First code release candidate is usually ready three to four weeks before code release.
Gold master is the final game's build that is used as a master for production of the game.
Overtime is expected in the games industry. Particularly, crunch time or crunch mode is unpaid overtime requested by many companies to meet project deadlines and milestones that negatively affects game developers. A team missing a deadline risks the danger of having the project cancelled or employees being laid off. Although many companies are reducing the amount of crunch time, it is still prominent in smaller companies.
Many companies offer time-off, called comp time or extra paid time-off after product ships to compensate for crunch time's negative effects. Some companies offer bonuses and financial rewards for successful milestone reach. Sometimes on-site crunch meals are offered and delivered to the team during crunch time.
After the game goes gold and ships, some developers will give team members comp time (perhaps up to a week or two) to compensate for the overtime put in to complete the game, though this compensation is not standard.
Once a game ships, the maintenance phase for the video game begins.
Games developed for video game consoles have had almost no maintenance period in the past. The shipped game would forever house as many bugs and features as when released. This was the norm for consoles since all consoles had identical or nearly identical hardware. In this case, maintenance would only occur in the case of a port, sequel, or enhanced remake that reuses a large portion of the engine and assets.
In recent times popularity of online console games has grown, and online capable video game consoles and online services such as Xbox Live for the Xbox have developed. Developers can maintain their software through downloadable patches. These changes would not have been possible in the past without the widespread availability of the Internet.
The PC development is different. Game developers try to account for majority of configurations and hardware. However, the number of possible configurations of hardware and software inevitably leads to discovery of game-breaking circumstances that the programmers and testers didn't account for.
Programmers wait for a period to get as many bug reports as possible. Once the developer thinks they've obtained enough feedback, the programmers start working on a patch. The patch may take weeks or months to develop, but it's intended to fix most bugs and problems with the game. Occasionally a patch may include extra features or content or may even alter gameplay.
In the case of a massively multiplayer online game (MMOG), such as a MMORPG or MMORTS, the shipment of the game is the starting phase of maintenance. Such online games are in continuous maintenance as the gameworld is continuously changed and iterated and new features are added. The maintenance staff for a popular MMOG can number in the dozens, sometimes including members of the original programming team.
Several development disciplines, such as, for example, audio, dialogue, or motion capture, occur for relatively short periods of time. Efficient employment of these roles requires either large development house with multiple simultaneous title production or it requires outsourcing from third-party vendors. Employing personnel for these tasks full-time is expensive. Majority of developers outsource a portion of the work. Outsourcing plans are conceived during pre-production stage; where the time and finances required for outsourced work are estimated.
- Programming is not usually outsourced. Some modular tools, such as, video compressor or map editor, may be outsourced.
- The music cost ranges based on length of composition, method of performance (live or synthesized), and composer experience. In 2003 a minute of high quality synthesized music cost between US$600-1.5k. A title with 20 hours of gameplay and 60 minutes of music may have cost $50k-60k for musical score.
- Voice acting is well suited for outsourcing, it requires a set of specialized skills. Only large publishers employ in-house voice actors.
- Sound effects can also be outsourced.
The game production has similar distribution methods to those of music and film industries.
The publisher's marketing team targets the game for a specific market and then advertises it. The team advises the developer on target demographics and market trends, as well as suggests specific features. The game is then advertised and the game's high concept is incorporated into the promotional material, ranging from magazine ads to TV spots. Communication between developer and marketing is important.
The length and purpose a game demo depends on the purpose of the demo and target audience. A game's demo may range between a few seconds (such as clips or screenshots) to hours of gameplay. The demo is usually intended for journalists, buyers, trade shows, general public, or internal employees (who, for example, may need to familiarize with the game to promote it). Demos are produced with public relations, marketing and sales in mind, maximizing the presentation effectiveness.
Trade show demo
The major annual trade shows are, for example, Electronic Entertainment Expo (E3) or Penny Arcade Expo (PAX). E3 is the largest show in North America. E3 is hosted primarily for marketing and business deals. New games and platforms are announced at E3 and it received broad press coverage. Thousands of products are on display and press demonstration schedules are kept. In recent years E3 has become a more closed-door event and many advertisers have withdrawn reducing E3 budget. PAX, created by authors of Penny Arcade blog and web-comic, is a mature and playful event with a player-centred philosophy.
Independent games or indie games are produced by individuals and small teams with no large-scale developer or publisher affiliations. Indie developers generally rely on Internet distribution schemes. Many hobbyist indie developers create mods of existing games. Indie developers are credited for creative game ideas (for example, Darwinia, Weird Worlds, World of Goo). Current economic viability of indie development is questionable, however in recent years internet delivery platforms, such as, Xbox Live Arcade and Steam have improved indie game success. In fact, some indie games have become very successful, such as Braid,[r 10] World of Goo,[r 11] or Minecraft.[r 12]
The video game industry (formally referred to as interactive entertainment) is the economic sector involved with the development, marketing and sale of video games. The industry sports several unique approaches.
In the United States, in the early history of video game development, the prominent locale for game development was the corridor from San Francisco to Silicon Valley in California. Most new developers in the US open near such "hot beds".
At present, many large publishers still operate there, such as: Activision Blizzard, Capcom Entertainment, Disney Interactive, Eidos Interactive, Electronic Arts, Foundation 9, LucasArts Entertainment, Namco Bandai Games, Sega of America, Sony Computer Entertainment America, THQ. However, due to the nature of game development, many publishers are present in other regions, such as Big Fish Games (Washington), GarageGames (Oregon), Majesco (New Jersey), Microsoft Corporation (Washington), Nintendo of America (Washington), Take-Two Interactive (New York), SouthPeak Interactive (Virginia).
Notable developers in California are: Blizzard Entertainment, Crave Entertainment, Cryptic Studios, Crystal Dynamics, Double Helix Games, Insomniac Games, Koei Corporation North America, Naughty Dog, Neversoft Entertainment, Obsidian Entertainment, Rockstar San Diego, Tecmo. The Washington area houses the following developers: Amaze Entertainment, ArenaNet, Bungie Software, Gas Powered Games, Monolith Productions, PopCap Games, Sucker Punch Productions, Snowblind Studios, Ubisoft Massive/Sierra Entertainment, Valve Corporation. Other developers in the states include: Bethesda Softworks (Maryland), Big Huge Games (Maryland), BreakAway Games (Maryland), Epic Games (Carolina), Firaxis Games (Maryland), id Software (Texas), 2K Boston (Massachusetts), Petroglyph (Nevada), Raven Software (Wisconsin), Red Storm Entertainment (North Carolina), Vicarious Visions (New York), and Irrational Games (Massachusetts).
Many universities and design schools are offering classes specifically focused on game development. Some have built strategic alliances with major game development companies. These alliances ensure that students have access to the latest technologies and are provided the opportunity to find jobs within the gaming industry once qualified. Many innovative ideas are presented at conferences, such as Independent Games Festival (IGF) or Game Developers Conference (GDC).
Indie game development may motivate students who produce a game for their final projects or thesis and may open their own game company.
Video game industry employment is fairly volatile, similar to other artistic industries including television, music, etc. Scores of game development studios crop up, work on one game, and then quickly go under. This may be one reason why game developers tend to congregate geographically; if their current studio goes under, they can flock to an adjacent one or start another from the ground up.
In an industry where only the top 5% of products make a profit,[r 13] it's easy to understand this fluctuation. Numerous games may start development and are cancelled, or perhaps even completed but never published. Experienced game developers may work for years and yet never ship a title: such is the nature of the business. This volatility is likely inherent to the artistic nature of games.
- Independent video game development
- Software development
- Software development process
- Agile software development and Scrum, development methodologies
- List of video gaming topics
- Video game controversy
- Open source video games
- ^ a b Bethke 2003, p. 4.
- ^ Bethke 2003, p. 7.
- ^ Bethke 2003, p. 14.
- ^ Bates 2004, p. 239.
- ^ Bethke 2003, p. 12.
- ^ a b Bethke 2003, p. 17.
- ^ Bethke 2003, pp. 18–19.
- ^ a b Bethke 2003, p. 18.
- ^ a b c Bethke 2003, p. 3.
- ^ Bethke 2003, pp. 17–18.
- ^ a b Moore & Novak 2010, p. 19.
- ^ a b c Moore & Novak 2010, p. 17.
- ^ a b c Moore & Novak 2010, p. 37.
- ^ Moore & Novak 2010, p. 18.
- ^ Adams & Rollings 2006, p. 13.
- ^ a b c Chandler 2009, p. xxi.
- ^ a b c Moore & Novak 2010, p. 5.
- ^ a b Bates 2004, p. 3.
- ^ Adams & Rollings 2006, pp. 29–30.
- ^ Bethke 2003, p. 75.
- ^ Chandler 2009, p. 3.
- ^ Adams & Rollings 2006, pp. 31–33.
- ^ a b Bates 2004, p. 6.
- ^ Oxland 2004, p. 25.
- ^ Bates 2004, pp. 14–16.
- ^ a b c d e Bates 2004, p. 151.
- ^ a b McGuire & Jenkins 2009, p. 23.
- ^ Chandler 2009, p. xxi-xxii.
- ^ a b c d e f McGuire & Jenkins 2009, p. 25.
- ^ Chandler 2009, p. 82.
- ^ Chandler 2009, p. 87.
- ^ a b c McGuire & Jenkins 2009, p. 26.
- ^ Chandler 2009, p. 90.
- ^ McGuire & Jenkins 2009, pp. 26–27.
- ^ Moore & Novak 2010, p. 7.
- ^ a b Moore & Novak 2010, p. 6.
- ^ Moore & Novak 2010, p. 9.
- ^ Moore & Novak 2010, p. 12.
- ^ Moore & Novak 2010, p. 13.
- ^ a b Bethke 2003, p. 26.
- ^ a b c Bethke 2003, p. 15.
- ^ Bethke 2003, pp. 15–16.
- ^ Bethke 2003, p. 30.
- ^ Moore & Novak 2010, p. 15.
- ^ a b c McGuire & Jenkins 2009, p. 24.
- ^ Moore & Novak 2010, p. 16.
- ^ Bates 2004, p. 154.
- ^ a b c d Moore & Novak 2010, p. 71.
- ^ Bates 2004, pp. 156–158.
- ^ Bates 2004, pp. 154–156.
- ^ a b Bates 2004, p. 153.
- ^ Moore & Novak 2010, p. 25.
- ^ Salen & Zimmerman 2003.
- ^ Oxland 2004, p. 292.
- ^ Moore & Novak 2010, p. 74.
- ^ Oxland 2004, pp. 292–296.
- ^ Bates 2004, p. 163.
- ^ Brathwaite & Schreiber 2009, p. 171.
- ^ Moore & Novak 2010, p. 94.
- ^ a b Bates 2004, p. 171.
- ^ Moore & Novak 2010, p. 85.
- ^ a b Moore & Novak 2010, p. 86.
- ^ Bates 2004, p. 173.
- ^ a b Moore & Novak 2010, p. 87.
- ^ Moore & Novak 2010, p. 88.
- ^ a b c Bates 2004, p. 176.
- ^ a b Moore & Novak 2010, p. 89.
- ^ Bates 2004, p. 175.
- ^ a b Moore & Novak 2010, p. 90.
- ^ a b Bates 2004, p. 168.
- ^ Moore & Novak 2010, p. 78.
- ^ Bates 2004, p. 165.
- ^ Bates 2004, p. 162.
- ^ Moore & Novak 2010, p. 76.
- ^ Bates 2004, pp. 185, 188, 191.
- ^ Moore & Novak 2010, p. 91.
- ^ Moore & Novak 2010, p. 95.
- ^ Bates 2004, p. 177.
- ^ a b Bates 2004, p. 225.
- ^ a b Bates 2004, pp. 218–219.
- ^ Bates 2004, pp. 226–227.
- ^ Chandler 2009, p. 47.
- ^ Chandler 2009, p. 41.
- ^ Chandler 2009, pp. 41, 43–44.
- ^ Chandler 2009, p. 44.
- ^ a b Bates 2004, p. 227.
- ^ a b c d e f g h i j Moore & Novak 2010, p. 70.
- ^ a b c d Bates 2004, p. 203.
- ^ a b c d e f g h i Bates 2004, p. 204.
- ^ Adams & Rollings 2006, p. 29.
- ^ Oxland 2004, p. 251.
- ^ Chandler 2009, pp. 5–9.
- ^ a b Chandler 2009, p. 6.
- ^ a b c d e Bethke 2003, p. 102.
- ^ Bethke 2003, pp. 101–102.
- ^ Bates 2004, pp. 203–207.
- ^ Bethke 2003, p. 103.
- ^ Bates 2004, p. 274.
- ^ Bethke 2003, p. 27.
- ^ a b Chandler 2009, p. 8.
- ^ Bates 2004, pp. 204–205.
- ^ Bates 2004, p. 276.
- ^ Oxland 2004, pp. 240, 274.
- ^ Oxland 2004, p. 241.
- ^ Brathwaite & Schreiber 2009, p. 189.
- ^ Bates 2004, p. 226.
- ^ Chandler 2009, p. 9.
- ^ Bates 2004, p. xxi.
- ^ Brathwaite & Schreiber 2009, p. 2.
- ^ Adams & Rollings 2006, pp. 20, 22–23, 24–25.
- ^ a b c Bethke 2003, p. 49.
- ^ a b Bethke 2003, p. 363.
- ^ Bethke 2003, p. 50.
- ^ a b c Bethke 2003, p. 344.
- ^ a b c d Bethke 2003, p. 345.
- ^ a b Bethke 2003, p. 353.
- ^ a b c d Chandler 2009, p. 244.
- ^ a b c Bethke 2003, p. 293.
- ^ a b Chandler 2009, p. 244–245.
- ^ a b c d Bethke 2003, p. 294.
- ^ a b c d e f g h i j Chandler 2009, p. 245.
- ^ a b c Bethke 2003, p. 192.
- ^ Bethke 2003, p. 295.
- ^ a b Moore & Novak 2010, p. 241.
- ^ a b McShaffry 2009, p. 17.
- ^ Moore & Novak 2010, p. 20, 212.
- ^ a b Moore & Novak 2010, p. 48.
- ^ Moore & Novak 2010, p. 20.
- ^ Moore & Novak 2010, p. 48, 241.
- ^ Moore & Novak 2010, p. 212.
- ^ a b Moore & Novak 2010, p. 97.
- ^ Bethke 2003, p. 183.
- ^ Bethke 2003, pp. 183–184.
- ^ Bethke 2003, p. 184.
- ^ Bethke 2003, p. 185.
- ^ Bethke 2003, p. 343.
- ^ a b c Bates 2004, p. 241.
- ^ a b Bates 2004, p. 242.
- ^ Bates 2004, p. 246.
- ^ McGuire & Jenkins 2009, pp. 24–25.
- ^ Bethke 2003, p. 57.
- ^ a b Bethke 2003, p. 58.
- ^ a b c d McGuire & Jenkins 2009, p. 27.
- ^ Moore & Novak 2010, p. 272.
- ^ Bates 2004, p. 252.
- ^ Moore & Novak 2010, pp. 50–51.
- ^ Moore & Novak 2010, p. 51.
- ^ Moore & Novak 2010, pp. 52–53.
- ^ Oxland 2004, p. 309.
- ^ Moore & Novak 2010, p. 298.
- ^ McShaffry 2009, pp. 19–20.
- ^ a b c Irwin, Mary Jane (November 20, 2008). "Indie Game Developers Rise Up". Forbes. http://www.forbes.com/2008/11/20/games-indie-developers-tech-ebiz-cx_mji_1120indiegames.html. Retrieved January 10, 2011.
- ^ Crossley, Rob (January 11, 2010). "Study: Average dev costs as high as $28m". http://www.develop-online.net/news/33625/Study-Average-dev-cost-as-high-as-28m. Retrieved October 17, 2010.
- ^ a b Reimer, Jeremy (November 7, 2005). "Cross-platform game development and the next generation of consoles — Introduction". http://arstechnica.com/old/content/2005/11/crossplatform.ars. Retrieved October 17, 2010.
- ^ http://www.pcgamer.com/2011/03/24/duke-nukem-forever-release-date-disparity-demystified/
- ^ "XGS PIC 16-Bit Development System". Microchip Technology. http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en542085. Retrieved June 20, 2010.
- ^ John Anderson. "Who Really Invented The Video Game?". Atari Magazines. http://www.atarimagazines.com/cva/v1n1/inventedgames.php. Retrieved November 27, 2006.
- ^ Wolverton, Mark. "The Father of Video Games". American Heritage. http://www.americanheritage.com/articles/magazine/it/2009/3/2009_3_26.shtml. Retrieved March 31, 2010.
- ^ "Cost of making games set to soar". BBC News. November 17, 2005. http://news.bbc.co.uk/2/hi/technology/4442346.stm. Retrieved April 9, 2010.
- ^ "Quality of Life White Paper". International Game Developers Association. Archived from the original on May 19, 2008. http://web.archive.org/web/20080519052523/http://www.igda.org/qol/whitepaper.php. Retrieved October 23, 2004.
- ^ Chaplin, Heather (August 27, 2008). "Xbox's 'Braid' A Surprise Hit, For Surprising Reasons". NPR. http://www.npr.org/templates/story/story.php?storyId=94025221. Retrieved February 4, 2011.
- ^ Mysore, Sahana (January 2, 2009). "How the World of Goo became one of the indie video game hits of 2008". Venturebeat. http://venturebeat.com/2009/01/02/the-world-of-goo-became-one-of-the-indie-hits-of-2008/. Retrieved February 4, 2011.
- ^ Plunkett, Luke (January 4, 2011). "Why Minecraft Is So Damn Popular". Kotaku. http://kotaku.com/5724989/why-minecraft-is-so-damn-popular. Retrieved February 4, 2011.
- ^ Gillin, Paul. "Profile: Getting Into Gear". BizTech. http://www.biztechmagazine.com/article.asp?item_id=132. Retrieved March 23, 2008.
- Adams, Ernest; Rollings, Andrew (2003). Andrew Rollings and Ernest Adams on game design. New Riders Publishing. ISBN 1-59273-001-9.
- Bates, Bob (2004). Game Design (2nd ed.). Thomson Course Technology. ISBN 1-59200-493-8.
- Bethke, Erik (2003). Game development and production. Texas: Wordware Publishing, Inc.. ISBN 1-55622-951-8.
- Brathwaite, Brenda; Schreiber, Ian (2009). Challenges for Game Designers. Charles River Media. ISBN 1-58450-580-X.
- Chandler, Heather Maxwell (2009). The Game Production Handbook (2nd ed.). Hingham, Massachusetts: Infinity Science Press. ISBN 978-1-934015-40-7.
- McGuire, Morgan; Jenkins, Odest Chadwicke (2009). Creating Games: Mechanics, Content, and Technology. Wellesley, Massachusetts: A K Peters. ISBN 978-1-56881-305-9.
- McShaffry, Mike (2009). Game Coding Complete. Hingham, Massachusetts: Charles River Media. ISBN 978-1-58450-680-5.
- Moore, Michael E.; Novak, Jeannie (2010). Game Industry Career Guide. Delmar: Cengage Learning. ISBN 978-1-42837-647-2.
- Oxland, Kevin (2004). Gameplay and design. Addison Wesley. ISBN 0-32120-467-0.
- Salen, Katie; Zimmerman, Eric (2005). The Game Design Reader: A Rules of Play Anthology. The MIT Press. ISBN 0-262-19536-4.
- Salen, Katie; Zimmerman, Eric (2003). Rules of Play: Game Design Fundamentals. MIT Press. ISBN 0-262-24045-9.
- GameDev.net, a resource for game development
- DevMaster.net, game development site
- Gamasutra.com, articles on game development
- International Game Developers Association (IGDA)
Wikimedia Foundation. 2010.