The Unofficial Quake II FAQ
Post-Release v1.7 - MINOR revision



Last Updated: February 25th, 1998 GMT
Quake Quote: "Mess with me and your problems are all over... all over the floor."

© 1997, 1998 Richard "Sat" Connery. All rights reserved.



This document is provided "as is" without any guarantees or warranty. Although the author has attempted to find and correct any errors or mistakes he, and everyone who contributed to it, are not responsible for any damage or losses of any kind caused by the use or misuse of information in this FAQ. The author is under no obligation to provide service, corrections, or upgrades to this FAQ.



The following is legal information and refers to all the information in this document. This information pertains to all use of the FAQ worldwide. All specific names included in the package are registered trademarks and are hereby acknowledged. Any other trademarks not mentioned in the FAQ are still hypothetically acknowledged.

As long as you comply with the above rules you may do whatever you want with this document.



Sections added "+" or updated "u" since the last version of the FAQ.

Chapter I: Introduction

  1.     Foreword u
  2.     Submissions
  3.     Getting the FAQ u
  4.     Credits & Acknowledgments u
  5.     History u
  6.     About the FAQ Author u
  7.     About Who Made Quake II

Chapter II: Basic Information

  1.     What is Quake II?
  2.     System requirements
  3.     Windows 95 / NT
  4.     MMX
  5.     OpenGL
  6.     Consoles & other OSs
  7.     Getting Quake II u
  8.     Demos

Chapter III: In Depth Information

  1.     3D Engine
  2.     Levels
  3.     Textures
  4.     Models
  5.     Soundtracks & Effects
  6.     Demos & Cutscenes
  7.     Artificial Intelligence
  8.     DLL

Chapter IV: Gameplay

  1.     Storyline
  2.     Your Character
  3.     Weapons
  4.     Inventory
  5.     Enemies
  6.     Units u
  7.     Cheats

Chapter V: Multiplayer games

  1.     Modem-to-Modem & Serial
  2.     LAN / Internet
  3.     Lag
  4.     Deathmatch
  5.     Cooperative
  6.     CTF

Chapter VI: Editing Quake II

  1.     Levels
  2.     Textures
  3.     Models
  4.     PAKs
  5.     Cinematics
  6.     Code

Chapter VII: Quake II Third Party

  1.     Levels
  2.     Addons
  3.     TC/PCs
  4.     Mission Pack #1

Chapter VIII: Frequently Asked Questions


Chapter I: Introduction

    1.    Foreword

Welcome to The Unofficial Quake II FAQ!

The FAQ is maintained by Richard "Sat" Connery, the maintainer of The Official Hexen II FAQ and The Unofficial Trinity FAQ. This is intended to be a compilation of all the information floating around the various websites about the new game by id Software: Quake II. It's the place where all the features, news bits, scoops fall back to. The ultimate source of general information about Quake II. Please note that all text in gray are quotations and that actual content of the quotes may be outdated.

I, and everyone who has contributed so far, hope you enjoy reading it and that this FAQ ultimately answers all your questions about the game. The FAQ is now on post game versions (v1.x format). The latest Quake II version is, at this time of writing, v3.13. Darryl "Nite" Ashton is the creator of the FAQ but handed it over to Ismail "Slipgate" Saeed which, in turn, has handed over the FAQ to me.


    2.    Submissions

If you wish to submit something to the FAQ (i.e. questions, comments or articles) then mail me and if your submission is accepted and incorporated into the FAQ you will be credited under section I.4. Please be advised each and every submission becomes the property of the author. If you wish to ask something then do but please keep it FAQ related. If you don't get a reply within two days then mail me again. Keep trying, as I do my best to answer everyone.


    3.    Getting the FAQ

The latest version of The Unofficial Quake II FAQ will always be uploaded to PlanetQuake first. You can get it as a file here. If you wish to mirror/store the latest version of the FAQ then please mail me with an elaborate request. If you're accepted your URL will go to the FAQ mirror list: - Maintained by Richard Connery [Sat] - Maintained by Bini Parkhurst [Blitz] - Maintained by Russell Cavell [Dr. Death] - Maintained by Jozsef Sasvari [angelday]


    4.    Credits & Acknowledgments

The following people have made this FAQ a much better one than it would be otherwise:

My sincere thanks to all of these and to everyone who reads the FAQ.


    5.    History

The versions of the FAQ with the changes made in each are sorted below. The FAQ was started on 1997.

Anniversary Edition
Two years ago today, id Software was releasing Qtest, the first look into what Quake was shaping up to be. It was strictly for multiplayer testing and although LAN was the prime target id received a lot of feedback concerning Internet play. Qtest is as crude as Quake gets, you neither had the axe nor the shaft (lightning gun) and the weapon models were very, very basic. There were some monsters but they changed considerably before the game shipped. Some even lacked skin. You had three levels which, after some polishing, became DM1, DM2 and DM3. The Rocket Launcher from Doom quickly rose to the status of "prime-weapon".

The lighting was very dramatic, especially in DM2 and the sky which is now obsolete was then a sight to behold. Some ppl even got sick watching it. There were no .MIDs and all you listened was crying, shouting, rockets blasting away and the ocasional lava dipping sound. The 3D world really pushed the mouse as the number one throwing the keyboard into the oblivious void (to some extent at least). The death animations were delightfull, and even the lack of inventory items (like in DukeMatch) didn't seem to care. Real DM was back and we longed for it ever since our Doom II days begun to fade.

Two years have passed and Quake still has that special glow of "true DM" even with Quake II out the door for almost three months. Quake failed single player wise but in DM it is a worthy sucessor to Doom and Doom II and it all begun two years ago today...


    6.    About the FAQ Author

I go by Richard "Sat" Connery and I live in Miramar, Portugal, Europe, Earth, Solar System, Milky Way, ad infinitum... My house is just three hundred yards from the sea. It really is great to wake up, go to the balcony and watch the waves caress the burning sand... :-)

I like to think of myself as a level designer. I've started with Doom back in the good 'ol days but I never actually released any of my work since I didn't think it was good enough. In January 1997 I was hired by Dark Designs, inc. a company which will release its first game, using the Quake II engine, in late 1998. I'm in charge of game and level design as well as doubling as the company's biz guy.

You can find me on IRC occasionally, on Undernet #3dgamers but I rather go out and live a little. You should too. If you'd like to get in touch with me you can mail me at For more personal matters you can catch me on ICQ. On the servers I go by UberFragMëister, a tribute to the old Doom days of true Deathmatch.

Past work include:

  1. Kraan, a world designed for Unreal
  2. Hexenworld along with Phoebus and Bakshra
  3. UAC Gateway, the first database of links exclusively dedicated to Quake II
  4. Serpent's Realm, the first database of links exclusively dedicated to Hexen II
  5. The Mailbag


    7.    About Who Made Quake II


John Carmack
John Cash
Brian Hook

Adrian Carmack
Kevin Cloud
Paul Steed

Tim Willits
American McGee
Christian Antkow
Paul Jaquays
Brandon James

Todd Hollenshead
Barrett (Bear) Alexander
Donna Jackson


Ending Cinematic by Blur Studio - Venice, California
Environment models for Introduction Cinematic by Karl Dolgener
Assistance with environment design by Cliff Iwai

Sound Design by Soundelux Media Labs. Music Composed and Produced by Soundelux Media Labs.
Level Music by Sonic Mayhem
"Quake II Theme Song" © 1997 Rob Zombie. All Rights Reserved.
"Climb" by Jer Sypult
Voice of computers by Carly Staehlin-Taylor

Producer: Marty Stratton
Marketing Product Manager: Henk Hartong
QA Project Leads: John Tam, Doug Jacobs, Tim Vanlaw
Quality Assurance Testers: Steve Rosenthal, Mike Spann, Winnie Lee,
Steve Elwell, Derek Johnstone, Igor Krinitskiy, Ian Stevens, David
Baker, Chad Bordwell
Manual Written by: Marc Saltzman
Thanks: Mitch Lasky, Sandi Isaacs, Michael Rivera



Chapter II: Basic Information

    1.    What is Quake II?

Quake II is a first-person 3D game developed by id Software. It's the second game from id Software to use a real 3D engine. Based on WinQuake, a native Win32 application, Quake II runs on either Windows 95 or Windows NT 4.0 or later in its first release. id Software is the company responsible for creating the first-person shooter perspective genre when they released Wolfenstein 3D and then Spear of Destiny, the sequel to Wolf3D. Then it was well underway to release the game that would make the PC a games platform to be reckoned with: Doom, arguably one of the top 5 games of all time, if not the first.

Doom 2, Ultimate Doom and Final Doom followed shortly. While every competing company was trying to beat Doom for its sheer gameplay brilliance, id started development on "the next big thing": Quake. Using a real 3D engine, Quake surpassed everything in terms of internet community known to date and now id did it all again. Quake II, much more than a mere sequel, is totally different from Quake fixing the incoherence present in that game plus adding tons of new effects which were impossible to do in Quake. "There are no satanic references in Quake II but it still rules the cosmos" and you better believe it!

The war engines are in place, the mines buried beneath the earth, and already the towers tremble; the ladders stand at the gates, the grappling hooks cleave to the walls and fire runs through the roof tops.

With the gleaming swords and the menacing faces of his enemies around him, and thinking utter ruin is upon him, why should he not quake and mourn?

Francesco Petrarca, in Secretum, 1342 A.D.


What is beyond Quake II? Check section VII.4 for information about the mission pack.

Brian Hook: There is talk of a mission pack, there will be interim "point releases" that will fix bugs and maybe put in some new features for multiplayer, and, of course, there is Trinity.


    2.    System Requirements

