Micromanagement (gameplay)

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

In gaming, micromanagement are minor, detailed gameplay elements that must be manually addressed by the player. It appears in a wide range of games including strategy video games, construction and management simulations and pet-raising simulations. Micromanagement has been perceived in different ways by game designers and players for many years: some perceive it as a useful addition to games that adds options and technique to the gameplay, something that is necessary if the game is to support top-level competitions; some enjoy opportunities to use tactical skill in strategic games; others regard it as an unwelcomed distraction from higher levels of strategic thinking and dislike having to do a lot of detailed work. Some developers attempt to minimize micromanagement in a game's interface for this reason.[citation needed]

Micromanagement in strategy games

File:StarcraftPsiStorm01.png
An example of an advantage gained through micromanagement in the real-time strategy game StarCraft. The Protoss High Templar uses a lightning-like Psionic Storm spell to devastate enemy Probes (worker units), who are not programmed to react to its presence.[clarification needed]

Combat

Detailed management of units in combat aims to maximize damage given to enemy units and minimize damage to the player's units. For standard combat units the most common techniques are: grouping units into formations, for example to keep lightly armored shooters behind and protected by more heavily armored melee units;[1][2] concentrating the fire of all ranged units on one target and then a second, etc., to destroy threats as fast as possible; withdrawing seriously damaged units from combat, if repairing / healing them is cheaper than replacing them; "dancing" units that have taken some damage out of enemy weapons range and then back into combat once the enemy have locked on to another target; using military tactics such as flanking and counterattacks; exploiting nontransitive ("circle of death" or "rock-paper-scissors") power relationships between units; using cheap units to draw the enemy's fire away from more expensive units, gameplay especially typical of games of the real-time tactics type. Micromanagement is even more necessary for units with special abilities, that can only be used infrequently. "Micromanagement" in this sense is often abbreviated to "micro", which can be used as a noun or a verb.

File:Orion 000.png
Master of Orion's main screen. The panel on the right shows the sliders that control how resources are allocated by the colony which the player has most recently clicked.

Micromanagement versus macromanagement

There is sometimes confusion regarding the difference between micromanagement and macromanagement, normally abbreviated as 'micro' and 'macro' respectively. Macro generally refers to managing large quantities of tasks at the same time. For example, building units from various structures throughout the game while also building more structures, scouting, creating new bases, etc. This is different from micro, which is generally controlling small amounts of units and giving them very specific orders.

Economic micromanagement

The range of possible economic micromanagement techniques is much wider than for combat, because strategy games' economies work in so many different ways. If the game uses "worker" units to gather resources and / or build things (a common technique in Real-time strategy games), one must make sure none are idle and that they are doing the right things, and must avoid letting enemy raiders destroy them (as is happening in the Starcraft image above). In some turn-based games one tells colonies what percentages of their efforts to put into various activities such as industrial growth, research, and building defenses or combat units; as colonies grow or the strategic situation changes, one has to check and adjust these ratios. In Sid Meier's Civilization series, it may be important for either economic or military reasons to build railroads as fast as possible, and doing this efficiently requires considerable micromanagement of Settler / Engineer units.[3]

Twitch vs trick micromanagement

Lua error in package.lua at line 80: module 'strict' not found. Some forms of micromanagement involve continuous input of a large number of commands over a short period of time. This is known as twitch micromanagement. For example, a micromanagement technique known as kiting requires continuous input from the player in order to keep their character at an optimum distance from a target.[citation needed] Another example of twitch micromanagement can be found in racing games whereby a player is required to keep making split second adjustments to the position of their vehicle.

In contrast to twitch micromanagement, some game elements need only occasional input from the player in order to exploit tricks in their behavior.[vague] In these situations, quick thinking is rewarded over continuous, quick reaction. This is known as trick micromanagement.

Other types of games are based entirely on micromanagement, such as pet-raising simulations and games like Cake Mania, where the player's ability to micromanage is often the only skill being tested by the game.

