Jump to content

Programmer art

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by 166.173.185.44 (talk) at 15:39, 5 August 2015. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
A computer-generated image of a typical platform game, showing simplified graphics of the player's character, a door, a ladder, a set of spikes, a lever to be pulled, and one of the monsters. The graphics are very simple with basic textures, on a plain blue background
A computer-generated image of the release copy of Braid as a platform game, showing the main character, a door, a ladder, a set of spikes, a lever, and one of the monsters. The art appears to be painted elements, consisting of wooden beams adjoining rock faces, with foliage around, against a faded yellow-green background showing more of a forest.
Jonathan Blow's original programmer art for the game Braid (top) compared with the game's final artwork by artist David Hellman.

Programmer art refers to temporary graphics added by the software developer to test functionality. When creating the artwork, speed is a priority and aesthetics are secondary (if they are given any consideration at all). In fact, programmer art might be intentionally bad. This draws attention to the fact that the artwork is only a placeholder and should not go into the final product. This practice might also speed its replacement.

Examples include stick figure sprites and fuchsia textures. Alphanumeric characters and simple 2-d shapes are very common as programmer art in games with a "top-down perspective". An example of this is the use of text symbols to represent characters and landscape elements in the game Dwarf Fortress.

Not all programmers decide to replace the art in their games prior to release, though. This is especially common in indie games, since indie developers generally lack the resources to commission large amounts of art for their games.