Since Quake II has new effects, more detailed textures, levels and models than Quake it also requires a more high-spec machine. Here are the official system requirements:

Minimum Install Additional Requirements (Play from CD-ROM)

Normal Install Additional Requirements (Play from Hard Disk)

Maximum Install Additional Requirements (Play from Hard Disk)

GLQuake II Additional Requirements

A genuine Intel Pentium processor, fast video card, 32 MB RAM, an OpenGL compatible card and a decent sound card will give you much better gameplay. Don't go for Cyrix chips. I'm not saying they're bad it's just that since Quake II uses Quake's engine the same kind of sluggish performance you get with a Cyrix and Quake is back in Quake II ten fold. AMD K6 chips have good FPU performance, so if you really can't afford an Intel, the K6 chips are excellent Intel alternatives (especially if you use software that uses the FPU, like the Quake engine). The Pentium Pro's are not recommended since the Pentium II (Pentium Pro evolution with MMX) is already out.

Concerning sound cards, unless your card is recognised by DirectX 5.0 you won't be running at full performance. Also, controllers like joysticks and so on seem to have a problem with Quake II. Force Feedback controllers are not supported. Such a big memory requirement is not a surprise since Quake needed 16 MB to run under Windows 95 but because you could run it in DOS with only 8 MB no one really complained. Quake II ONLY runs in Windows 95 / NT so it was bound to need much more than Quake. Also, all the new effects and file formats require a lot more memory.

John Carmack: Cyrix has a new processor that is significantly faster at single precision floating point calculations if you don't do any double precision calculations anywhere. Quake had always kept its timebase as a double precision seconds value, but I agreed to change it over to an integer millisecond timer to allow the global setting of single precision mode.

I asked John whether Quake II final uses any double precision calculation. Here's his reply:

John Carmack: The first demo still included some double precision calculations. The released Quake2 did not do any double precision calculations, and it set the control word to single precision, but we found out later that every LoadLibrary() that we did reset the control word. The next release of Quake2 makes sure that it stays in single precision mode all the time.

Running Quake II 3.10 under Linux, Only 2.9 MB are really neccessary (just the binaries). You can push it to below 2.6 MB if I run Quake II in just one video mode. Quake II supports the following video modes if available in both windowed or fullscreen rendering:

  1. 320x240
  2. 400x300
  3. 512x384
  4. 640x480
  5. 800x600
  6. 960x720
  7. 1024x768
  8. 1152x864
  9. 1280x960
  10. 1600x1200


    3.    Windows 95 / NT

Yeah, I know: why Windows and not plain, old and fast DOS? Well, it's easier to develop games since you don't have to worry about devices like mice, sound cards, modems, LAN card setups, video cards, 3D acceleration cards; the list is endless. Trust me. It's BETTER this way. The OS handles things automatically and the programmers can concentrate on the game itself instead of writing emulators and drivers like in the DOS days. Quake II doesn't use Direct3D but OpenGL instead, which is a set of drivers 3D card developers are really pushing forward, some even say it has surpassed Direct3D, at least in the first-person perspective genre. The bottom line is: install either Windows 95 or NT 4.0 and you can be sure if the OS detects and correctly configures your device Quake II will have no problems using it and that can only be a good thing.

Brian Hook: We will support DirectX if it's available, e.g. DSound, DInput, and DDraw (NOT Direct3D), but we won't require it. If DInput isn't available we'll use standard Windows messaging. If DSound isn't available we'll use WaveOut. If DDRAW isn't available we'll use GDI with DIB sections. DDRAW will be required if you want fullscreen software rendering support though. In a nutshell -- DirectX is supported, but not required.


    4.    MMX

Quake II does NOT use Intel's latest MultiMedia eXtensions. Unreal will though as well as other upcoming games. Even then, it's wise to buy a MMX chip if you're already thinking of upgrading your machine.

The Quake engine uses the Intel FPU extensively, and also uses a native feature of the Intel FPU called Parallel FPU lines. This allows simultaneous integer and FPU calculations and Quake uses these to do lots of calculations at the same time. The problem is that the MMX instructions use the Parallel FPU lines for calculation, and if MMX were supported in Quake, Quake and the MMX would be fighting over the usage of the Parallel FPU lines. This isn't the problem for most programs because Quake is just about the first major program that even uses Parallel FPU lines in the first place, so other programs don't have this conflict.

Carmack reported that a MMX version of Quake he had in alpha stages would run, at best, the same speed in 16-bit colour as an 8-bit colour version does on a non-MMX Pentium chip of the same clock speed. Carmack says this increase in colour depth only isn't worth the development time and money and has decided not to support MMX with the Quake engine in its current form.


    5.    OpenGL

Quake II runs in one of two modes: Software or OpenGL rendering. At this moment, you can choose between four rendering options: Software, Default OpenGL, 3DFX OpenGL and PowerVR2 OpenGL. Verite is currently not 100% supported but Rendition is bringing out beta drivers of their OpenGL implementation. Keep checking their site the news pages for news versions of Verite drivers. 3DFX was the first chip technology to make drivers for it and many more are writing their own too. Although Quake didn't have native support for OpenGL, 3DFX wrote a OpenGL mini-driver for Quake. (both VQuake and GLQuake are available as a free download from several websites) but Quake II uses a much wider and expandable format: OpenGL and the term "GLQuake II" now refers to hardware rendering through OpenGL drivers.

Readme file: OpenGL is a low-level API (Application Programming Interface) that works with a compatible 3D video chipset to render top quality 3D graphics. Some of the features you will see while using OpenGL, and a compatible 3D hardware video accelerator, are 16-bit graphics, colored lighting, improved translucency and increased game speed.

If you don't have any OpenGL compatible card then the game will render through software by default. This is still great and MUCH better than Quake ever was.

Brian Hook: Well, you simply can't do as much with software rendering as you can with GL. Obviously with GL we can support hardware accelerators, which means high quality colored lighting and nice looking transparencies. You'll also get higher resolution and better performance. So yes, in a way we're "biased" towards GL, only because it allows us to do more stuff. We definitely strive to make the software rendering engine as good, but we run into limitations of the 8-bit palette all the time.

Brian Hook on the list of cards capable of running GLQuake II:

Brian Hook: So far we run on 3Dfx (Win95 and NT), PowerVR PCX2 (Win95), Permedia2 (Win95 and NT), Rendition V1000 and V2200 (Win95 and NT), NVidia RIVA128 (Win95(soon) and NT), Voodoo Rush (Win95 and NT) and a few others that haven't been announced yet. The PowerVR doesn't implement colored lighting because...well, someone there decided that the particular blending mode we need for colored lighting wasn't worth implementing in their chip.

3D cards running with the PowerVR2 chipset (like the Matrox 3D) do have coloured lighting. The lowest resolution is 320x240 and not 320x200; this old resolution has a poor and ugly ratio thus id has replaced it with 320x240 which is half 640x480, considered a "perfect" resolution. Extra high resolutions were added like 960x720 to provide speedy computers, yet not speedy enough for 1024x768, a chance to take advantage of the extra horsepower.

Brian Hook: It's our opinion that the Voodoo is likely going to be the best board for Quake2 when we release. As for "Voodoo 2" and other non-existent accelerators - we'll support anything with a working OpenGL driver. In terms of practical differences, the only difference between a Voodoo and a Voodoo2 for us is that the Voodoo2 is going to be much faster.

Regarding Rendition and Verite, John "NiNe" Mury (thanks man) reporting:

