Paradroid

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Paradroid
256px
European cover art
Developer(s) Graftgold
Publisher(s) Hewson Consultants, Jester Interactive Publishing
Designer(s) Andrew Braybrook
Platforms Commodore 64, Amiga, Atari ST, Acorn Archimedes, C64 Direct-to-TV, Virtual Console, iOS (ZX Spectrum Elite Collection)
Release date(s) 1985
Genre(s) Shoot 'em up / Puzzle
Mode(s) Single-player

Paradroid is a Commodore 64 computer game written by Andrew Braybrook and published by Hewson Consultants in 1985. It is a shoot 'em up with puzzle elements and was critically appraised at release. The objective is to clear a fleet of spaceships of hostile robots by destroying them or taking them over via a mini-game. It was later remade as Paradroid 90 for the Commodore Amiga and Atari ST home computers[1] and as Paradroid 2000 for the Acorn Archimedes. There exist several fan-made remakes for modern PCs. In 2004 the Commodore 64 version was re-released as a built-in game on the C64 Direct-to-TV,[2] and in 2008 for the Wii Virtual Console in Europe.[3]

Gameplay

Paradroid on the C64. Player controls the "139" droid.

Enemy forces have hijacked a space fleet by turning its robot consignment against the crew and your job is to neutralize all the robots, rescuing the humans. You control a prototype influence device that allows you to control the hostile robots.[4]

The game is set on a spaceship viewed from a top-down perspective. The ship consists of numerous rooms and levels, each one populated by hostile robots or "droids". The player, in control of a special droid called the "Influence Device", must destroy all the other droids on the ship. Each droid (including the player) is represented as a circle around a three-digit number. The numbers roughly correspond to the droid's "power" or "level", in that higher-numbered droids are tougher to destroy.[5]

The Influence Device is numbered "001". The primary way in which the Influence Device destroys other droids is by "linking" with them, effectively taking them over. When the player takes over another droid, the previously-controlled droid is destroyed.

Taking over a droid is done via a mini-game involving basic circuit diagrams and logic gates. Each droid has one side of the screen, with a series of logic gates and circuits connected together. The droids have a number of "power supplies" that can apply power to one circuit. Higher-numbered droids have more power supplies. At the end of a short time period, the droid supplying the most power to the circuit "wins". The logic gates are the key to allowing lower-numbered droids to beat higher-numbered droids. There is also a strategy in timing when power is applied to a circuit (as two supplies of power to the same circuit result in the later supplier of power gaining control of the circuit).[5]

In either case, the droid being controlled by the player is destroyed. If the player beats the droid in this mini-game, he takes control of that droid. If not, either the droid is destroyed and the player returned to the game as just the Influence Device (if he was previously controlling a different droid), or the player is killed, ending the game, if he was not already controlling another droid before the takeover attempt.

While in control of another droid, the player effectively acts as that droid, meaning the player has access to that droid's maneuverability, armor, weapons and "power supplies" (used during the droid-control mini-game). If the droid has weapons, the player can destroy other droids simply by shooting them, instead of taking them over (though higher-numbered droids can require several shots to destroy, and might actually fire back). The player only has control of a droid for a limited amount of time (which is inversely proportional to the droid's number). If that time elapses, the controlled droid is destroyed and the player reverts to the Influence Device (001).

The spaceship has several decks, and each deck can have several rooms. Doors and elevators connect the rooms and the decks. Many rooms have computer terminals that provide access to maps of the current deck and the entire ship as well as droid information. Each droid can access information about itself and all lower-numbered droids (this access is available to the player based on the droid being controlled).[6]

Goals and challenges

As well as achieving a high score, Paradroid players also see certain achievements as worthy. Clearing one or more ships entirely of robots is one such goal. Another is a successful transfer from the 001 Influence Device to the unstable 999 droid. Despite the instructions referring to a finite fleet, the Commodore 64 game never ends. When you clear the eighth ship called "Itsnotardenuff", you're just replaced back on the ship, with higher-ranking droids on each deck.[6]

History

Development

During the development of the original game, Andrew Braybrook held a diary that was published in Zzap!64 magazine where he stated:

<templatestyles src="Template:Blockquote/styles.css" />

The thing you actually play with are robots shown from above. There's going to be lots of them. If you want to know more about a particular robot what you do is log-on to a computer terminal. From there you can sift through all the robots and get large side view pictures and you can select things to get more information. I've been working hard on it for about four weeks, but I was working on utilities - programs to help make the finished game - for a couple of weeks before that. I always like to do the character set first because it buys time while you're thinking about the rest of it. It's probably the easiest thing that you can do.

It's not really an arcade adventure - it leans more towards arcade. Gribbly's I wanted to be a non-violent game. All of the zapping and violence that I couldn't get into Gribbly's will be going into this one. Last week we designed the game's 20-deck space-ship, but I'd like to actually build one just to make sure it all works - all the lift shafts tie up and the decks fit together. Maybe I'll try using Lego. Dunno, it might work.

So far I've got a little robot skating about inside a test deck plan. You can log onto a console, select an option, make an enquiry on the test robot and get a big picture of it. The piccie uses all eight sprites combined (the maximum available on the 64 at any one time). Despite being a view from above, I intend you won't be able to see anything behind a wall. You'll have to go into a room to actually explore it.[7]