Policy-based micromanagement

Some games are designed in such a way that players must constantly set or check strategic parameters to ensure that operations are proceeding smoothly and efficiently. A typical city-building game or 4X game, for example, requires the player to regulate taxation and production levels in order to keep their industries and commerce flowing. The amount of detail that goes into a simulation like this may necessitate spending a disproportionate amount of time in adjusting relatively minor parameters in order to achieve maximum efficiency.

Controversy about micromanagement in games

Micromanagement can divert the player's attention from grand strategy by overloading the player with repetitive and mechanical work.[4] Some commentators think that "Strategy is irrelevant in today’s real-time strategy games when you’re playing against a fourteen-year-old who can click twice as fast as you."[3] Games in which constant micromanagement is needed are often described as "micromanagement hell".[5][6][7]

In turn-based games the need for economic micromanagement is generally regarded as a defect in the design,[3] and more recent TBS games have tried to minimize it.[5][8][9] But hands-on tactical combat is a feature of many turn-based games (e.g. Master of Orion II, Space Empires III, Heroes of Might and Magic III), and reviewers complained about the difficulty of controlling combat in Master of Orion 3.[10]

There is controversy between fans[who?] of different RTS games about whether micromanagement is: (a) a skill which involves making decisions quickly while under pressure; or (b) a chore which degenerates into a "clickfest" where a player who is faster with the mouse usually beats a player who is better at grand strategy.[11][12] As a result RTS games vary widely from e.g. Total Annihilation, which eliminates most economic micromanagement and reduces tactical micromanagement, to StarCraft, in which both economic and tactical micromanagement are considered important skills. Software has been developed to analyze players' Actions Per Minute (commonly known as APM).[13][14] Other games aim for differing levels of micromanagement of different types: for instance, the Relic Entertainment title Dawn of War 2 minimises economic micromanagement as much as possible, such that there is no base construction, all units are produced from a single source, and resources are accumulated automatically over time by controlling strategic battlefield locations, while on the other hand the game emphasises tactical micromanagement as its primary skill, with combat taking place principally between relatively small squads of highly effective and highly vulnerable units, with victory a function of the rapid deployment of special weapons and tactics in order to counter enemy manoeuvres and inflict maximum damage quickly while avoiding sustaining damage.

A Gamasutra article pointed out that micromanagement in Civilization III resulted in the game becoming "a chore more than a game," explaining: "Computers can now animate more units than any player could reasonably want to control, and the number will continue to increase exponentially."[15]

Many role-playing video games and first-person shooters are developing more advanced hotkey layouts, allowing these genres to develop their own micromanagement skills.

Micromanagement in popular culture

  • The popular Internet-distributed mockumentary series Pure Pwnage coined the term "über-micro", a term describing unusually superior levels of micromanagement. In one episode, it was claimed that micromanagement was discovered in "The Battle of 1974".[16]
  • In South Korea, the real-time strategy game StarCraft is highly popular as a professional sport.[17] The need to micromanage efficiently and multitask under pressure are regarded as features that make it suitable for top-level competitions.[18] The game is broadcast on Korean national television, showing professional players' micromanagement skills.[19]

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 3.2 Lua error in package.lua at line 80: module 'strict' not found.
  4. PC Strategic Games FAQ: 2.8) What is a 4X game?
  5. 5.0 5.1 The Geryk Analysis - Master of Orion 3 rebuttal at quartertothree.com (2001)
  6. D-Day (PC) review at gamespot.com (2004)
  7. Emergency 3 review at armchairempire.com (2006)
  8. Galactic Civilizations reviews at metacritic.com
  9. Master of Orion 3 reviews at metacritic.com
  10. Master of Orion 3 review at quartertothree.com (2003)
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Total Annihilation review at gamespot.com (1997)
  14. BWChart FAQ
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Pure Pwnage - Episode 203
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. World Cyber Games - National Geographic Channel documentary (90 second clip on YouTube)

See also