There is a GL miniport available at Rendition's web site ( Zanshin used it for his Quake2 /Rendition review. This miniport is for V2100 chips (Diamond Stealth 2) and V2200 chips (upcoming Hercules Thriller 3D, Jazz Outlaw 3D). With the v1000gl.uc (I think that's the name), the V1000 chips can also run GLQuake (Sierra Screamin' 3D, Canopus Total 3D, etc.) if the Rendition Win95 reference drivers are used.

There is a native V1000 renderer ( which has a sharper image than OpenGL (because it supports edge anti-aliasing) but does not do colored-lighting. This also works for V2x00 chips.

There is a native V2x00 renderer ( that I pulled from Zanshin's site. This renderer supports coloured lighting. Zanshin claims it has better image quality that GLQuake2 on a Voodoo and can even be faster. It doesn't work on V1000 chips, however.

For more VQuake and VQuake II information check NiNe's Rendition Quake Workshop.


    6.    Consoles & other OSs

Quake II is available as a supported product for Windows 95 and NT 4.0. A Linux port has been released, however, and can be found here. Brian Hook mentioned in his .plan that they will be releasing executables for several other OSs like Linux, SGI, Alpha and other workstations. There are no plans for a MacQuake II just yet though; we'll have to see if MacQuake is well received. Only then a Mac port will be discussed.

It should be noted that John Carmack has mentioned numerous times in interviews that he will be porting Quake II to Rhapsody shortly after the commercial release of Quake II. Rhapsody is Apple' next-generation OS (already seeded to developers) that runs on Mac hardware as well as Intel hardware. In fact, Carmack had Quake up and running on Rhapsody at one point.

Brian Hook: We plan on porting to Linux, DEC Alpha WinNT (done today), Rhapsody, and SGI Irix. I'm sure we'll port to other stuff later as time permits.

Quake is being developed for the Saturn and N64. Again, like the Mac, only if these versions are well accepted a Quake II port will be considered at all. At the moment, the N64 version (which includes a 2 player DM mode) is as good (if not a little better) than GLQuake; the Saturn version however has a slight colour depth problem which fools into thinking you can only get 128 colours. This is understandable considering the Saturn's spec relatively to the N64 or the 3D accelerated PC thus a N64 port of Quake II is more likely than one for the Saturn.


    7.    Getting Quake II

You can buy Quake II from any major software retailer or order it from Activision which publishes Quake II. The original Quake II retail version is 3.05 but activision will start producing Quake II CDs which come with v3.13. Here's the version history. Unless stated otherwise each can patch any of the previous versions.

There was a v3.11 which was a specific patch for Alpha workstations but it was not released for Windows 95 / NT versions of Quake II. Keep checking this page to download the latest patches. There's also two other official Quake II components you can download: DM levels and CTF:

It's highly recommended you download the Point Release as it will allow you to run CTF and have better performance while playing with the 64-player levels. Here is a description of all the changes from v3.10 to v3.13:

  1. Fixed qhost support code. We were using the wrong threading API.
  2. No longer report WSAEADDRNOTAVAIL on IP broadcasts since some PPP drivers will fail them with this error.
  3. Added cvars gl_3dfx_no_gamma, gl_particle_min_size, gl_particle_max_size, gl_particle_size, gl_particle_att_a, gl_particle_att_b, gl_particle_att_c
  4. Fixed a bug in Sys_Milliseconds that would cause what appeared to be a system freeze. It was really just frozen for 65 seconds.
  5. Fixed a bug in Sys_ScanForCD due to NT and Win95 interpreting the parameters to GetDriveType differently.
  6. Added Win95 specific screen saver detecion code
  7. Changed the interface on the video menu a bit
  8. Fixed a crash in ref_soft that happened when firing weapons under certain circumstances. For example, if you had r_drawentities set to 0.
  9. Fixed a bug that caused clients to not be able connect sometimes when the server was changing levels.
  10. Reimplemented macro expansion where appropriate
  11. Fixed console redirection for rcon
  12. Moved chat functionality in to the game dll
  13. Added coop play including savegame support. This brought about a major rework of the savegame code.
  14. Added code to make sure coop and deathmatch always have consistant values
  15. Moved player model sounds in to the same directory as everything else so the models, sounds, and icons are all in one place now. The male sounds are used as a fallback if a model has no sounds of its own.
  16. Added glquake type shadows. There are definitely issues with them, but some people really like it.
  17. Removed duplicate copies of the vertex normals table.
  18. Latched cvars are now changed immediatly if a server is not active.
  19. The cvar game is now latched instead of write protected. We're treating it much like quakewold did to automatically set it when you connect to a CTF server. When it does change video and sound systems are restarted to flush the caches. It's fairly fast since you aren't in a game at the time.
  20. Fixed so it will check for pak0 through pak9 instead of starting at pak0 and stopping when it gets a miss. This was keeping people who had done a minimum install from seeing the pak1 for the DM levels.
  21. Fixed an out of band message overflow crash.
  22. Commented out printing of "using previous origin"
  23. Game API changes required bumping version to 3.
  24. Network protocol changes required bumping version to 31.
  25. Added client side support for various mission pack #1 and CTF effects
  26. Added ability for game dll to temporarily disable client prediction; used for grappling hook
  27. Reworked sound code for model specific sound support.
  28. Made key binding check on inventory screen case insensitive
  29. Changed setenv command to let you see an environment variables value without changing it
  30. Added code to clear all pallete effects when disconnected
  31. Added fixedtime to the cheatvars list
  32. Rewrote client side code for model and skin parsing so CTF can enforce team skins. No more cross dressers!
  33. Added CTF scoreboard
  34. Added an offset to client beams to make grapple work better
  35. Added a slew of gross hacks to fix problems in various maps, mostly dealing with coop issues
  36. Added fixed FOV support for those that consider it cheating (off by default)
  37. Added quad dropping (like in QuakeWorld) to turn them into targets
  38. Fixed monsters in coop ignoring the last player
  39. Fixed mask for monsters checking for a clear shot to have windows block
  40. Made sure everything in hard is in hard+ skill
  41. Fixed insane guys getting mad at the player
  42. Fixed team determination code
  43. Added invnextw, invprevw, invnextp, and invprevp to allow cycling through only weapins or powerups
  44. Fixed "give ammo #" to be absolute instead of addative
  45. Fixed "give <item>" to work as if it has just been picked it up instead of just stuffing it in the inventory
  46. Enabled dropping for single player and coop
  47. Added weaplast command to switch back to your previous weapon
  48. Fixed it so you can only suicide once every 5 seconds
  49. Added a "players" command that lists all the players in the game in the console
  50. Added a "score" command to bring up the scoreboard. This was needed since in coop you have both help and a score. DM still shows the scores if you do help.
  51. Limited max negative health to prevent wrapping and other printout oddities
  52. Changed monster pain reaction code for coop so they don't cycle among multiple players shooting at them
  53. Fixed a bug that let monsters run around with a ducked bounding box
  54. Fixed teamplay scoring
  55. Fixed a crash with teamed rotating doors
  56. Fixed inadvertant weapon switch when picking up ammo
  57. Resassigned sound channels for power armor sounds so they don't get lost
  58. Preserved power armor state across levels
  59. Fixed picking up power armor when you had active power armor was deactivating it
  60. Reworked a bunch of code related to keys for coop
  61. Replaced some hard numbers with defines so mod authors know what they are for
  62. Fixed bad frame message; it was trying to animate dead bodies
  63. Fixed monster combat points checking self instead of other when trying to not allow swimming and flying monsters from being held
  64. Removed test code and variables that were unused and just taking up space
  65. Stopped dead monsters from screaming in pain
  66. Fixed a bug in testentity position that was not using the entities clip mask. This was allowing monsters to pass through objects sometimes.
  67. Added password so you can have a private server again
  68. Added a server command interface; see the game dll source for details
  69. Fixed help computer for coop
  70. Fixed target_changelevel allowing being activated when the player is dead in single player
  71. Fixed target_changelevel was checking other instead of activator in DM
  72. Fixed switched lasers that had been off were not causing damage
  73. Fixed crash in the body que code
  74. Fixed some sounds that were sent to PVS instead of PHS
  75. Fixed monsters were becoming non-solid at the wrong time
  76. Fixed monsters don't go into pain in skill 3.
  77. Fixed soldiers were playing wrong pain sounds
  78. Added death messages (obituaries). This was done the right way; it always knows what killed you (directly killed you). There are even some fun sub-cases tracked like a direct rocket hit vs a near miss. I'm tracking 32 distinct causes of death right now as well as if it was due to friendly fire. The messages are gender correct too. I didn't do anything to modify them for powerups.
  79. Made dead players gibbable
  80. Added a hook in the game dll for IP banning.
  81. cleaned up comments to help mod authors know what's going on a little better
  82. Fixed help computer to show when skill is 3
  83. Stopped armor number from flashing when in god mode or invulnerable
  84. Stopped player playing pain sounds when in god mode or invulnerable
  85. Fixed falling damage so you are no longer saved by steep slopes
  86. Stopped switching to a weapon when you already have one in inventory
  87. Stopped switching to super shotgun or bfg10k when you don't have enough ammo


    8.    Demos

Unlike Quake, there is NO shareware version of Quake II. Instead, id has already released the first of its two demos. This first demo has no multiplayer, rushed sound effects, no soundtrack (obviously), incredibly rough AI and has some frequent bugs. On the other hand, it has three levels linked into a unit, six weapons (of a total of ten), all four rendering modes, half of the enemies and artifacts. This was a compatibility test to receive technical feedback instead of gameplay comments. Still, the three level demo is incredibly addictive and shows the single player gameplay of the final game.

Teleport to id Software...

The second demo should include everything the full does with the exception of content (levels, textures, models, etc.)



Chapter III: In Depth Information

    1.    3D Engine

Everything (well, almost) in quake is represented in three axis: x,y and z. The z axis was lacking in Doom, Duke Nukem 3D and Hexen for instance. Unlike these games, Quake's world is the real thing and not an interpretation. For instance, if you want a cube you give the editor the eight corners each with its own x,y,z values and the engine - through QBSP - builds it while in Doom and others you had to do tricks with sectors and linedefs to achieve the same effect. It was a gruesome way of doing things but it was great at that time. Duke Nukem attempted to fake z movement and sector placing and it worked pretty well until Quake arrived.

The bottom line is: You can build whatever structure you want in Quake engine games without worrying if the engine is capable of doing it. The engine IS capable of building anything. You could say that Quake can't have true spheres; yes, that's right because Quake's engine is not based on raytracing. But if you build a sphere with more than 128 faces on each of the three axis you can fool the human brain at the right scale. This, of course, poses some incredible pulls on the processor so it's not really feasible.

Here are some of the new highlights of Quake II's engine:

Let me arrange all these topics into these categories:


    2.    Levels

Rotating brushes were present on id's Quake: Mission Pack #1: Scourge of the Armagon yet in a crude way. Hexen II received John Carmack's new Quake II rotation code which is much simpler for the level designers and much more solid. Transparent and translucent brushes are also present in Hexen II. Quake II is even better though as the code has been optimised since then. With this feature you can have stained glass like you did in Duke Nukem 3D.

Brian Hook: Stipple alpha is a method of implementing transparency that is very fast but also pretty ugly. Instead of making individual pixels transparent we just draw every other pixel (i.e. "screendoor" transparency).

You are able to see through water in both software and OpenGL just like in Hexen II. Lighting is standard white in software and colour enabled in OpenGL rendering. Radiosity makes lighting a level a bit differently. Although you can still have light entities in mid space, light is now originated by textures making it much more realistic. Also, now the light beams reflect off the surfaces of the world creating a more life-like scenario. Dynamic shadowing is used in weapon firing and several effects like picking up a powerup. What is news though is that instead of increasing the light intensity (positive) you can now decrease it (negative). Check the Weapons section for more details. Unfortunately, Quake II still has the light from explosions going through walls.

Brian Hook: The second thing I want to discuss is "lights shining through walls". I can not BELIEVE the number of people who simply think we're lazy or too stupid to get this happening. *fume* The problem is this -- yes, we can backface cull the lights and not show them on opposite sides of a wall, however backface culling will NOT prevent lights from splashing across a floor. In those instances the lights wouldn't poke through the wall, but it would flood under the wall and show up on the floor, which actually looks WORSE. There have been some efforts to reduce the "light through walls" phenomena, but right now it's essentially a part of the engine that would be very difficult to fix.

Screenshots in GL accelerated mode will be TGA format and screenshots in standard 256 color mode will be PCX format. Momentum will work the same as in Quake (automatic acceleration, no coefficient of friction). Quake II will use DirectX (except Direct3D) if it is present. The DLL source will be released but that is the only documentation id will provide to it, people can document it themselves.

Levels are grouped in Units which are the equivalent of hubs on Hexen II. Every level in a unit is connected to the rest of the unit's levels and changes you make in one level might affect the next level's behaviour and so on. Also, you have to backtrack a lot between levels, solving puzzles, destroying machinery and killing bad guys. There are 39 levels and more are planned for the point release or the addon pack.

Quake couldn't stand outdoor environments because of the sky engine which broke the sky brush into several little ones making an abode which would simulate a sphere. This presented tremendous pulls on the CPU cycles thus Quake was a dungeon type game. With Quake II, id has returned to Doom's type sky where you can see the actual horizon with mountains, clouds, buildings. But they also worked on it making it semi-interactive making believe it actual changes depending where you stand on the level, whenever direction you look (including up and down) the visage is different. Unfortunately the sky can't be animated, here's why:

Paul Steed: I've spoken to John about this and the memory hit would be tremendous. Trinity hopefully will feature this.

Still, the sky can rotate by any axis at any speed. Like Quake, the new levels can be 8K (8000) units big in all 3 dimensions. Although this hasn't changed from Quake, now this capability is fully used and levels are massive. id has released their utils so you can build your own maps and take advantage of the new effect. Levels are a little bigger than Quake levels but they are tons bigger gameplay wise. Also, you'll need to parse your Quake maps through a converter to play them on Quake II.

While level designing you can now tag any brush face as slippery (i.e. ice), transparent (i.e. clear glass), translucent (i.e. stained glass), flowing (i.e. water animations), damaging and QRAD: reflective and / or self-illuminating. This makes the life easier and requires less coding by the programmers.

Brian Hook: Terrain and walls cannot be dynamically destroyed in the general case, but we do have some effects where we emulate the effect of destroying a particular brush or wall or whatever.

John Cash: For things like doors, plats, etc. a team is a group of entities that move (or don't move) as a unit. That way you can make a set of doors so that if one gets blocked they both stop. A million and one fun uses for that. You can also makes teams of items; very useful for DM. Teamed items work like this: when the map loads one (and only one) of the ietms will be spawned. When somebody picks up that item there is the usual respawn delay time and then one of the items on the team is randomly selected to respawn. For example, you could put a quad and a invulnerability on a team so that they are both on the level but never at the same time. Or you could put 5 RL on a level as a team so that you can't camp on it because you don't know which one will come back next.

To play any home-made levels you need to create a subdirectory in your Quake II folder ("test" for this example). Create a "maps" subdirectory on your "test" subdirectory you created earlier and put the levels there. Start Quake II with the "+set game test" command line parameter (or type "set game test" on the console) to enable the directory. Of course, replace "test" with eachever directory name you have. Type at the console: "map mapname" where mapname is, obviously, the name of the map you wish to play; you don't need to type the .BSP extension.


    3.    Textures

Quake II's BSPs do NOT have the textures inside them. This is a much economic format since it will reduce BSP filesize making downloading levels a welcome activity. Besides, having two levels use the exact same textures and don't take advantage of common grounds to reduce filesize was odd. Thankfully, id has now implemented the new format. The actual textures are separated into several .WALs instead of being grouped into a single .WAD. The actual information is not different though. The textures themselves now have surface and content attributes, meaning they will behave differently in Quake II. You can change a texture's preset attributes at any time.

Brian Hook: We've gone to considerable effort to make the colors in Quake2 more vibrant and less gloomy and dark.


    4.    Models

Models run at a minimum of 10fps, just like Quake; but if you have the number crunching necessary (i.e. a fast computer) extra frames of animation will kick in making the model's movement ultra smoother; this is called linear frame interpolation. Quake's average face count is around 250. Check out Quake II:

Paul Steed: Our models run from 400 to 700 with the bosses around 2000 faces.

Brian Hook: Recursive subdivision rendering has been dropped since we couldn't update it to support the new features we wanted such as transparency. Or, more specifically, updating it wouldn't have been worth the hassle.

Paul Steed: Keep in mind that just because they are in separate pieces, it doesn't change the fact they're just considered a collection of vertices. The bounding box doesn't recognize individual limbs or objects yet within any particular character.

The explosions are now models, unlike in the first demo, although the sprite explosions are still included in the final version.


    5.    Soundtrack & Effects

Quake's soundtrack and sounds were left to Trent Reznor and Nine Inch Nails. Although not exactly a flop, everyone felt it should sound more like NiN instead of background noise. Quake II's soundtrack was handled by Sonic Mayhem (Methods of Destruction fame). They have released three MP3 samples which are playable by Winamp. Go try them. There were early reports of Ozzy Osbourne's contribution as CD tracks and player / environment sounds. Ozzy is romoured to produce a soundtrack but you'll have to buy this second CD.

Brian Hook updated his .plan a few months ago stating that Rob Zombie (lead singer for White Zombie) sent id a really kick ass music track for the intro to the game, and the might be using that for the intro. His contribution is in the final game. Trent Reznor, although rumoured at first, hasn't worked on Quake II. Unlike Hexen II, Quake II only has CD Audio music and not MIDI. The mixing quality has also improved. You can now choose between 22KHz or 11KHz mixing rate. The later will give you less quality but faster framerate. There is an addon patch to let Quake II play .MID files.

John Carmack discussed the possibility of implementing the sound equivalent of Radiosity lighting. But this idea has been scrapped for Quake II. Also, there is no support for 3D sound. Here is the soundtrack information:

  1. Data - Quake II
  2. Operation Overlord
  3. Rage
  4. Kill Ratio
  5. March of the Stroggs
  6. The Underworld
  7. Quad Machine
  8. Big Gun
  9. Descent into Cerberon
  10. Climb
  11. Showdown


    6.    Demos & Cutscenes

Like Quake you're be able to record your performance for posterity. Unlike Quake, however, demos can be recorder both client and server side. Demos can now be recorded from any point during a game not necessarily from the start. There are no demo based cutscenes included with the game. There are, however, cutscenes for the intro, the end and between units.

Paul Steed: I'm using 3ds4, 3dsMax, Photoshop and animatorPro for the cinematics in Q2. We will probably have some scripted animations using the quake engine ala the Rangers stuff.

Ganslick wrote to Paul Steed which in turn pasted into his .plan instructions on how to make your own cutscenes:

Ganslick: Render scene to individual PCX's (8-bit), all named *0000.pcx Copy the files to /bin_nt/video/[dir with same name as *] Place an optional .WAV file, also named the same as the PCX's (minus the 0000) in the bin_nt/video dir. Create a text file (with .QDT extension) and place the following info in it

$video pcx-file-name (minus the 0000) 4

eg, $video testing 4 would process the files named testingxxxx.pcx and the /video/testing directory, and process the optional WAV file, named testing.wav place QDT file in /bin_nt, and type QDATA testing.qdt (or whatever your filename is)

I just got word from John Carmack that Quake II supports "serverrecord" which generates a HUGE demo file of all entities during a recording session, specifically to allow some very nice post-production. This is a massive improvement over the old demo technology.


    7.    Artificial Intelligence

The enemies are cleverer than Quake's ones but not too difficult so it doesn't scare newbies, or inexperienced players, away. Monsters duck rockets and other projectiles, roam around certain parts of the level, are affected by visibility (shadowy areas) like a real human instead of being omniscient. At higher difficulty settings monsters stalk the player without getting lost in the level. They are not reaper-kind intelligent but clever nonetheless.


    8.    DLL

No more QuakeC, pseudo-code giberish. Now you can REALLY code something worth your time. Make your own .DLLs and release them, simple huh? Also, QuakeC code can't be used in Quake II directly. The code will be server side only. No more client downloads! (Please note that in QuakeWorld you didn't have client code just in plain Quake DM)

Brian Hook: Quake2 will probably be MORE customizable than Quake, since we're using a DLL architecture that really gives PC and TC authors a LOT more power. However, with added power comes complexity, so the barrier to entry for some folks may be a lot higher now than it was qith QuakeC.

To use addon patches you need to create a subdirectory on your Quake II folder and put the "game86x.dll" file there. Start Quake II with the following command parameter: "+set game gamedir" where gamedir is the name of the directory in which you put the game86x.dll.



Chapter IV: Gameplay

    1.    Storyline

Quake II has a coherent story for once. Nothing like Quake. "So is it a sequel?" - I hear you ask; no. The only reason it uses the same name is because id encountered legal problems with the other names they come up with, besides (like Hexen II) the game became popular and known as Quake II thus it was too late to change it.

Paul Jaquays: I've had a request (which means that there's a lot more of you out there who don't write) to explain why I'm saying that Quake II is not a sequel to Quake. The word sequel implies a continuation of what has gone before. In this case, a continuation of the battle against Quake, the mythical overlord of evil, by soldiers fighting in an undefined army in undefined places. Although many of the features of Quake II will be similar to Quake players (such as a 3D environment, some weapons that function similar to those of Quake, lava, slime and use of game's logo in certain special game powerups), it is not a continuation of the Quake story.

With Quake II, id has chosen to follow a different story line (and they did this before I got here). Instead of a vague "Kill the minions of Quake" sort of imperative, we have created a brand new story with a solid, homogenous, entirely futuristic, totally militaristic story line. In Quake II, you are a soldier in the TCM (Terran Confederation of Man) army, a combined force put together from the surviving armies of nations on the planet Earth and those of Earth's colonies on the Moon and the new independent nation of Ares on the planet Mars. Humanity is commited to what we hope will be the terminal battle of an ongoing war to not only repell alien invaders from our system, but to destroy their ability to make war of any kind. The battle (in this episode) takes place on the planet Stroggos, the alien homeworld, the core of their barbaric "civilization." Levels are designed to be played in a logical, sequential progression. And here, your mission doesn't end until the big guy, the core of the problem goes down for the long dirtnap.

OK, now WHY are we calling it Quake II, when it's not really a sequel to Quake? Several reasons. Trademarking. The names we were going for, the ones that to our thinking, really expressed the concept and theme of the game were owned by someone else (when it appears that you may have money to actually cover real or imagined damages, "foxxing" really gets ugly. They don't just tell you to cease and desist). We kept putting forward names to our copyright attorneys and they kept telling us "You're not safe from liability with that one." The deadline for having our real and true name in time for E3 came, and our hands weren't grasping that one great name. And there it was waiting for us like an old lover ... our working title ... Quake II. It knew we'd come home to it at last. It should have been obvious. We've built up a great deal of name recognition with Quake. We shouldn't just throw that away.

Paul Steed: An alien force has been pounding the shit out of earth in an attempt to invade and conquer us. The aliens are a nightmarish and painful hybrid of machine and flesh. They are pure evil incarnate and probably eat raw human flesh as well.

As the game unfolds you are part of an invasion force which has found a way to reach the alien homeworld through their own technology (i.e. worm hole/black hole trans-dimensional transportation 'portals'). As you hit the dirt of the said alien homeworld you quickly realize that most of your buddies are in the process of being wiped out and it is of course up to you to save the day. Your goal? To shut down the defenses of the alien military complex which you've crash landed into and specifically incapacitate the 'Big Gun' which can shoot down any one of the ships in the awaiting fleet overhead.

Once you've accomplished the destruction/shut-down of the Big Gun, the fleet will begin pounding the alien planet into submission as most of their defending fighters are off pounding OUR planet.

Activision: After years of waging war against the alien aggressors, the Earth is on the verge of being completely obliterated. A last effort to bring the mass destruction to an end is underway. Launched from a giant space carrier, you are part of a secret assault force sent through an interplanetary gateway in single-manned pods. Shortly after landing on the alien surface you learn that hundreds of your men have been slashed to just a few. Now, you must do what entire armies could not: fight your way through heavily fortified military installations, lower the city's defenses, and shut down their war machine. Only then, can Earth even hope to launch an air assault. Only then, will the fate of all humanity be known.

Taken from the Quake II manual:

Long shadows claw desperately away from your dusty combat boots, fueled by the relentless sun of a late Texas afternoon. Shading your eyes against the glare, you squint for the thousandth time at the line of soldiers ahead of you. It stretches on endlessly across the rubble, disappearing at last into the cool shadows of a troop carrier. Soon you'll walk up the ramp into the ship, climb into your one-man cocoon, tear through the interplanetary gateway, and smash down light-years away from the blowing sand and blasted ruins that surround the Dallas-Metro crater.

"What the hell is taking so long?!" you snarl, slamming the battered barrel of your side arm, the blaster, against your scarred palm. "I've waited long enough. Time to kick some Strogg ass."

Slightly rocking back and forth under the sweltering August sun, you spit out of the side of your mouth, rub your eyes, and think back to the day when the wretched creatures first attaced. Like flaming meteors, their crafts pounded into the Earth and unbelievably, these bio-mechanical aliens... these hideous cyborgs... swarmed out while their ships still sizzled with reentry heat. They killed or captured anything that lived. We figured that the Strogg were after our planet's resources: minerals, metals, and water: things like that. But their onboard storage facilities did little to disguise what they considered to be resources: fleshy limbs and organs for new cyborgs, and of course, food. The line moves. And moves again. Into the cool shadows at last. The assembled armies branch off into new lines divided by corps and unit.

"I can't deal with this shit - what's the friggin' hold-up?"

"Cool your jets, marine." Tokay mutters and smiles over his shoulder. "We'll all get a few Strogg heads to take home as souvenirs. I promise you that."

"Yo, soldier, 3585." The medtech's voice startles you. "You in or out?"

Competent hands guide you into the coffin-like opening of your Mark 9A drop pod: sleek, dark, and invisible to the Stroggos defense systems. One of the techs begins to drop the reinforced pod door. "Sleep tight, soldier. You'll see sunlight in less than six and a half hours. Not our sun, mind you." <SLAM>

Pitch black except for the mild glow of your video readout system in front of you. You've done this a dozen times in the sim classes. No sweat. Just a few short hours to sleep, recharge, and then the moment of glory. But this time it's for real.

It's also time to think. You recall your first official day of training, your unit commander discussing how these damn parasites made it to Earth and other nearby colonies in the first place. By employing our best satellites and long-range scanners, we learned how they traveled light years so quickly - the Strogg used these black hole-like gateways as their highway to heaven. We still don't know if they created these rips in the fabric of space and time, or if they simply discovered them by accident. Either way... it's just like opening the door to an all-you-can-eat restaurant for these bastards. In about two hours, we'll be entering the same interstellar portals, to hit 'em where it hurts... on their own turf. You close your eyes and relish this thought. Eventually, you nod off to the low hypnotic hum of the troop carrier.

*Crackle* ... *fzzzz* ... "Greetings to the people of the Coalition. This is Flag Admiral Crockett, speaking to you from the bridge deck of Phobos. We are entering the outer orbits of Stroggos, the alien's home system. As we had postulated, Stroggos' atmosphere is harsh but breathable. We expect to make planetfall soon. Now is the time to switch on your debriefing panel if ya need it."

"Boomer?" the voice crackles through every soldier's headset. "Drop X-ray squad in 30 on my mark. You copy?"

"Roger that!" In another pod, your sergeant snaps back. "OK boys and girls, you see the clock on your heads-up. Two demerits for anyone who up-chucks during bounce and roll!"

*Shthunk!!* Your drop pod is shot from the side of the carrier and hurtles downward. *Wheee-oooooo!* Incendiary atmosphere howls past the pod's rapidly heating shell. *Ka-WHUMP! * The pod wall suddenly buckles to your right, but stays intact. Another pod must have clipped yours on its way in. ECM didn't indicate enemy fire. Shit. Thrusters and stabilizing gyros are fading. Based on the pings, the other pods are pulling away. Below you, the large alien city roars into focus on the screen. But where are the other pods? They were there a minute ago.

Suddenly, distorted radio chatter lights up, "Mayday! Mayday! Lost all power... shielding failed... missed dz... some kind of EMP is... kzzzt... us out. We're dropping like fli... zzzzkkkzzzt". Silence.damn! If the Strogg have electromagnetic pulse defenses and we failed to detect them... all of us are in the shitter. That HUGE blip has to be the Big Gun. You do a slow dogleg left as your navcomp finds a place to land when all of a sudden retros kick in and propel you south.

"What the...?" Before you know it you skip across the lip of a crater and slam into a structure, a good distance away from your target. Dazed and bleeding from a head cut you toggle open the labeled arsenal bins and reach for where your gear ought to be stowed. Damn. Nothing but your sidearm.

Damn again.

You leap out the crushed pod door, alone, with blaster in hand, and tear off into the room with the bittersweet stench of vengeance coursing through your veins...


    2.    Your Character

You are able to choose between male and female space marines. The female is more a Vasquez type marine than a Babe; yet it manages to retain a sexy look while the male character is bald and tough. Note that there is at least one male skin where the character isn't bald. These don't have Duke kind of attitudes though:

Brian Hook: The player you play is not a character we create. We prefer it when the character takes on the player's own state of mind and personality, so we're not going to try and insert an artificial personality into the character.

Brian Hook: I don't think "id" has a view on female gamers, but I know there are a lot of individuals here that do. We think it's really cool that all-female clans exist, and we think it's cool that Quake is THE game that has popularized female gamers in what is predominantly a male dominated genre (first person shooters). We did a female character because this is what people like PMS, CW, etc. will want. It would suck that a female player would run around in a guy's body when we can provide them a female equivalent. So that's what we're doing. We're providing the female character to appeal to female gamers out there, not to appeal to the hormonal urges of teenage boys.


    3.    Weapons

Breaking up with previous id games, the weapons are offset to either side (lefties rejoice) giving it a much more realistic look and the basic "out-of-the-stomach" view which probably is only used in Deathmatch. All weapons are futuristic with a mix of earth and alien pieces of mass destruction. Currently, there are no plans for a melee weapon. (personally I'd like to see a comeback of Doom's chainsaw :) The third column tells you how much ammo a particular weapon discharges with just one press of the trigger. The fourth column lists how much raw health (raw as in before acounting for armour) each individual hit will take from the target in Deathmatch and the final column for any special cases:

Weapons Type Of Ammo Ammo 1 Shot DMG Special DMG
Blaster - - 15 10 DMG in single player
Shotgun Shells 1 4 / fragment Max DMG = 48 if all 12 fragments hit
Super Shotgun Shells 2 6 / fragment Max DMG = 120 if all 20 fragments hit
Machinegun Bullets 1 8  
Chaingun Bullets 9 6 8 DMG in single player
Grenades Grenades 1 125 Blast Radius = 165 units
Grenade Launcher Grenades 1 120 Blast Radius = 160 units
Rocket Launcher Rockets 1 100 + (0 to 20 random) Blast Radius = 120 units
Hyper Blaster Cells 1 15 10 DMG in single player
Railgun Slugs 1 100 150 DMG in single player
BFG10K Cells 50 - -

The Blaster has unlimited ammo thus no info is relevant regarding how many ammo it depletes in one shot. The Chaingun has a rate of fire of 20 bullets / sec for the first second and 40 bullets / sec afterwards. To understand the units you should be aware that the height of the player is around 64 units. BFG elaborate explanation:

Once you fire it and the green ball is hovering to its target a number of green lasers will ignite from the center of the green ball which will hit any adversaries within a 256 units radius. This laser will take 50 health points per second. Once the green ball touches either an enemy or a wall it will take 100 points (when closest from impact point) from the unlucky target plus it has a 200 unit radius from the impact point. Please be careful if you happen to be within that radius the blast will take twice the health points from you (200 when closest to impact point). But the fun is not over, the BFG also spawns up to 500 damage in a 1000 unit radius.

If you'd like a more in depth view on weapons and inventory then you should read the Tips section or The Quake II Weapon and Combat FAQ.

Due to time constraints weapon discrimination in multiplayer games is still not implemented (i.e. you still can't tell which weapons the other players are using). id has stated, though, that this feature might be available in an official addon. Apparently you'll be able to view three different weapon models: small, medium and big. Although not perfect it helps to know when to charge and when to... er... run away. =) Also, when running, one hand wings for balance while the other holds the weapon.

Brian Hook: We're aware of the weapon balance issues people had with Quake, and those are being addressed. We're going to have more weapons, and we're also going to be modifying the characteristics of some of the weapons (DB shotgun will be more powerful, RL may be a little weaker or slower).

Unfortunatly we can't use the gun turrets found in some of the levels. Several weapons like the desintegrator, flaregun and mines were removed from the game. A variation of Rocket Jumping is now possible in Quake II: Barrel Jumping where you step on top of one of the exploding barrels present in Quake II (ALA Doom) and doing a Rocket Jump. This was already possible in Quake but you had to be invincible otherwise you'd be blown to pieces by those Nuke Boxes. This new Barrel Jumping propells you to incredible heights, possibly four times your standard jumping height.

In Quake II you can do a BFG jump as well, pretty much like Rocket Jumping. The major difference is that you have to pull the trigger _before_ you jump. Wait a couple seconds (for the BFG to warm up), point downwards, jump and blast yourself into the cosmos.

Paul Steed:


    4.    Inventory

Here are some of the items available from the simplest and mundane to the rare and powerful:

Ammo Amount per box Max Bandolier Backpack
Shells 10 100 150 200
Cells 50 200 250 300
Bullets 50 200 250 300
Slugs 10 50 75 100
Grenades 5 50 - 100
Rockets 5 50 - 100

The Bandolier and Backpack columns state the new maximums for a particular kind of ammo after picking up those artifacts.

Armour Amount per item Max
Armour Shards 2 -
Flak Jacket 25 50
Combat Suit 50 100
Body Armour 100 200
Energy Armour - -
Energy Shielding - -

Armour Shards keep raising your stats even if you have 100 or more. The last two armour protections use cells so their Amount and Max are dependent of your cell suply. The Energy Shielding is actually not available in Quake II but it is included in the Quake II gamex86.dll (which controls the actual game) but id Software decided not to put it in. This armour only works when the energy weapons' blasts hit the target in the front, unlike the Energy Armour which protects the whole body.

Health Amount per box Max
Stimpacks 2 -
First Aid 10 100
Medkits 15 100
Adrenaline raises up to 100 if health < 100 100
Mega-Health 100 -

Stimpacks keep raising your stats even if you have 100 or more. The First Aid and Medkits raise to 100 (or whatever is your standard maximum health).

Paul Steed: We currently have plans for IR goggles and a scope which zooms in on a target.

These two artifacts were removed.


    5.    Enemy

I already discussed about AI so I'll concentrate on the actual foes you'll be encountering throughout the game. There are lots of new stuff in Quake II's enemies: there are female-looking monsters, they seem to be alien cyborgs (machines with living tissues), when they die swarms of flies gather around the corpses, monsters have amazing animations to reflect which part of their body was hit and they have two condition skins which will reflect the monsters health (and aggressiveness :).


    6.    Units

Levels are broken down into missions (Units). There is more scenery interactivity by being able to destroy walls and other parts of the world. You're now able to crouch, use an inventory and interact with the scenery. You still don't have a "use" key though.

The levels now have a theme and objectives like "destroy the reactor core" and things like that. You'll see several pieces of machinery where you can interact and push levers and stuff. It won't be just mindless carnage this time. If you wish to skip a certain unit then just bring down the console and type the exec command as described below:

Units Description Skip
Military Base The start of the game. Scenery damage due to marine strike -
Bunker Warehouse Sabotage the alien's logistic support of their main defense systems exec warehouse.cfg
Jail Pretty obvious exec jail.cfg
Mines Damp, eerie passage ways back to the factory exec mine.cfg
Factory The Strogg's assembly line exec factory.cfg
Power Station Take out the energy to the Big Gun exec power.cfg
Big Gun Sabotage the Strogg's main planetary defense system exec biggun.cfg
Hangar The aliens are trying to escape through their wormholes, stop them exec hangar.cfg
City Stroggos capital city exec city.cfg
Final Battle Hunt down and kill the Stroog's leader, Makron exec boss.cfg

Here is the complete lowdown of the 55 levels present in Quake II sorted by category and filename. Type "map x" at the console where x stands for the first term below:

Single Player Levels

base1 - Outer Base
base2 - Installation
base3 - Comm Centre
biggun - Big Gun
boss1 - Inner Chamber
boss2 - Final Showdown
bunk1 - Ammo Depot
city1 - Outer Courts
city2 - Lower Place
city3 - Upper Place
command - Launch Command
cool1 - Cooling Facility
fact1 - Receiving Centre
fact2 - Processing Plant
fact3 - Sudden Death
hangar1 - Outer Hangar
hangar2 - Inner Hangar
jail1 - Main Gate
jail2 - Detention Centre
jail3 - Security Complex
jail4 - The Torture Chamber
jail5 - Guard House
lab - Reaserch Lab
mine1 - Upper Mines
mine2 - Borehole
mine3 - Drilling Area
mine4 - Lower Mines
mintro - Mine Enterence
power1 - Power Plant
power2 - The Reactor
security - Grid Control
space - Comm Satellite
strike - Outlands
train - Lost Station
ware1 - Supply Station
ware2 - Warehouse
waste1 - Toxic Waste Dump
waste2 - Pumping Station 1
waste3 - Pumping Station 2

DM Levels

q2dm1 - The Edge
q2dm2 - Tokay's Towers
q2dm3 - The Frag Pipe
q2dm4 - Lost Hallways
q2dm5 - The Pits
q2dm6 - Lava Tomb
q2dm7 - The Slimy Place
q2dm8 - Warehouse

64-player DM Levels

base64 - Tim Willits
city64 - Paul Jaquays
sewer64 - Christian Antkow

Capture The Flag

q2ctf1 - McKinley Revival
q2ctf2 - Stronghold Opposition
q2ctf3 - The Smelter
q2ctf4 - Outlands
q2ctf5 - Capture Showdown


    7.    Cheats

If you don't like to cheat then skip this section. Otherwise read on. Btw, these are typed in the console.



Chapter V: Multiplayer

    1.    Modem-to-Modem & Serial

There is no native Modem-to-Modem or Serial play. Since QuakeWorld technology is getting better, a simple (not perfect, but easier) solution if you want to play a friend like this is to just both jump on a close server and play. With the Plus! pack for Win95, you can use its included Dial Up Server utility to have two modems connect and then simulate an IPX LAN over it. This makes Quake II modem-to-modem playable, but the problem is that one player would still be the server, the other would still be the client, and the one who is the client is going to have about some lag while the server has zero lag. This makes for a very unfair (for whoever the client is) game and is not likely to be a whole lot of fun. The best solution is likely still going to be playing via the Internet where two modem players are fairly equally lagged. You don't need Plus! tough, here's Microsoft's DUN.

Anyway, I removed the steps to connect using DUN since several ppl reported it to be inacurate. If you wish to setup a Modem-to-modem game check either this one or this one.


    2.    LAN / Internet

No IPX, just TCP/IP. John Cash is apparently working on IPX support. Nevertheless I got word that Quake II v3.10 is indeed capable of IPX networking; apparently Quake II will use TCP/IP but if you uninstall it and leave IPX Quake II will use it. Again, I've not tested this and the person who told me this isn't capable of writing a "how-to" setup an IPX game like the one below for TCP/IP because of the language barrier. Anyway Stefan Norman told me that v3.10 IPX is indeed ok to use as an protocol for LAN multiplayer. Apparently, there is no special thing you need to do to get it running. Just start a server on one of the machine and the others just do a search.

Ron Stockwell: For a straight Windows 95 peer to peer network with more than two PC's, go get yourself a cheapy little 8 port 10baseT ethernet hub. They can be found for be less than $100 bucks if you look hard enough, or buy one of the kits that comes with 2 LAN Cards and some wire, also for under $100. Install an ethernet card in each PC you want to hook up to your LAN. They run the gambit; you can find generic ones for $20 or brand names like Intel or 3Com for about $100.

Let Windows detect and setup your ethernet card. Once you have that done, be sure to go into Control Panel -> System, and make sure it installed properly; i.e. there shouldn't be any conflicts or yellow "!"' by the ethernet board in the Device Manager.

Now, in Control Panel, pick Network, to open up your Network settings. Since you're already using Dial-up Networking, you will have the Microsoft TCP/IP protocol already installed. What you will have to do is click on Add, then add it again. This time, it will bind to your ethernet card also. Click on the File and Print Sharing... button, check the I want to Share my Files box, and click OK. If during the card detection by Windows, it automatically installed IPX and a client for Novell networks, you may remove these because they won't do anything.

When you're done, you should have the following list in your Network dialog box:

Client for Micosoft Networks
Dial-Up Adapter
Your Ethernet Card
TCP/IP -> Dial-Up Adapter
TCP/IP -> Your Ethernet Card
File and printer sharing for Micorsoft Networks

Go into the Identification Tab. Type in a unique name for your computer. It must be different on every Win95 machine you hook up. Set the Workgroup name to "WORKGROUP" The description doesn't matter. Click OK.

Click the Access control tab. Make sure Share level access control is checked. Click OK.

Go back to the Configuration tab. Click on the "TCP/IP .> Your Ethernet Card" line and then click on Properties. Click the IP Address tab. Click on Specify on IP Address.

The address I used was for my fast PC that will act as the server. I just incremented the last number by one on each subsequent PC ( ( etc. In the Subnet mask, type in Click OK. Click OK to save these changes in the Network Dialog box.

That's it. Re-boot the computers, start Quake2 on the server, and then start Quake and join from the other PC's. They should see the local Server without having to do anything with the address book.

If you don't get the server to appear, open a dos box and type thins on the command line: ping (or whatever address you gave the server) You should get four lines of replies from that address (your server), in like 1 millisecond. It will time out if the PC's are not talking.

Also, to help in sending patches, add-ons, config files, etc. to the other PC's after you've spent all the time to download them from the internet, do this to make your life easier.

Open Windows Explorer. Right click on the C drive icon. Select Sharing. Click the Shared As button, and give the hard drive a unique name. Click the access setting to Full and click OK. You can use the password security if you like, but it really doesn't do much. Once you supply the password on the PC that will access this hard drive's files, it remembers it, and you never are prompted for it again. On the PC's you wish to copy files to, click the Network Neighborhood icon on your Desktop. You will get a list of all the PC's set up on your network with the Microsoft Clients. Double click on the PC you wish to access, then supply a password if you used that option, and do the rest just like copying or moving files in regular old Explorer. You can even run install executables from the other PC without copying the install files over to the destination. Pretty cool.

Novell IPX LAN users:

You can run Quake 2 on your LAN, under these conditions that I have tested. On a NetWare 4.1 LAN running Windows 95 on the workstations with Novell Client 32. The Client32 is version 4.11, the latest version. I would not suggest trying this stuff unless you are absolutely sure you can restore the Client32 system if something gets messed up. I can't stress this enough: Please know what you're doing before you start messing with your Netware LAN!

You can run Microsoft TCP/IP over the same LAN cards in your PC's that are currently using IPX with Client32 for Netware. In Control Panel -> Network -> Add -> Protocol-> Microsoft, just add TCP/IP and it will bind to your LAN card. You may need to do this even if you have TCP/IP for Dial Up Networking installed. Also, in the same dialog box, add the Client for Microsoft Networks. Select the Identification Tab, and make sure all the PC's you want to connect have the exact same Workgroup name. Select your LAN card and click on Properties. In the IP Address tab, give your LAN card an IP address, for example, with a subnet mask of Number each PC with a unique IP address, like, and so on. MAKE SURE that the Novell Client 32 remains the Primary Network Login. Click File and Print Sharing and turn on the File Sharing, click OK, the OK one more time and reboot.

The first time rebooting, you may not get your normal Novell Login. All I had to do was shutdown once more, and reboot, and the system came back up just fine with the Novell Login. Now, this should work fine for the 4.11 version of (Intra)NetWare, especially if you're using TCP/IP instead of IPX for the protocol. But I wouldn't try it with either of the first 2 versions of Novell's Client 32 on any enterprise LAN. Those first 2 versions were buggy and very, very picky, and if everything wasn't done in the proper order, it didn't work (sometimes not even if you did it right). I know, I've been through the process of going from the DOS/Win3.1 Client all through the various versions of Client 32.

Also, if you're running the Network on a hub, be careful. You could cause a huge amount of traffic and slow down your LAN, and even cause excess collisions. If you're fortunate enough to have a Fast Ethernet switch, like the Cisco 1900, the traffic goes only to the destination PC, not EVERY PC on the LAN.

Hope these instructions help the needy Quakers out there!

If you are using BNC (coax) cabling for your network and you want to connect more than 2 PCs be sure that the wire runs from PC to PC, not each to a "Y" type connector.  This can cause termination problems. Although you may be able to "see" each other in Network Neighborhood, Quake II may not.  Just make sure they are running in a series type setup. This is different than the Cat5 (10BaseT) wire I use, which runs fine in a "star" wiring setup with a Hub.

CTF is NOT included as standard on Quake II's first release; not enough time. The code is being implemented by Dave "Zoid" Kirsch one of CTF's original programmers. Also, you'll be able to trade weapons and inventory items with your team mates. This will come as a free update later.

Dave Kirsch: Just for people's curiousity, here's what I've been working on in respect to Q2 CTF lately:

* means fixed, no star means still needs done

*- intermissions need fixed in ctf5
*- blue side dm spawns need fixed in ctf5
*- grapple pull sound doesn't stop when hitting team member
*- pull sound doesn't stop when killed while grappling
*- stuck on doorway from central areas on ctf5
*- clip brushes on ctf5 near escape pods
*- explain tech inv, how to drop them
*- blue scoreboard names wrap
*- cmd team from spectator causes problems (should be disabled, use the menu)
(this is the invisible player prob)
*- Explain [ and ] on the menu for selection
*- 'already have tech' overwrites other msgs? don't spam it
*- powerup should fly randomly from player (stuck in gun right now)
*- grappling floor causes damage on release
*- grapple release is too slow
*- bfg beams target team members
*- grapple is broken with haste (frame stuff)
*- telefrag should work on teammates
*- bad model frames when switching weapons with haste
*- flag icons for carrier on scoreboard is wrong
*- check that flag sounds are on the flag, not the player
*- add drop tech
*- skins are too dark--can't see them
*- say capturelimit, not fraglimit hit
*- add capturelimit cvar
*- make sure hyperblaster is stay weapon in dm3 rules on ctf1 (not bfg)
*- grapple is broken with haste (frame stuff)
*- telefrag should work on teammates (damage no protection on teammates)
*- bad model frames when switching weapons with haste
*- flag icons for carrier on scoreboard is wrong
*- check that flag sounds are on the flag, not the player
*- add drop tech
*- score is kept when changing teams?
*- fixed it so flags don't explode when blocked by a plat/door, etc.

- Add prevweapon (impluse 69 clone from old ctf)
- player connect time isn't on scoreboard--dunno if I can fit this
- some grapple sounds are still ATTN_NONE (full volume through out level)
- grapple doesn't stop sound sometimes
- new sound effect integration
- add team armor protect
- check that tech powerups aren't getting destroyed, too

exe changes:

- 'ctf' string in executelayout
- red and blue flag/flag carrier glows

The Internet code in Quake II is pretty much like QuakeWorld (client prediction is in as well). Still, the point release will be made available to improve network play. Each server can host a maximum of 200 players if the system is capable of it however 64 players is the recommended maximum. Servers won't be dynamically linked, meaning you can't jump from server to server through slipgates, etc.

Regarding Client Side Prediction:

Brian Hook: As far as I know CSP can be disabled at will.

Brian Hook: No, the number of polygons won't cause more lag, but it may reduce framerate. There are issues with uploadable models that we haven't addressed yet (e.g. really small models that would be impossible to see, etc.), but these are handily addressed by simply disabling custom models on the client side. We'll try and come up with other workarounds too to prevent models that are too small.


    3.    Lag

When you connect to a server, no matter how near it is, your commands (like firing, moving, etc...) take some time to arrive there. Then the server's response will take the same time to arrive at your comp. This is unnoticeable on LAN games since the computers are too close. Over the Internet, however, lag is the player's worst nightmare. :)

QuakeWorld manages to reduce lag in half because it doesn't need confirmation from servers for movements - client prediction. Firing still requires confirmation though so it's not a smooth ride altogether.

Here is what John has to say about Multicast IP:

Are you thinking of using ip multicast (igmp) in your quake server at some point? I'm sure many routers do not yet support this, but at some point it will be a perfect way to propagate game status information at a reduced bandwith.

John Carmack: Actually, multicast won't help. Each client gets a specifically tailored stream of packets with only the bare minimum information they need. No two clients get the same info, so multicast isn't usable.

Robert McMillan reports: I was getting ping times for Quake II ranging from 350 to 8000. (It was totally unplayable) I then discovered the following sites and I now get ping times in the low 200's. I think it would be a tremendous service to include this info or links in the multiplayer section of the FAQ. A headline on with an overview might be nice too.

Note this site recommends installing a Unimodem Driver update. The self extract needs to be unzipped in the windows\system dir and should not be applied if IE 4.x is installed. If you have OSR 2, you probably don't need the update anyway. I'm not sure if it really did anything for me...

A freeware program to give easy access to the TCP/IP registry variables is at this URL:


    4.    DeathMatch

The beauty of DeathMatch is that instead of wiping out brainless foes (the enemy) you have the opportunity to take out intelligent ppl as bot like artificial intelligence is still far away for single player (perhaps in Unreal). I strongly advise you to finish Quake II without cheating and, at least, in normal as codes will not work in DM. This will give you some knowledge of enemy standard attacks, ammo management and, of course, knowledge about the levels themselves. Like I said earlier, your enemies will be intelligent and won't just charge mindlessly to their DOOM =) so the usual "strafe 'n' fire" will no longer work, as they will run hide from you, try to surround you, jump small gaps and will be carrying the same weaponry as you! Ever wanted to know how a BFG shot feels like?

A good control system (i.e. config.cfg) can sometimes give you that extra edge. Instead of pasting any "perfect" config.cfg I will mention some things that you may test and, if you feel confortable with, use them in your configuration. You have several configuration files from the "pros" inside pak0.pak. You can take a look to see if you're missing something but like the saying goes: "The best config, is the home-brewed one."

  1. A good rule of thumb is to use the most sensitive imput device you can find. (Sensitive? Input? Er... no pun intended) The mouse is regarded as one of the best (if not the very best) method of controlling your player. I've been a keyboarder until Quake showed up and it took me a while to play as well as with keys, I changed controls not because everyone else was saying rodents were the best but because swiming, vertical / horizontal aiming and turning simply cried out for more sensitivity than the keys provided. Experiment. Not one time but actually finish Quake II using a mouse.

  2. If you do use a mouse, the more buttons it has the better; but even if yours only has two you'll be fine. Firstly enable "freelook", this will relieve you of binding / learning / pressing one key more while playing the game. If you're like me and also play / enjoy flight simulators then you may want to "invert mouse" for the vertical movement. I encourage you to enable "always run".

  3. Personally I use my second mouse button to bring the Chain gun and the third to bring the BFG. I also bound the weapon keys around my movement keys (W - forward; S - backwards; A - strafe left; D - strafe right) which means the blast, shotgun, super shotgun and machine gun remain on their original numbers but the E - Grenade Launcher; R - Rocket Laucher; F - Hyperblaster; C - Railgun. If you don't have three mouse buttons I suggest you bind the BFG to Q. This will allow you to quickly change weapons without taking your left hand (if you're right handed) from the movement keys. And since the new weapon keys are adjacent to the movement keys after a while you won't need to look down on the keyboard while selecting. I've bound G to grenade tossing.

  4. I use SPACE and ALT to jump and duck respectively. As they also remain close to the movement keys I only have to slide my left thumb whenever I want to preform those actions. Regarding swiming, I encourage you to swim using the mouse and pressing the movement keys instead of having to remember two new keys (move up, move down). Nevertheless, SPACE and ALT also double as those actions while in water. I didn't bind any of the artifacts simply because most servers enable auto-use imediatly after picking up an artifact.

Here arew few general advices on how to improve your gameplayship. Some of you may already follow these guidelines unconsciently but I felt a written approach would make them more obvious to you.

  1. Always know the level you are playing! Know the secret rooms, the spawn spots, weapons locations, possible hideouts for when you are low on health and finally sniper points or SPs (to attack from but also to defend yourself from them).

  2. Always know which weapons are available in the level and try to guess your oponents' current ammunition status by taking small mental notes of which ammo your enemy has picked up. This will be a great help to you in future confrontations.

  3. Use the scenery to your advantage. The most common thing is to blow up a barrel next to the other player but also use pillars to "hide 'n' seek", trenches to safely flee from a confrontation, use slime pits to trap your enemies (if you've got a Environmental Suit or not), use SPs (usually higher places with a great view where you can "download" waves of bullets or even rockets) and finally lure your foes to crushing ceilings or other areas with lots of traps willing to suck some blood.

  4. Try to spot opening/closing doors and operating lifts either by audio or visual effects to know the proximity of your foe. Also, getting in/off water, picking up powerups and jumping sounds. Of course, you will want to reduce the sounds you make. Don't pick up shells if you're not planning to use either of the shotguns. DM could be defined as decision making where you have to quickly evaluate whether your future move will be worth the risk or not; and this in fractions of a second.

  5. Don't walk next to walls unless the lighting is poor or you have cover. When entering a room try to spot any other doors, windows or corners and quickly find a place you can hide; try to memorise the maximum number of rooms you can, so if you are being chased just remember the room with the best place for a counter-attack (usually a dark one).

  6. Always assume another player is chasing you (i.e. turn around quickly or strafe and turn back) or assume the other player is in the room you are going to enter (open it and step back quickly). Do NOT fire a few rounds when entering a room as you'll give away your location; the important thing I want you to remember is that you must be ready for _anything_.

  7. Don't stay in the same place for a lot of time or the others will pin point you (specially from the SPs). This includes stops to "chat". If you want to then find a quiet spot or wait until you die =). This, of course, when "force respawn" is disabled.

  8. When chasing someone that knows you're after him be very careful: You should watch for rapid counter-attacks specially after some twisted tunnels or when entering dark rooms/corridors (which is something you shouldn't do when the distance between the two of you is great) and try to spot if your enemy is luring you to some place. If you know the level well, you must break pursuit after some time, and then try to surround your foe to surprise him. Be ready to strafe as he can easily turn around and walk backwards while firing a couple of rockets at your bloody face!

  9. The best way to chase anyone, without him knowing, is by keeping your distance and avoiding opening doors or operating lifts. Prepare your weapons for highest impact and fire only when your enemy is in a dead-end, next to a high cliff, a slime pit or crushing ceiling or when you "know" his health is low. For "sure kill" use a rocket (careful! Rockets are relatively easy to avoid since they were slowed down from Quake).

  10. Unless you're 110% sure the others will not discover your secret armoury, pick up EVERYTHING! Leave nothing for the others! This is the time to be selfish!

  11. If you blow up the barrels you'll be wasting your ammo but it could be saving your life, on the other hand it could be saving the others life as well. Tough subject...Hummm.... Frag'em! It's FUN!

  12. When playing in teams (CTF for instance) TALK to each other! Not just "Let's wipe out these suckers" or anything like that but (when together) "Open that door and quickly step out, I'll be ready!" or something like that because it adds to the fun and it makes your DeathMatching a lot more effective. You should bind certain keys to pre-written messages so you don't have to take your finger from the trigger. =)

I'll give you the low-down on the weapons first and ways to defend from them:



Chapter VI: Editing Quake II

    1.    Levels

Here is a listing of all the Quake II aware level editors at this time of writing; sorted alphabetically:

After saving your map you'll need to compile it before testing it. Here are all the compiling utilities needed:

Related websites:


    2.    Textures

Here are some utilities to help you create/edit your textures and / or skins:

Related websites:


    3.    Models

Coming soon.


    4.    PAKs

Let you edit the Quake II .PAK file or create your own. Extract or Import files from / into .PAK files:


    5.    Cinematics

Utilities that let you create your own cutscenes:


    6.    Code

Needed to create your own mods:

Related websites:



Chapter VII: Quake II Third Party

    1.    Levels

List of websites which host / review single player and / or DM user levels:


    2.    Addons

This sections was created to listing the most popular Quake II multiplayer mods so please don't ask me to link to your mod. Sorted by name.


    3.    TC/PCs

Only released TC/PCs are listed here with a small description:


    4.    Mission Pack #1

There is already an official mission pack planned for Quake II. Being distributed by Activision Quake II Mission Pack: The Reckoning, developed by Xatrix Entertainment and published by id Software is said to be available in stores in March 1998. The mission pack will provide extra levels plus specific DM ones that allow at least 32 players. Also, new weapons and enemies are said to be included. You can get more information and five screenshots here.



Chapter VIII: Frequently Asked Questions

Question: Can I take screenshots while playing the game?
Answer: Yes, press F12.

Question: Does Quake II take advantage of multiple processors for faster rendering?
Answer: No, not at this time of writing.

Question: How can I find out at how many fps Quake II runs?
Answer: With the console command "timedemo 1" and then "demomap demo1.dm2" or "demomap demo2.dm2".

Question: Where can I see if my framerate is any good for my system?
This is a good place to start.

Question: Is there anyway to get the Quake II console font?
Answer: No. That font is a set of graphics and not a true type font or whatever.

Question: Can I play single player Quake II without the CD when I max install?
Answer: No. Only DM.

Question: How can I dload custom skins so I can see them while playing? Is there any command?
Answer: No. You need to dload them from a website before joining a game.

Question: How can I find servers on the Internet?
Answer: Download or visit some of the server pages like this one.

Question: I'm new to the Quake community and / or Quake II. Should I kill myself?
Answer: Too messy. Visit the
Quake II Scene.

Question: What's this clan stuff? Where can I find them?
Answer: Visit the
Wireplay Clanring.

Question: I'd like to start my own server; do you have any info for me?
Answer: Get the
Quake II Server Frontend.

Question: When I connect to a server it says I have the wrong version. What's up?
Answer: Check
II.7 for information on patches.

Question: Where is the -dinput command in Quake II?
Answer: Gone.

Question: While installing Quake II it says I have the wrong language OS. It's not true so how do I install it?
Answer: Go to the regional settings and change to either English US or UK or whatever language your Quake II version supports.

Question: My sound is all jumpy, what can I do to fix it?
Answer: Install the latest

Question: I can't connect to servers / have tons of difficulties. Btw, I use AOL...
Answer: Don't use AOL.

Question: How come my guns don't show up when I play DM?
Answer: Check your character settings and set the handling to either left or right but not center. Or revert the FOV back to 90.

Question: Is there a Quake II Name Maker?
Answer: Yes, check

Question: How do you change the position of your status bar?
Answer: You can't change it.

Question: I installed a patch but I want to return to the original version; how do I do that?
Answer: You'll need to uninstall and re-install Quake II.

Question: I had a mod that worked fine until I installed the latest patch. How do I fix it?
Answer: You can't. You need to wait for the author to release a version compatible with the latest Quake II version.

Question: I'm having some problems with my mouse. Can you help?
Answer: Check
this page.

You should also read The Official Quake II FAQ if you're having problems installing/running.


The End