The game was influenced by several different computer games and movies. Author Andrew Braybrook said in a Retro Gamer interview that the droid-swapping idea came from an arcade game, Front Line, where you could enter a tank and had to leave it when it got hit.[8] In another Retro Gamer feature, Braybrook also stated that the cover of the Black Sabbath album Technical Ecstasy influenced him, where two droids "interfacing" can be observed, along with the corridors of the movie Aliens. Development started right after Braybrook finished his previous game Gribbly's Day Out and even shared some code with Gribbly's.[6] Later when Braybrook was working on Morpheus he did another diary for Zzap!64 where he revealed that the then recently released Competition Edition of Paradroid was 50% faster than the original.[9] In the same series he revealed that they had redone the Paradroid graphics in the new (Morpheus) style,[10] which was later released as Heavy Metal Paradroid. Andrew Braybrook did another diary during the development of Paradroid 90 for Amiga Action.[1]

Reception
Review scores
Publication Score
CVG 9/10 [11]
Zzap!64 97%[5]
Amiga Format 88%[12]
Awards
Publication Award
Zzap!64 Gold Medal
C+VG Blitz Game [11]
C+VG C+VG Hit [13]

Versions

  • 1985 - Paradroid
  • 1986 - Paradroid Competition Edition - Released as a double pack at Christmas with Uridium+,[14] plays faster than the original, mainly due to scroll code enhancements[9]
  • 1987 - Heavy Metal Paradroid - Paradroid with Morpheus style graphics.[10] (Budget Release in 1989)[15]
  • 1990 - Paradroid 90 (Commodore Amiga, Atari ST)
  • 1993 - Paradroid 2000 (Acorn Archimedes)[16]

Reception

The game has been heralded as one of the best ever original games to appear on the Commodore 64, as can be seen when the readers of Retro Gamer selected it as the best game ever on the platform:

<templatestyles src="Template:Blockquote/styles.css" />

Andrew Braybrook's Paradroid is a masterpiece, there's no other way to describe its sheer brilliance.[17]

Also in a 2002 Zzap!64 tribute publication, Paradroid via a community vote was ranked the best C64 game ever with the comment "There is something about Paradroid that sets it apart from other C64 games.". [18]

When it originally came out it received 97 out of 100 in the Zzap!64 November 1985 issue with the comment "THE classic shoot em up"[5] and receiving a "Gold Medal" where 98% is the highest score ever given in the magazine.[19] And again 97 out of 100 with the remark "A game no C64 gamer should be without", in 1989 for the re-issued "Heavy Metal" Edition.[15] In November 1988 it was selected the second best Shoot 'em up on the C64[20] and in December the same year it was selected the third best game ever by Zzap!64 magazine.[21]

Paradroid 90 received "C+VG Hit" with a score of 93% in Computer and Video Games[13] and was ranked the 22nd best game of all time by Amiga Power.[22]

Other clones and games inspired by Paradroid

Several free software clones of the game have been published:

    • Paradroid for Windows and Linux, current version 1.3 (March 2004),[23] which garnered favourable reviews at The Home of the Underdogs.[24]
    • Freedroid Classic for Windows, Linux, OS X and Sharp Zaurus, current version 1.0.2 (2004)[25]
    • Project Paradroid for Windows, current version 2 (2006)[26]
    • Paradroid Redux is a reimplementation of the original Commodore 64 code, fixing bugs and adding features.[27]
  • Freedroid RPG is a Diablo-style role-playing video game based on Freedroid Classic, inheriting only the main theme of fighting hostile robots, the takeover-game, and the robot models.[28]

Quazatron

Andrew Braybrook's Graftgold partner, Steve Turner, wrote a version of Paradroid for the ZX Spectrum called Quazatron in 1986, also published by Hewson. Gameplay was similar but on an isometric playing field, and based in cities rather than spacecraft.

See also

References

  1. 1.0 1.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. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. 5.0 5.1 5.2 5.3 Lua error in package.lua at line 80: module 'strict' not found. Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.0 6.1 6.2 Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. 9.0 9.1 Mental Procreation part 2 - Web Archive Lua error in package.lua at line 80: module 'strict' not found.
  10. 10.0 10.1 Mental Procreation part 1 - Web Archive from Lua error in package.lua at line 80: module 'strict' not found.
  11. 11.0 11.1 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. Lua error in package.lua at line 80: module 'strict' not found.
  13. 13.0 13.1 Lua error in package.lua at line 80: module 'strict' not found. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found. Lua error in package.lua at line 80: module 'strict' not found.
  15. 15.0 15.1 Lua error in package.lua at line 80: module 'strict' not found. Lua error in package.lua at line 80: module 'strict' not found.
  16. 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. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Paradroid for Linux and Windows version 1.3 (March 2004) at SourceForge
  24. Home of the Underdogs – SDL Paradroid review
  25. Freedroid Classic information at the bottom of the page
  26. Project Paradroid Project home page
  27. Paradroid Redux Project home page
  28. Freedroid RPG project home page

External links