Vampire: The Masquerade – Bloodlines

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Vampire: The Masquerade – Bloodlines
File:Vampire - The Masquerade – Bloodlines Coverart.png
Developer(s) Troika Games
Publisher(s) Activision
Director(s) <templatestyles src="Plainlist/styles.css"/>
Producer(s) <templatestyles src="Plainlist/styles.css"/>
Designer(s) <templatestyles src="Plainlist/styles.css"/>
Programmer(s) <templatestyles src="Plainlist/styles.css"/>
Composer(s) Rik Schaffer
Engine Source
Platforms Microsoft Windows
Release date(s)
    Genre(s) Action role-playing
    Mode(s) Single-player

    Vampire: The Masquerade – Bloodlines is a 2004 action role-playing video game developed by Troika Games and released by Activision for Microsoft Windows. Set in White Wolf Publishing's World of Darkness, the game is based on White Wolf's role-playing game Vampire: The Masquerade and follows either a male or female character who is killed and subsequently revived as a fledgling vampire. The game depicts the fledgling's journey through 21st-century Los Angeles to uncover the truth behind a recently discovered relic that heralds the end of all vampires.

    Bloodlines is presented from first- and third-person perspectives. The player assigns their character to one of several vampire clans—each with unique powers, customize their combat and dialog abilities and progress through Bloodlines with violent and nonviolent methods. The selection of clan affects how the player is perceived in the game world, and which powers and abilities they possess; this opens up different avenues of exploration and methods of interacting with or manipulating other characters. The player is able to complete side missions away from the primary storyline by moving freely between the available hubs: Santa Monica, Hollywood, downtown Los Angeles, and Chinatown.

    Troika's 32-member team began development of Bloodlines in November 2001, as an indirect sequel to the previous year's Vampire: The Masquerade – Redemption. Troika used Valve Corporation's Source game engine, then-in-development, which was being used for Valve's own Half-Life 2. The game's production was turbulent, as the design's scope exceeded the available resources, and the team were left without a producer for nearly a year until Activision appointed David Mullich to the role, where he found designs and levels unfinished or abandoned. After three years in development with no end in sight and running over budget, Activision set a strict deadline for completion, and Bloodlines was released incomplete on November 16, 2004.

    Released in competition with Half-Life 2 and several other titles, Bloodlines sold fewer than 80,000 copies during its initial release, which was considered a poor performance. It divided critics at the time; although they praised the game's writing and scale of choice, they criticized its technical flaws. It was Troika Games' last production before its failure in early 2005, when it was unable to secure additional projects. The game has a cult following as a rarely replicated example of gameplay and narrative, and contemporary criticism has recognised it as a flawed masterpiece. As of 2014, Bloodlines had received ten years of post-release support from its fans, who have supplied fixes and restored lost and deleted content.

    Gameplay

    Bloodlines is an action role-playing video game optionally presented from the first- or third-person perspective.[2] Before the game begins, players create a male or female vampire character by selecting a vampire clan and configuring available points in three areas—Attributes, Abilities and Disciplines (vampiric powers)—or by answering questions, which create a character for the player.[2][3] The player can select one of seven vampire clans:[4] the powerful Brujah, the decadent Toreador, the insane Malkavian,[5] the aristocratic Ventrue,[4] the monstrously-deformed Nosferatu, the blood-magic wielding Tremere,[6] or the animalistic Gangrel.[7]

    The player builds their character by spending acquired points to increase their ratings in the three areas. The points spent on Attributes and Abilities combine to determine a player's success or effectiveness in performing tasks such as using firearms, brawling, and lock-picking; for example, determining how accurate or how far the player can shoot, or if they can hack a computer.[8][9][10] Attributes are represent by physical (strength, dexterity, and stamina), social (charisma, manipulation, and appearance), and mental (perception, intelligence, and wit). Abilities are talents (such as brawling and dodging), skills (such as firearms and melee) and knowledge (such as computers and investigation).[10] The player is initially assigned points to spend in the three areas, with the amount they can spend determined by clan; for example, the Brujah can spend the most points on physical and skill attributes. During character creation, each upgrade costs one point. The upgrade cost increases as the game progresses.[7] Each ability can be raised from zero to five, and it is impossible to accrue enough experience points to complete every skill (allowing the player to specialize or balance their character).[2][8] Experience points are gained by completing quests, finding items or unlocking secret paths, rather than killing enemies, and are used to increase or unlock the character's statistics and abilities.[11][12] The game features a main story, and optional side quests that can be completed at any time; the player is able to move between the available areas at will to revisit locations, characters, or merchants.[13]

    The player's clan affects their skills and powers. Although the attractive Toreadors receive bonuses for seduction and persuasion, opening additional dialog options, they are physically weak; the Nosferatu are forced to travel in the shadows or through sewers to avoid alerting humans, but receive bonuses to their intelligence and computer skills, which enables access to more information. The Malkavians have separate dialog options, reflecting their inherent insanity.[9] Upgrading some skills provides additional dialog options; attractive and charismatic characters seduce to get their way, aggressive characters threaten, and others persuade their targets to cooperate.[4][14]

    File:Vampire The Masquerade Bloodlines - Gameplay.jpg
    From the third-person perspective, a Malkavian wields a melee weapon. The interface shows character health and weapon on the left, with available blood and Disciplines on the right.

    Firearms combat is first-person, with character points assigned to the firearms skill determining the shot's accuracy and how long it takes to target an opponent.[15] Melee combat is third-person,[2] with access to weapons such as katanas and sledgehammers for melee combat,[16] or pistols, crossbows and flamethrowers for firearm combat.[17] If a player sneaks up on an opponent, they can perform an instant kill; weapons provide unique instant kill animations.[16] The player can block attacks manually or automatically, by leaving their character idle.[18] They can use stealth in missions by sneaking past guards and security cameras, picking locks, and hacking computers to locate alternative routes.[2]

    Each clan has specific Disciplines, which can be used in combat and to create approaches to quests.[2] Although some powers overlap clans, no two clans share the same three Disciplines.[19] More physical vampires can enhance themselves to become fast and lethal killers or summon spirit allies to attack their foes; others can mentally dominate their targets to force their cooperation or render themselves invisible to hide from detection;[2] and others can boil their opponent's blood from afar.[6] Some Disciplines, such as Auspex (which boosts perception, highlighting items and other characters' auras through obstacles) and Blood Buff (which temporarily upgrades strength, dexterity, stamina and lockpicking) are common to all vampires.[20] Several abilities can be active at the same time.[21] Blood is a primary currency in Bloodlines, used to activate Disciplines and abilities. It is drained with each use, and can be replenished by drinking from rats, visiting blood banks or drinking from humans by attacking or seducing them;[2][6] the player can feed on enemies during combat.[22] Drinking from innocents for too long can kill them, costing a character humanity points.[6]

    Players are penalized for using certain vampiric abilities in front of witnesses; exposing their existence loses masquerade points. Violating the masquerade five times draws the ire of vampire hunters and loses the game, although additional masquerade points can be earned with quests and other actions.[6][16] The player has humanity points, representing the vampire's humanity. Some actions cost humanity points; a low humanity score alters available dialog options to become more aggressive, and increases the chance of entering a frenzied state and embarking on a killing spree, when the vampire's blood is low. This frenzy can also be triggered by a large amount of damage. Like masquerade points, losing all humanity points ends the game, with the vampire becoming a mindless beast.[6][18] Some areas, known as Elysium, prevent the use of Disciplines or weapons.[21] Players can recruit a female ghoul, Heather, as a customizable servant who gives them blood, gifts, and money.[23]

    Synopsis

    Setting

    <templatestyles src="Module:Hatnote/styles.css"></templatestyles>

    Vampire: The Masquerade – Bloodlines takes place in four areas of 21st-century Los Angeles: Santa Monica, Hollywood, downtown Los Angeles, and Chinatown.[2][24] Set in the World of Darkness, the game depicts a world in which vampires, werewolves, demons, and other creatures shape human history.[12][25] The vampires are bound by a code to maintain their secrecy (forbidding the use of vampiric abilities in front of humans) and avoid unnecessary killing (to preserve the vampire's last shreds of humanity).[6][26] The vampires are divided into seven clans of the Camarilla, the vampire government, with distinctive traits and abilities. The Toreadors are the closest to humanity, with a passion for culture; the Ventrue are noble, powerful leaders; the Brujah are idealists who excel at fighting; the Malkavians are cursed with insanity, or blessed with insight; the Gangrel are loners, in sync with their animalistic nature; the secretive, untrustworthy Tremere wield blood magic; and the monstrous Nosferatu are condemned to a life in the shadows to avoid humanity. The clans are loosely united by their belief in the Camarilla's goals and opposition to the Sabbat: vampires who revel in their nature, embracing the beast within. The Anarchs are a faction of idealistic vampires opposed to the Camarilla's political structure, believing that power should be shared by all vampires.[7]

    The main character of Bloodlines, whom the player controls, is an unnamed fledgling vampire, transformed at the start of a game and belonging to one of the clans.[27] The fledgling is employed by Sebastian LaCroix (voiced by Andy Milder),[1] prince of Los Angeles' vampires.[27] The fledgling's travels through the vampire world bring them into contact with other undead creatures such as the deformed information broker Bertram Tung, the Anarch Smiling Jack,[27] and the mentally-unstable Voerman sisters, Jeanette and Therese.[9] Chinatown is controlled by the Kuei-Jin, Asian vampires led by Ming-Xiao, who do not require blood and consider themselves superior to the other vampires.[28]

    Plot

    The game begins with the player character, an unnamed human, being killed and resurrected as a fledgling vampire. For this unauthorized act, the fledgling and their Sire are brought before the Camarilla. The Sire is executed by order of LaCroix; the fledgling is spared the same fate by the intervention of the Anarch, Nines Rodriguez, and employed by the prince.

    LaCroix sends the fledgling to Santa Monica to help his ghoul, Mercurio, destroy a Sabbat warehouse. Following his success the fledgling travels to downtown Los Angeles, meeting separately with Nines, LaCroix, and Jack. LaCroix tasks the player with investigating a docked ship, the Elizabeth Dane, for information about an Ankaran sarcophagus rumored to contain the body of an Antediluvian, one of the oldest and most powerful vampires, whose arrival would herald the vampire apocalypse, Gehenna. The fledgling discovers that the sarcophagus seems to have been opened from within.

    Increased Sabbat activity coincides with the disappearance of the Malkavian chief, Alistair Grout. At Grout's mansion, the fledgling sees Nines leaving and discovers Grout's remains in the mansion with vampire hunter Grunfeld Bach, who denies involvement in Grout's death. Learning about Nines' presence at the mansion, LaCroix tells the other chiefs to approve Nines' execution. The fledgling is sent to the Museum of Natural History to recover the sarcophagus, but finds that it has been stolen. Jack later suggests to the fledgling that LaCroix wants the sarcophagus to drink the blood of the ancient within, gaining its power.

    Believing that Gary, the Nosferatu chief, has stolen the sarcophagus, the fledgling is sent to Hollywood to find him; after locating a captured Nosferatu for Gary, he reveals that the sarcophagus was stolen by the Giovanni vampire clan. The fledgling infiltrates the Giovanni mansion and finds the sarcophagus guarded by the Kuei-Jin, who claim their leader, Ming-Xiao, has formed an alliance with LaCroix. The locked sarcophagus is returned to LaCroix's tower and Beckett, a vampire historian, tells the fledgling that the only person who can open it has been abducted by Grunfeld to lure LaCroix. The fledgling kills Grunfeld and learns that the sarcophagus' key has been stolen.

    They return to LaCroix, learning that the Sabbat tried to steal the sarcophagus to destroy it and prevent Gehenna, and kill the Sabbat leader to disperse his followers. The fledgling is met by Ming-Xiao, who offers to form an alliance. Ming-Xiao reveals that she has the key, and LaCroix killed Grout to prevent his powerful insight from unveiling LaCroix's plans; Ming-Xiao changed into Nines at the mansion to frame him. Denying Ming-Xiao's claims, LaCroix rescinds the blood hunt on Nines and entrusts the fledgling with recruiting the Anarchs to punish the Kuei-Jin for murdering Grout. The fledgling finds Nines hiding in the forest, and they are then attacked by a werewolf and Nines is badly injured. The fledgling escapes with Jack, who reveals that LaCroix has issued an execution order on the fledgling for framing Nines on orders from Ming-Xiao.

    The end varies, depending on whom, if anyone, the fledgling allies with. If the fledgling supports LaCroix or Ming-Xiao, each sends the fledgling to kill the other. LaCroix opens the sarcophagus, to be killed with the fledgling by hidden explosives; Ming-Xiao betrays the fledgling, chaining them to the sarcophagus and sinking it in the ocean. Supporting the Anarchs or no one makes the fledgling kill Ming-Xiao and maim LaCroix, who is killed after he opens the sarcophagus. If the fledgling opens the sarcophagus, they die in the explosion. If the fledgling is a Tremere, they kill Ming-Xiao; LaCroix is replaced by Tremere leader Maximillian Strauss, and the sarcophagus is stored. Each ending has Jack watching from afar with the mummy taken from the coffin and the enigmatic taxi driver who transports the fledgling between locations, who says "The blood of Caine controls our fate ... Farewell, vampire."

    Development

    Conception

    File:Vampire The Masquerade Bloodlines - Changes.png
    Bloodlines underwent many modifications during its three-year development. (above) The original character model of Jeanette in a Hollywood club; (below) the final model in a Santa Monica club.[1]

    The development of Vampire: The Masquerade – Bloodlines began at Troika Games in November 2001. The developers wanted to put a role-playing game in a first-person setting, believing that the genre had become stale.[26] Troika approached publisher Activision with its idea; Activision suggested using the Vampire: The Masquerade license used a year earlier in Nihilistic Software's Vampire: The Masquerade – Redemption, which had experienced sufficient success to merit a sequel.[26][29] Instead of developing a sequel to Redemption, the development team researched the White Wolf property, including the game's rules and its storylines.[30][26] Troika was a small game studio, with five developers and a total staff of thirty-two (including lead writer Brian Mitsoda, who joined the team less than a year after development began).[1][31][32] Although some preliminary design and levels were completed, much of the work was abandoned or redeveloped.[31]

    Troika wanted to make a 3D game, but was uncertain whether to build a new game engine or license an existing one and whether to use first- or third-person.[33] At that time, the Source game engine was being built by Valve Corporation.[31] Valve employee Scott Lynch approached Troika about using the engine, and it was the first external team to use it.[33][26] Troika chose Source for its facial animation and lip-synching system, since it wanted players to speak to the characters face-to-face.[26] Since the engine was in development with Bloodlines and Valve's own Half-Life 2, Troika was working with unfamiliar code and tools, forcing it to write its own code to compensate for the unfinished engine, and with only a single source for technical support.[1][34] Troika developed a lighting system to create distinctive, moody illumination for the nighttime setting, a particle system for the special effects accompanying the vampire Disciplines, and a cloth system for clothing flow.[33] Source lacked its later artificial intelligence (AI) coding, and Troika's code worked poorly with the Source engine.[35]

    Writing

    Many of the central plot elements existed before designer Brian Mitsoda's involvement: the prince, the anarchs being upset, aspects of the Gehenna storyline, and Jack and the sarcophagus as a major subplot. The designers broadly tied the overarching story into each hub and level. Each designer controlled their assigned section of the game, and working with a small team enabled quick decision making and ease in keeping plot elements consistent. Mitsoda became the primary writer for many of the characters and their quests, dialog, and side content in the game, such as emails, which helped retain a consistent narrative. He was given freedom with respect to the script, with no restrictions on language or content, and could rewrite characters when he thought his initial draft weak.[31] Although the story was developed by Troika, it is inspired by White Wolf's Time of Judgment novels about a vampire apocalypse. Bloodlines' story was accepted as canonical by White Wolf, with the game serving as a prequel to Time of Judgment and including characters from the White Wolf game, such as Jack.[20][36] Discussing character design, Mitsoda said he tried to disguise the need for characters who simply point a player in an appropriate direction:

    "You need a character to pose a problem or give out a quest or be a barrier of some kind. I don't like to make the [character] outright say 'I need you to do X, then I'll give you Y' ... – it makes the character into an automated quest kiosk. I like the characters to come off like people actually do – they don't say 'hi' when strangers come knocking, they say 'who the hell are you?' or they're expecting you and know more than they let on, or they don't care. I don't like my [characters] to be standing around as if their lives begin when the character starts talking to them and end when the player leaves.[31]

    Single purpose characters needed a distinctive personality trait to quickly establish them with the player, rather than serving as a disposable item, while major characters had to reflect the player's progression and actions through the game. Mitsoda wrote the characters by thinking about who each character was, assigning them motivations determining why they were where they were, what they thought about the player and what they wanted from them.[31] In accordance with a suggestion by fellow writer Chad Moore[37] the Malkavian player character has a dialog script distinct from that of the other eight clans; Mitsoda said it was one of the simpler aspects of the development cycle. He wrote the Malkavian script last, with time running out on development, and the overwork and lack of sleep contributed to what Mitsoda considered an unhealthy state of mind, ideal for writing insane dialog. He wanted to highlight their madness, without making it comical.[1][31] Since the story is set during the Camarilla's takeover of Los Angeles, the team simplified the plot by only allowing the player to belong to one of the LA-based clans.[7]

    Design

    Troika co-founder Jason Anderson's research on Vampire: The Masquerade source material and fansites found that character interaction and involvement in the vampire societies, not statistics and powers, was the game's main attraction. Troika tried to remain true to the pen-and-paper role-playing game, hoping not to alienate the game's fans, but rules designed for multiple players did not translate well to single player computer game design. The team attempted to discover which elements could work equally well in pen-and-paper and computer games. Although much of the character system and attributes translated, not all the attributes (such as "knowledge of law") made sense in the computer game. Of 30 pen-and-paper abilities, 15 reached the final design.[38]

    Another difficult area was feats. Although common feats worked well, with a random chance of success or failure, uncommon ones would appear to fail more often. To avoid this, randomization was replaced by a degree of difficulty in accomplishing the feat. Although pen-and-paper falling damage is random, the computer game bases damage on the distance of the fall. The team's biggest challenge was adapting disciplines. The pen-and-paper version may require a little blood that requires a long time to use, or have no blood cost and can be used at will; upgraded disciplines had additional requirements considered too confusing for a computer game. Troika attempted to equalize the disciplines, keeping the effect intact and normalizing the cost, so a first level power requires one blood point, a second level two points and so on.[38] To balance the clans the aristocratic Ventrue were only allowed to feed on noble blood, though this was changed to allow them to feed on lower-class humans, receiving less blood.[39] During character creation, the game had an optional character biography with unique positive and negative characteristics (increasing one ability while limiting another).[10] This was removed from the released game; Activision felt that there was insufficient test time, and removing it was a more stable option.[40]

    The team's previous experience was with turn-based combat games, and it struggled to develop a real-time combat system affected by customizable attributes and abilities that provided feedback to the player on how those statistics were affecting the battle. It initially found that by adhering too closely to the White Wolf source material rules for guns, where the effectiveness of a shot is determined in a contest between the player's skill and the opponent's defense, the firearms seemed broken; the player would not hit where they aimed. Troika found it difficult to mesh the available factors in a real-time setting.[22] Melee combat had to deal with a variety of melee weapons and animations and adjust for melee-on-melee and melee-on-ranged combat.[41]

    Troika used first-person perspective to immerse the player in the setting, interacting face-to-face with the characters and seeing their facial reactions to the player.[42][43] It chose to follow a single-character to aid the immersion, creating the isolation of a vampire unable to trust any other character. This aided the story and compensated for the technical issues of allowing multiple player characters.[43]

    Choice is a significant aspect of the game, requiring a non-linear design to accommodate the customized characters. Level design began with a list of factors such as Disciplines, stealth and feats. Each area had to be viable for a shooting character (sufficient ammunition), a discipline-focused character (sufficient blood sources to keep the powers fueled) and a melee specialist (to reach enemies without being killed), with stealth options and option combinations. Level design began with a focus on stealth, taking into consideration the positioning of guards and the character's potential stealth capability at that point in the game. Then direct, combat-heavy and dialog paths were added.[44] The amusement arcade area was to feature playable versions of Activision arcade games such as Pitfall!, though the idea was abandoned due to time constraints.[40]

    Director Leonard Boyarsky considered the animation system important in the team's choice of the Source engine. The integrated "faceposer" tool allowed Troika to customize facial animations, expressions, gestures and lip-synching, eliminating the need to explain what a character was doing. Every non-player character required a voiceover, which helped Troika define its characters more quickly. The engine had a physics system permitting new features, such as monsters hurling corpses at the player or dying characters realistically crumbling into pieces, instead of requiring pre-built animations.[33] Although Troika had ignored first-person engines due to technical limitations, such as a low polygon count and limited texture memory, as the technology improved, it thought it could create a real-time action game without sacrificing the immersion and story of a role-playing game.[41]

    Describing the choice of developing a game based on the existing White Wolf property over creating their own, Boyarsky said that although an original property lacked the constraints of an existing one the downside was that it had not been tested and could be rejected by its potential audience; an existing property was proven.[43] Troika tried to stay as close as possible to the White Wolf rules, while reducing the number of abilities and disciplines to those relevant to Bloodlines gameplay.[19]

    Later development

    File:David Mullich Publicity Photo.jpg
    Video game producer David Mullich was assigned to the team over a year after development had begun.

    Activision introduced the game in May 2003,[45] but, that October, Valve experienced a security breach in which hackers stole the source code for Half-Life 2. The breach required new security implementations for the engine, delaying both games; the release of Bloodlines was postponed until early 2005.[46] Until May 2004, Troika and Activision said that the game would feature a multiplayer component and modes including a team of vampires against a team of vampire hunters, with the ability to upgrade characters between each round.[47] The team was left without a producer by Activision for over a year before David Mullich was assigned to the project. With no producer oversight, Mullich found the game's design incomplete, game levels created and abandoned, and several technical issues, including problems with code for the proposed multiplayer option.[48][49] The Source multiplayer code was in its infancy, increasing its development time, and the idea was abandoned.[40]

    In addition to problems with the Source engine, the designers found that the game's scope exceeded their resources. Bloodlines has several styles of gameplay, requiring different interfaces, animations and artificial intelligence for stealth and melee combat, and first- or third-person capability.[1][31] Compared to contemporary first-person shooters, with 10 to 20 animated character models, Bloodlines had over 150 characters with 3,000 unique animations, in addition to boss characters, with their own styles of movement.[41] The designers underestimated the length of time required to develop and improve these systems. The game's scope suffered from content not being removed when necessary; other components would be endlessly refined without being finalized, preventing the developers from focusing on other parts of the game system.[1][31] All content additionally required approval by White Wolf and Activision.[35]

    After three years in development, the game was progressing slowly and it was unknown when it would be finished.[1] Activision set a series of deadlines for the project's development to ensure Troika would have sufficient time to effectively test the game, though these milestones were repeatedly extended, and Bloodlines eventually ran over budget.[29] In 2003, Activision intervened, ordering that the game be ready for release in the next few months, and even advancing more money to Troika to complete its work on The Temple of Elemental Evil for Atari, freeing the Troika team to work on Bloodlines exclusively.[34][35] Activision eventually issued an ultimatum that the project be finished within months, on September 15, 2004.[1][29] Troika delivered a version of Bloodlines on the required date; due to its scale, the game underwent three weeks of testing. Activision decided that the game was suitable for release, but was contractually-bound to withhold Bloodlines until after the debut of Half-Life 2 in November 2004. Troika convinced Activision to use the delay to fund further development; the additional budget was not enough to pay all of Troika's staff, and some employees worked unpaid to complete the project. This version underwent another three weeks of testing to become the final release code;[29] the game was still unfinished when Activision forced its release.[1] Bloodlines' creative director Jason Anderson blamed Activision, saying that the publisher took the game from Troika without providing enough time to test and polish it.[34] During the nearly four years of development, he estimated that the team worked overtime for all but two months.[35]

    Music

    The game's original score was composed and produced by Rik Schaffer.[50][51] Troika licensed many songs for the game, and posters for real bands are featured on the walls of the game's clubs.[50][52] The soundtrack was released as a limited edition CD to customers who pre-ordered the game through Best Buy.[53] It features nine tracks by artists including Daniel Ash, Chiasm, Tiamat, Darling Violetta, Genitorturers, and Lacuna Coil.[54] "Bloodlines", performed by Al Jourgensen and Ministry, was composed and performed specifically for the game.[55] The licensed tracks were chosen by Activision without input from Troika.[40]

    Tracks
    No. Title Artist(s) Length
    1. "Bloodlines"   Ministry 7:16
    2. "Come Alive"   Daniel Ash 5:55
    3. "Cain"   Tiamat 5:27
    4. "Swamped"   Lacuna Coil 4:02
    5. "Isolated"   Chiasm 5:17
    6. "Needle's Eye"   Die My Darling 3:55
    7. "Pound"   AERIAL2012 5:32
    8. "Lecher Bitch"   Genitorturers 4:15
    9. "Smaller God"   Darling Violetta 4:25
    Total length:
    46:04

    Release

    File:Bloodlines E3 2003.jpg
    Models as some of the game's clans during a promotion for the game at E3 2003

    Vampire: The Masquerade – Bloodlines was released on November 16, 2004 in competition with Half-Life 2, Metal Gear Solid 3: Snake Eater, Halo 2, and several other titles.[31][56] Valve's contract for Troika's use of the Source engine guaranteed that Bloodlines could not be released before Half-Life 2,[57] and could not be introduced to the public until after the announcement of Half-Life 2, over eighteen months after development began.[58] In February 2004, the game was scheduled for release in spring 2005, partially to avoid competing with Half-Life 2 and the competitive Christmas period, before Activision moved the date to November 2004.[59]

    In a 2013 interview, Mitsoda said that it was released at "the worst possible time - most people didn't even know we were out ... fans and the Troika [developers] are always going to wonder what the game could have been like with another six months."[1] Activision obtained model Erin Layne to play Jeanette in promotional material for the game. Layne worked with Bloodlines artist Tim Bradstreet for a day to provide the poses chosen by Activision to represent Jeanette in the game's posters, clothing, and other items.[60]

    Bloodlines' initial release sold 72,000 copies and earned approximately $3.4 million in sales, below Troika's other games, Arcanum: Of Steamworks and Magick Obscura (234,000 units, $8.8 million) and The Temple of Elemental Evil (128,000 units, $5.2 million).[57][61] In comparison, Bloodlines' release competitor Half-Life 2 had sold 6.5 million copies by 2008.[62] Bloodlines‍' relative failure contributed to the demise of Troika Games.[32][35]

    Shortly after its debut, most of the development staff were laid off; the remaining staff tried to patch Bloodlines and develop game concepts to secure funding to keep Troika in business.[35][63] Troika, unable to obtain further funding from Activision or other publishers,[35] released its employees in two waves: the first in November 2004, followed by the remaining staff in December,[32] except for its three founders, Anderson, Boyarsky, and Tim Cain.[64][65] Some employees worked without pay to fix the game.[63] When the company closed in February 2005, it had secured no other game development deals.[1][66] That month, Boyarsky confirmed that Troika had not been working on a patch for the game since most of its staff were gone since December 2004.[32] In a November 2004 interview Boyarsky said that although the team would like to pursue a Bloodlines sequel, the decision was Activision's.[40] In a 2006 interview, Anderson said that although Troika Games' library had been critically well received, consistent technical issues had marred the perception of the company's games, contributing to Troika's difficulty in obtaining new projects.[65]

    Unofficial patches have been created by the game's fans to address Bloodlines' technical problems, and restore missing and incomplete content.[1][67][68][69] After experiencing problems with the first versions of an unofficial patch created by Dan Upright, analytical chemist Werner Spahl continued patching the game from version 1.2 with permission and instructions. The game community tested Spahl's patches, providing reports on bugs and spelling errors. Although the game's complexity meant that repairing one aspect often broke another, as work on the patches progressed Spahl began restoring removed and incomplete content in the game files, adding quests, items, weapons, and characters, with fan help to provide voice acting, models, and reinstating whole levels.[1] The changes altered the original game so much that Spahl was criticized by some of the game's fans. This resulted in two patch versions: a basic version, fixing the game's technical issues, and a "plus" version with the additional content. As of April 2014, the game has had almost 10 years of post-release support with the release of version 9 of the patch.[1][70] The game fared better following its release on Valve's Steam digital distribution service in March 2007, where, as of 2015, it has sold 492,000 units.[71]

    Reception

    Reception
    Aggregate scores
    Aggregator Score
    GameRankings 81%[72]
    Metacritic 80/100[73]
    Review scores
    Publication Score
    AllGame 3.5/5 stars[74]
    Eurogamer 7/10[6]
    GameSpot 7.7/10[2]
    GameSpy 4/5 stars[8]
    IGN 8.4/10[75]
    PC Gamer (US) 77%[76]
    PC Zone 8.6/10[14]
    VideoGamer.com 8/10[77]

    Vampire: The Masquerade – Bloodlines received a mixed response, with reviewers praising its writing and presentation and criticizing its technical problems.[78] The aggregating review websites GameRankings and Metacritic give it a score of 81% (based on 68 reviews) and 80 out of 100 (based on 61 reviews), respectively.[72][73] Despite generally favorable reviews,[72][73]

    The game has been called a flawed masterpiece.[8][27][79] The scale and variety of choice and effect was highlighted by reviewers as Bloodlines' greatest success, including the variety of clans, with specific dialog options, and the specific reactions from other characters, each with their own clan loyalty and bias.[6][9] GameSpy called it a nearly flawless classic role-playing game;[8] the The New York Times described it as brilliant but unfinished.[79] Eurogamer praised its "effortlessly intelligent" script, saying that "no other game has come close. Nothing's even tried". VideoGamer.com opined that at its best, Bloodlines stands among the greatest RPGs of the preceding five years, although its technical problems should be remembered.[6][15][77] According to HonestGamers, the game "may not be polished and may end with a sigh instead of a shout, but for its ambition alone it deserves stream after stream of compliments."[80] Reviewers compared it to other successful role-playing games, including Fallout,[12] Star Wars: Knights of the Old Republic,[14] The Elder Scrolls III: Morrowind, Planescape: Torment, Baldur's Gate II,[12] and Deus Ex;[14] Eurogamer described Bloodlines as Deus Ex with vampires.[2][6][77]

    IGN appreciated Bloodlines' rewarding exploration outside the main story, and the New York Times and GameSpy praised its "wonderfully imaginative" missions.[9][79] Reviewers noted that later parts of the game were disappointing, delivering repetitive combat-focused missions with regenerating enemies, abandoning dialog and stealth and punishing players who build characters with more social skills than combat abilities.[6][15][79] GameSpy said that it had never seen a role-playing game so affected by player actions with everything, from clan choice and character build to actions in missions, influencing future options and dialog.[9]

    Its writing was consistently praised by reviewers. The narrative was considered deep, successfully using White Wolf's Vampire: The Masquerade content. Eurogamer said it had the best script the website had ever seen in a video game,[6] and others described it as a superbly crafted tale of conspiracies, underworld subterfuge, fun and intrigue.[2][9][76] Reviewers appreciated the use of adult themes, such as sex and death, in the storyline of a contemporary video game which no other games had tackled with similar effectiveness. The mature themes succeeded without being gratuitous or exploitative, and were explored honestly and intelligently by a knowledgeable writer.[2][6][77] The game's characters were praised for their memorable, developed personalities, with most major characters possessing their own backstory and presented as living people instead of ciphers.[3][9][77] Its ending had a mixed response, with some reviewers appreciating their ability to choose one of the game's four endings (adding an incentive to replay the game) and others considering the ending anti-climatic.[2][79]

    GameSpot and GameSpy called the dialog was sharply written, with many memorable lines.[2][9] Eurogamer noted that the characters' frequent use of vulgar language worked; written as real people, such language fit their character rather than giving the game an adult veneer.[6] The website appreciated the breadth of dialog options, allowing the player greater control of how to play their character. PC Zone opined that the quantity of well written dialog did not guarantee quality; many player choices seemed to have little effect on a conversation's outcome, and the best response was often the most obvious.[3] The voice acting was repeatedly praised for the actors' quality and the amount of voice work, due to the many dialog options.[2][16]

    Much of Bloodlines' criticism focused on technical problems when it was released, undermining the game experience or making it unplayable.[81][82] Several reviewers noted errors which closed the game and typographical errors in on-screen text. Others cited frequent, sometimes-lengthy load times encounted while moving between hubs and entering or exiting buildings and areas.[2][6][14] GameSpot called the game's artificial intelligence poor, often causing enemies to rush at an armed player, fire at them from too great a distance to be effective or become immobilized while waiting for the player's next attack.[2] IGN noted that stealth broke the AI, allowing traps to be triggered and leaving the assailants standing still, unable to locate a hidden player.[75] GameSpy said that the Source engine was Bloodlines' greatest weakness; although the RPG aspects were the game's strong suit, features of the Source engine, such as first-person shooting, were where it stumbled.[9][15]

    Combat was also criticized. Reviewers called it poor, clumsy, and unsatisfactory,[2][6] complaining that Bloodlines favors melee combat; firearms were weak, unwieldy and slow, even for characters specializing in guns.[2][6][16][75] PC Zone, however, called the first-person shooting entertaining and challenging.[14] Although melee combat was criticized as sluggish and difficult due to enemy attacks interrupting the player's, reviewers considered it overpowered; according to GameSpot, a boss character was killed with melee weapons on a first attempt after the repeated failure to do so with a gun.[2][15] The New York Times found the unavoidable combat in the last part of the game to be so difficult that they had to cheat to succeed.[77][79] Stealth was criticized, with IGN noting that even with low stealth skill it was possible to sneak around many enemies and feed from a guard without alerting another guard next to them.[75] GameSpot opined that some of the best missions were stealth-based, as combat was more straightforward.[2][9]

    Accolades

    In 2004, IGN named Bloodlines the Best PC RPG of that year and GameSpy called the "Ocean House Hotel" quest the Level of the Year.[83] In 2005, Computer Gaming World called it the Role Playing Game of 2004, saying that it offered "a deep, balanced character creation system, a truckload of interesting quests, a good story and great NPCs to interact with."[84] In 2006, PC Zone listed Bloodlines the seventh-best PC game which people were unlikely to have played, calling it the "best buggy game ever released".[85] In 2007, the game was 80th on Computer & Video Games' list of its top 100 games,[86] and 86th on PC Gamer's 2014 list of the same, moving to 63rd in PC Gamer's 2015 edition.[87][88] In 2011, Rock, Paper, Shotgun called Bloodlines one of the most important PC games of all time ("it signposts a direction to a future of games that we were denied"), listing it as one of the 122 Best PC Games Ever.[89][90] Cinema Blend called it one of the most underappreciated games of the decade.[91] In 2011, Official Xbox Magazine called it one of the ten PC franchises it wanted on the Xbox 360 console.[91][92] In 2013, PC Gamer named it one of the 100 Best Horror Games on PC,[93] and PCGamesN called it the seventh-best PC role-playing game.[94] In 2014, Bloodlines was 90th in Empire's readers' poll of the 100 Greatest Video Games of All Time,[63] and Maximum PC chose it as one of the games they wanted to be remastered for contemporary game systems.[95] In 2015, Rock, Paper, Shotgun listed Bloodlines as the PC's 19th Best RPG and 15th Best Horror Game.[96][97]

    Retrospective critiques continue to praise the game's narrative and degree of choice. In 2009, an article in Rock, Paper, Shotgun declared: "The sense of sorrow comes from the realisation that there's nothing like [Bloodlines] on the horizon ... why should there be so few games like this? Oh right, because it's so very hard to do ... the lack of games comparable to Bloodlines is one of the great tragedies of our time."[81] Eurogamer called the game inspirational, with an unmatched level of narrative detail.[82] In 2010, The Escapist called Bloodlines a flawed masterpiece which could have been a genuine masterpiece with more time, money and staff; although great games may inspire awe, it instead created a devoted fan base which continued to develop the game.[34] Bloodlines is considered a cult classic.[34][98]

    References

    1. 1.00 1.01 1.02 1.03 1.04 1.05 1.06 1.07 1.08 1.09 1.10 1.11 1.12 1.13 1.14 1.15 Lua error in package.lua at line 80: module 'strict' not found.
    2. 2.00 2.01 2.02 2.03 2.04 2.05 2.06 2.07 2.08 2.09 2.10 2.11 2.12 2.13 2.14 2.15 2.16 2.17 2.18 2.19 2.20 2.21 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. 4.0 4.1 4.2 Lua error in package.lua at line 80: module 'strict' not found.
    5. Lua error in package.lua at line 80: module 'strict' not found.
    6. 6.00 6.01 6.02 6.03 6.04 6.05 6.06 6.07 6.08 6.09 6.10 6.11 6.12 6.13 6.14 6.15 6.16 6.17 Lua error in package.lua at line 80: module 'strict' not found.
    7. 7.0 7.1 7.2 7.3 Lua error in package.lua at line 80: module 'strict' not found.
    8. 8.0 8.1 8.2 8.3 8.4 Lua error in package.lua at line 80: module 'strict' not found.
    9. 9.00 9.01 9.02 9.03 9.04 9.05 9.06 9.07 9.08 9.09 9.10 Lua error in package.lua at line 80: module 'strict' not found.
    10. 10.0 10.1 10.2 Lua error in package.lua at line 80: module 'strict' not found.
    11. Lua error in package.lua at line 80: module 'strict' not found.
    12. 12.0 12.1 12.2 12.3 Lua error in package.lua at line 80: module 'strict' not found.
    13. Lua error in package.lua at line 80: module 'strict' not found.
    14. 14.0 14.1 14.2 14.3 14.4 14.5 Lua error in package.lua at line 80: module 'strict' not found.
    15. 15.0 15.1 15.2 15.3 15.4 Lua error in package.lua at line 80: module 'strict' not found.
    16. 16.0 16.1 16.2 16.3 16.4 Lua error in package.lua at line 80: module 'strict' not found.
    17. Lua error in package.lua at line 80: module 'strict' not found.
    18. 18.0 18.1 Lua error in package.lua at line 80: module 'strict' not found.
    19. 19.0 19.1 Lua error in package.lua at line 80: module 'strict' not found.
    20. 20.0 20.1 Lua error in package.lua at line 80: module 'strict' not found.
    21. 21.0 21.1 Lua error in package.lua at line 80: module 'strict' not found.
    22. 22.0 22.1 Lua error in package.lua at line 80: module 'strict' not found.
    23. Lua error in package.lua at line 80: module 'strict' not found.
    24. Lua error in package.lua at line 80: module 'strict' not found.
    25. Lua error in package.lua at line 80: module 'strict' not found.
    26. 26.0 26.1 26.2 26.3 26.4 26.5 Lua error in package.lua at line 80: module 'strict' not found.
    27. 27.0 27.1 27.2 27.3 Lua error in package.lua at line 80: module 'strict' not found.
    28. Lua error in package.lua at line 80: module 'strict' not found.
    29. 29.0 29.1 29.2 29.3 Lua error in package.lua at line 80: module 'strict' not found.
    30. Lua error in package.lua at line 80: module 'strict' not found.
    31. 31.0 31.1 31.2 31.3 31.4 31.5 31.6 31.7 31.8 31.9 Lua error in package.lua at line 80: module 'strict' not found.
    32. 32.0 32.1 32.2 32.3 Lua error in package.lua at line 80: module 'strict' not found.
    33. 33.0 33.1 33.2 33.3 Lua error in package.lua at line 80: module 'strict' not found.
    34. 34.0 34.1 34.2 34.3 34.4 Lua error in package.lua at line 80: module 'strict' not found.
    35. 35.0 35.1 35.2 35.3 35.4 35.5 35.6 Lua error in package.lua at line 80: module 'strict' not found.
    36. Osborn 2003, p. 52.
    37. Lua error in package.lua at line 80: module 'strict' not found.
    38. 38.0 38.1 Lua error in package.lua at line 80: module 'strict' not found.
    39. Lua error in package.lua at line 80: module 'strict' not found.
    40. 40.0 40.1 40.2 40.3 40.4 Lua error in package.lua at line 80: module 'strict' not found.
    41. 41.0 41.1 41.2 Lua error in package.lua at line 80: module 'strict' not found.
    42. Lua error in package.lua at line 80: module 'strict' not found.
    43. 43.0 43.1 43.2 Lua error in package.lua at line 80: module 'strict' not found.
    44. Lua error in package.lua at line 80: module 'strict' not found.
    45. Lua error in package.lua at line 80: module 'strict' not found.
    46. Lua error in package.lua at line 80: module 'strict' not found.
    47. Lua error in package.lua at line 80: module 'strict' not found.
    48. Lua error in package.lua at line 80: module 'strict' not found.
    49. Lua error in package.lua at line 80: module 'strict' not found.
    50. 50.0 50.1 Lua error in package.lua at line 80: module 'strict' not found.
    51. Lua error in package.lua at line 80: module 'strict' not found.
    52. Lua error in package.lua at line 80: module 'strict' not found.
    53. Lua error in package.lua at line 80: module 'strict' not found.
    54. Lua error in package.lua at line 80: module 'strict' not found.
    55. Lua error in package.lua at line 80: module 'strict' not found.
    56. Lua error in package.lua at line 80: module 'strict' not found.
    57. 57.0 57.1 Lua error in package.lua at line 80: module 'strict' not found.
    58. Osborn 2003, p. 48.
    59. Lua error in package.lua at line 80: module 'strict' not found.
    60. Lua error in package.lua at line 80: module 'strict' not found.
    61. Lua error in package.lua at line 80: module 'strict' not found.
    62. Lua error in package.lua at line 80: module 'strict' not found.
    63. 63.0 63.1 63.2 Lua error in package.lua at line 80: module 'strict' not found.
    64. Lua error in package.lua at line 80: module 'strict' not found.
    65. 65.0 65.1 Lua error in package.lua at line 80: module 'strict' not found.
    66. Lua error in package.lua at line 80: module 'strict' not found.
    67. Lua error in package.lua at line 80: module 'strict' not found.
    68. Lua error in package.lua at line 80: module 'strict' not found.
    69. Lua error in package.lua at line 80: module 'strict' not found.
    70. Lua error in package.lua at line 80: module 'strict' not found.
    71. Lua error in package.lua at line 80: module 'strict' not found.
    72. 72.0 72.1 72.2 Lua error in package.lua at line 80: module 'strict' not found.
    73. 73.0 73.1 73.2 Lua error in package.lua at line 80: module 'strict' not found.
    74. Lua error in package.lua at line 80: module 'strict' not found.
    75. 75.0 75.1 75.2 75.3 Lua error in package.lua at line 80: module 'strict' not found.
    76. 76.0 76.1 Osborn 2005, p. 94.
    77. 77.0 77.1 77.2 77.3 77.4 77.5 Lua error in package.lua at line 80: module 'strict' not found.
    78. Lua error in package.lua at line 80: module 'strict' not found.
    79. 79.0 79.1 79.2 79.3 79.4 79.5 Lua error in package.lua at line 80: module 'strict' not found.
    80. Lua error in package.lua at line 80: module 'strict' not found.
    81. 81.0 81.1 Lua error in package.lua at line 80: module 'strict' not found.
    82. 82.0 82.1 Lua error in package.lua at line 80: module 'strict' not found.
    83. Lua error in package.lua at line 80: module 'strict' not found.
    84. CGW 2005, p. 64.
    85. Lua error in package.lua at line 80: module 'strict' not found.
    86. Lua error in package.lua at line 80: module 'strict' not found.
    87. Lua error in package.lua at line 80: module 'strict' not found.
    88. Lua error in package.lua at line 80: module 'strict' not found.
    89. Lua error in package.lua at line 80: module 'strict' not found.
    90. Lua error in package.lua at line 80: module 'strict' not found.
    91. 91.0 91.1 Lua error in package.lua at line 80: module 'strict' not found.
    92. Lua error in package.lua at line 80: module 'strict' not found.
    93. Lua error in package.lua at line 80: module 'strict' not found.
    94. Lua error in package.lua at line 80: module 'strict' not found.
    95. Lua error in package.lua at line 80: module 'strict' not found.
    96. Lua error in package.lua at line 80: module 'strict' not found.
    97. Lua error in package.lua at line 80: module 'strict' not found.
    98. Lua error in package.lua at line 80: module 'strict' not found.

    Bibliography

    • Lua error in package.lua at line 80: module 'strict' not found.
    • Lua error in package.lua at line 80: module 'strict' not found.
    • Lua error in package.lua at line 80: module 'strict' not found.

    External links