PAK is one of the formats that usually packs the content of games to make especially protected data, such as graphics and music files harder to access. This PAK files are not always the same: You can open the PAK files of many games of the Quake engine simply by using ZIP-compatible unpacker, whereas this doesn't work with others PAK files.
Archived from groups: alt.games.quake 'Stephen Howe' wrote in message news:[email protected]. Hi For Doom2, there were a number of great quality 32-level user WAD files (not forgetting Plutonia and TNT which were official ID) I am thinking of Eternal Icarus Memento Mori 1 Memento Mori 2 Requiem Hell Revealed Alien Vendetta For Quake 1, there were the official 'Source of Armagon' and 'Dissolution of Eternity' (which I have played). Are there any recommended user PAK files for Quake 1? Any URLs for a recommended list?
Thanks Stephen Howe Hi Stephen, This ought to get you started: Check out the Downloads/Mods area Nehahra is excellent G. Archived from groups: alt.games.quake 'Stephen Howe' wrote in message news:[email protected]. Hi For Doom2, there were a number of great quality 32-level user WAD files (not forgetting Plutonia and TNT which were official ID) I am thinking of Eternal Icarus Memento Mori 1 Memento Mori 2 Requiem Hell Revealed Alien Vendetta For Quake 1, there were the official 'Source of Armagon' and 'Dissolution of Eternity' (which I have played).
Are there any recommended user PAK files for Quake 1? Any URLs for a recommended list?
For each of the official missionpacks, the important data file is their 'pak0.pak' file. In the case of missionpack 1, its pak file should be placed in a game folder named 'hipnotic'. For missionpack 2, its pak should be placed in a game folder named 'rogue'.
Game folders for the official missionpacks (and also for any user-created mods) go inside your Quake installation folder. They are at the same level as your 'id1' folder.
So for example if your 'id1' folder is at this path: C: Quake id1 Then in that case your missionpack folders would need to be C: Quake hipnotic and C: Quake rogue Or if you're putting these inside your Steam Quake install, then those folders would typically (if you have Steam at the usual location) need to be C: Program Files (x86) Steam steamapps common Quake hipnotic and C: Program Files (x86) Steam steamapps common Quake rogue Your Quake install may be somewhere different than these examples, but hopefully you get the idea. The game folders go next to your id1 folder, and the pak0.pak file for each missionpack goes into its folder. (If you buy and install the missionpacks on Steam, it takes care of setting this up for you.) This post is getting kind of long so I'll talk about launching the missionpacks in a new post. To run the missionpacks you need to tell Quake to use the right game folder, at the time you launch Quake. (So I should mention again that if you buy and run the missionpacks through Steam, it will take care of getting this right for you.) If you launch the missionpacks yourself though, you need to provide a command-line argument to the Quake executable when you start it up. For missionpack 1, the command-line argument you need to use is '-hipnotic' (without the quote marks). For missionpack 2, it is '-rogue'.
This is a little different from launching a usermade mod. Usermade mods use the '-game ' argument, but the official missionpacks don't work that way. If you use '-game hipnotic' or '-game rogue' to launch a missionpack, some things will not work right. Back in the day people would typically use a batch file to start Quake with the right command-line argument. You can also create a Windows shortcut to your Quake executable and add command-line arguments at the end of its 'Target' box.
If you're using a modern Quake engine (sourceport) there are other ways to handle this too, but I won't get into that here. But the easiest way to launch missionpacks and mods IMO is to use a front end like the Simple Quake Launcher. The guide from negke that I linked above talks about that. If you're using the Simple Quake Launcher, you can use the dropdown menu for 'Base Game' to select the missionpack that you want to play. Then it will take care of providing the correct command-line arguments to Quake for you. Whoaaa:O Johnny, May god bless you sir:) I did exactly what you said, put the pak files in the corresponding folders I created and wrote the extra command line, Voila! It works:)) And I guess you're older than me and played games in dos era.I'm 24 ('93), when I was like 4-5, I started to play games on win95 (or 98 can't exactly remember), and I used to play doom, blood, duke, shadow w.:D At those times, (weirdly) while I could play Blood, I couldn't play Quake (because I was scared):)))) So, I thought even after 17-18 years I should play the series from the beginning.
You're welcome, and glad it's working! For Quake 2 I'm not quite as sure, but I think it's slightly different. You do still have to put a missionpack's pak files into a game folder and then launch the game with a command-line argument though. Some quick Googling seems to say that for the Ground Zero expansion, the folder (in your Quake 2 install location) should be 'rogue' and the command-line argument is '+set game rogue'.
For The Reckoning, folder is 'xatrix' and argument is '+set game xatrix'. If that doesn't work, someone over at the Quake 2 forum might know more. Originally posted by:You're welcome, and glad it's working! For Quake 2 I'm not quite as sure, but I think it's slightly different.
You do still have to put a missionpack's pak files into a game folder and then launch the game with a command-line argument though. Some quick Googling seems to say that for the Ground Zero expansion, the folder (in your Quake 2 install location) should be 'rogue' and the command-line argument is '+set game rogue'. For The Reckoning, folder is 'xatrix' and argument is '+set game xatrix'. If that doesn't work, someone over at the Quake 2 forum might know more.
![Pak Pak](/uploads/1/2/5/6/125628468/222950488.png)
That worked like you said:) Thank you so much, again.