This file is dedicated for Painkiller v1.64. It contains autosave for last level on trauma.

Installation:

• Unzip the archive
• Copy the 100 folder into the C:\Program Files\Painkiller\SaveGames folder
• Run the game, go to Autosaves

[[Visit blog to check out this spoiler]]

Painkiller: Battle out of Hell

This file is dedicated for Painkiller Battle out of Hell v1.64. It contains autosaves for last level on all difficulties.

Installation:

• Unzip the archive
• Copy the SaveGames folder into the C:\Program Files\Painkiller folder
• Run the game, go to Autosaves

[[Visit blog to check out this spoiler]]

Painkiller: Redemption

This file is dedicated for Painkiller Redemption v1.05f. It contains autosaves for several of its levels on nightmare.

Installation:

• Unzip the archive
• Copy the Saves folder into the C:\Users\*yourname*\AppData\Local\Painkiller Redemption folder
• Run the game, go to Autosaves

[[Visit blog to check out this spoiler]]

Once again you’ll have a chance to experience the magnificent dark gothic atmosphere of the good(or evil?) old Painkiller, the only true oldschool FPS tough as nails, without a trace of remorse, without a glimpse of motion blur or other technological makeup. Just Painkiller and nothing else matters!

This time you’re fighting for the freedom of your soul, and you’re going to need all your strength and courage in order to break free from a prison located in the darkest corner of the Purgatory.

Action takes place in some completely unknown areas of the underworld. These areas don’t look ordinary at all. Each level is a brand new world, a universe with its own unique atmosphere, history and mysteries.

You’ll have to fight with the undead in an old gloomy abbey, on a ruined as if by an earthquakespeedway with roads and turns twisting like circles of Hell. You’ll be hunting demons amongst numerous crypts and tombs of an old London cemetery. You’ll be cleansing the old warehouse, decaying and shrouded in darkness and terror. You’ll have to stop occult rituals in an old temple complex lost somewhere in the jungle.

Med-Art about the game:

We make the new Painkiller with all our heart and soul because we love what we’re doing. Once you play Painkiller you get hooked up on it. We were so deeply amazed by its astonishing atmosphere that we still highly admire it. Sometimes you think that it’s not you who chooses Painkiller but it’s Painkiller that chooses you.

Check out the gallery for the Recurring Evil levels and also have a look at the new Hellgun weapon model.

[[Visit blog to check out this spoiler]]

You can get the Custom Level Loader here.

You may need to know how to extract PAK or PKM files- you can find a guide on how to do this by clicking here.

Converting to SP

First, make sure you have the Custom Level Loader as well as a custom level installed. Find the custom level’s folder within the Levels folder of your Painkiller/Data directory- if you don’t see it then the level was installed as a PAK or PKM file (read the next section). Once you’ve found the level’s folder rename it so that it begins with SP_ (like in SP_TreeOfWoe). Keep in mind that you cannot use spaces.

Now inside that folder you should see two files (a LUA and a CLevel) among the many folders. Rename both of those files to match the name of the folder you just renamed. Open the LUA file with any word processor (like Notepad or Wordpad). In this file you should see at least one instance of the following line:

function LEVELNAME:

LEVELNAME will appear as the name of the level… just change it to match the new name. Do this for every instance of “function LEVELNAME:” within the LUA file.

That’s it- save the LUA file, run Painkiller and the level will appear in the Custom Level Loader menu.

Installers, PAKs, and PKMs

Some levels come as an installer, PAK, or PKM file- for these there are a few extra steps involved:

If the level comes as an installer it’s best to install to a new folder so you can see the exact contents of the level. After you install, extract the resulting PAK (or PKM).

Now copy all of the folders from the extracted contents of the PAK/PKM file EXCEPT for the LScripts folder- it may contain custom menus that will override the Custom Level Loader. For even the most basic of custom levels the Maps and Levels folder ARE REQUIRED- if you do not copy these folders then the custom level will not work! Other folders like Textures, Models, etc are also important.

Now just paste the custom level’s folders into Painkiller’s Data folder. Remember to also copy over the Sounds and Music folder if the level has them (they will be separate from the PAK/PKM). Then proceed with the steps in the above section (Converting Zip Archive Levels). Once you’re finished you’ll want to remove the original PAK/PKM, you won’t be needing it anymore.

Repacking Custom Levels

If you want you can package the folders of a custom level into a PAK or PKM file that allows for more convenient uninstalling, organizing, etc while still being fully compatible with the Custom Level Loader. Remember not to add the Music or Sounds folders to the PAK or PKM… the files within these folders must be placed directly in the Data folder. You can even package all of your custom levels into a single PAK or PKM if you want, just make sure to leave out the Music and Sounds folders and copy them to Painkiller’s Data folder instead.

Once you’ve got the PAK or PKM you will need to load it… there are a few ways to do this:

(1) If you made a PKM file just place it in the Data folder and Painkiller will automatically load it.

(2) Click here for a guide on how to make and use a mod loader that will work for all custom levels. For each custom level you will only need to add a single line of code to your loader- the “FS.RegisterPack…” line. If you have powermad installed then you already have a mod loader in the included loader.lua file (just click the above link to learn how to use it).

(3) Click here for info on running the custom level through a shortcut with a parameter (info is towards the end of the linked article).

Happy modding!

~ Leviathan

• Choose from 6 HUD panel styles- Classic, Black Edition, Overdose, Steel, Blood, and Frost.
• HUD size option is now a slider from 0.5 to 1.5 (instead of just 3 presets).
• You can now adjust crosshair size from 0.5 to 2.0.
• New HUD menu with some added text.

Check out some images of the new HUD panels and crosshair sizes:

The Steel, Blood, and Frost HUD styles were made by me. The other HUD styles are from various Painkiller games.

To offer feedback or suggestions just leave a comment.

~ Leviathan

Bracket | Russian VOD

Tastyspleen.tv VODs
• Part 1
• Part 2
• Part 3
• Part 4
• Part 5
• Part 6
• Part 7

Update: We have moved to challonge.com, due to tourney.cc having some issues, causing users to not be able to register for the cup.

NEW CUP PAGE HERE

This is open to all players, even if you are from outside of North America.

Jehar over at Tastyspleen.tv did a sweet job streaming and casting for us last time. I’m excited to say that he will be casting for us again!

• Date/Time: Sunday January 8th 2012 – 2pm pst/5pm est(time is subject to change)
• Client/Server: PK++ 1.3 [ Part 1 | Part 2 ]
• Game Mode: Duel
• Type: Best of 3, Single Elimination
• Server Settings: Proplus and Rocketfix Enabled Weapon Respawn Time 15
• Time limit: 10
• Maps:
  • DM_1v1_meatless
  • DM_Absinthe
  • DM_Blink
  • DM_Psycho
  • DM_Sacred

All matches will take place on our server (redarmour.net) in Dallas, TX.

Check-ins will begin 24 hours before the start of the tournament. I will do a roll call in IRC (see below for IRC channel info) 30 minutes before start of the tourney. I will then make the brackets and post up in IRC for everyone to see. If you check-in and aren’t there for the roll call, then you will be removed from the brackets (unless otherwise noted/pardoned from this roll call).

Be sure to check out the rules.

Join #redarmour on Quakenet IRC network, if you don’t have an IRC client, you can use the web client here.

PS – go support our post on esreality.com.

Related links:

• Cupsite
• Sign-ups
• Rules
• Painkiller Lite
• Just Duel Cup #1

I wrote this guide using Painkiller + Battle Out Of Hell expansion, but I assume that this will also work with any Painkiller game.

Why Use the Mod Loader?

Easily choose which mods are loaded when you run Painkiller- enable/disable mods individually or just turn mods off altogether. You don’t even have to uninstall or reinstall any mods!

Creates a clean modding environment- each mod is put into a single PAK file and all mods are controlled by a single LUA file. This means any extra files in the Painkiller folder are files from your own mod projects- this removes any confusion as to which files are “your mods” and which are “other mods” (especially if two mods use the same file).

Easy install and uninstall of mods- all you have to do is move (or delete) the relevant PAK file then update the mod loader. No more manually deleting dozens of files spread across many folders!

Help solve mod compatibility issues by turning mods off one by one until you find the problem. Some compatibility issues may be solved just by rearranging the order of each mod’s loader code (more on this in a future update).

Making the Mod Loader

Before I begin, let me tell you something- the developers at People Can Fly created a hook within Painkiller’s code that allows mods to be easily attached to the core game. Each time you run Painkiller it searches the Data/LScripts folder for a file called local.lua and, if it exists, it will run it. There is no default local.lua file, so the developers must have left this hook in the code for modders to use.

Lets create our own local.lua file that allows you to easily enable or disable mods individually (or altogether) without having to uninstall them.

First, open a blank document with Notepad. Go to “File > Save As…” and at the bottom of the save window change “save as type” to All Files. Now save the document as “local.lua” (don’t use quotes or capital letters and don’t forget to add .lua to the end of the filename).

So now you should have a blank document named “local.lua”. Depending on your computer’s configuration, the LUA file type may not be recognized. If double-clicking the file does not open it with Notepad, then right-click on local.lua and select Open With… > Notepad.

Now let’s start our mod loader. First, let’s set a boolean (true/false) variable that determines whether mods are loaded when Painkiller is run. Enter the following line into the local.lua document:

ModLoader = true

Now press enter to start a new line in the document, then type in the following line:

if ModLoader then

What the above line means is this: “If the ModLoader variable is true, then perform all the following lines of code until the ‘end’ line is reached.” Now we will insert our mods, also as boolean variables. I will use the HUDmod and Powermad mods as examples:

HUDmod = true
Powermad = true

So, if ModLoader = true, then the HUDmod and Powermad mods will also be set to true. If ModLoader = false, then the above lines are skipped, which means that the above mods will default to false.

Once you’ve entered lines for each mod, enter the following line to end the ‘if ModLoader then’ statement:

end

That concludes the first half of the mod loader. Simple, isn’t it? Now we will add lines code which will load these mods if they have been set to ‘true’. For each mod you will need AT LEAST these lines of code:

if MODNAME then
FS.RegisterPack(“../Data/Mods/MODNAME.pak”, “../Data/”)
end

Replace both instances of MODNAME above with the name of the mod.

Notice the path to the mod’s PAK file- make sure that the PAK file is located where the path is set to (paths begin in the Painkiller folder). The above example is set to check within Painkiller’s Data/Mods folder (which is where I place my mods), but you can change it if you want to.

Also, make sure that the name used for each mod matches the name in the top section (where the mod variable was set to true or false).

This is all you need to do for mods which do not contain any LUA files themselves. If the mod does contain LUA files then additional code must be added. Look at the following example:

if HUDmod then
FS.RegisterPack(“../Data/Mods/HUDmod.pak”, “../Data/”)
DoFile(path..”Main/Cfg.lua”)
DoFile(path..”HUD/Menu/Options/HUDConfig.lua”)
DoFile(path..”HUD/HUD.lua”)
end

Notice that after the FS.RegisterPack line there are 3 DoFile lines. Each of these DoFile lines will load a LUA file from within the mod’s PAK file. Also notice that the paths are different- instead of starting at the Painkiller folder, DoFile paths begin in the LScripts folder (within Painkiller’s data folder).

Each mod may contain a different set of LUA files (or none at all). In order to add the proper DoFile lines you must know which LUA files are in the mod’s PAK file. You can’t see these files until you extract the PAK- for a guide on how to do this click here.

Once you’ve extracted the PAK check to see if there is an LScripts folder in the extracted contents- if there is, add a DoFile line for each LUA file within the LScripts folder (taking care to preserve the path structure).

That’s it- you’ve just created a simple and effective mod loader!

Save your finished local.lua file and place it in Painkiller’s Data/LScripts folder (go ahead and create the folder if it doesn’t exist). Now Painkiller will automatically load the file each time the game is run.

A Note For Powermad Users

I’ll make it easy for powermad users… the powermad mod only requires a single DoFile, “powermad.lua”. This file is located in the LScripts folder, so the path is left blank (since DoFile paths begin at the LScripts folder). The resulting complete loader code looks like this:

if powermad then
FS.RegisterPack(“../Data/Mods/powermad.pak”, “../Data/”)
DoFile(path..”powermad.lua”)
end

Make sure to either put powermad.pak in the Data/Mods folder OR change the above path to match the location of powermad.pak (it defaults to the LScripts folder).

Using the Mod Loader

To disable all mods: Change the ModLoader variable (in the very first line of local.lua) to false. That’s all you have to do. This allows you to load Painkiller mod-free without having to actually uninstall any mods.

To load specific mods: Leave the ModLoader variable as “true” and just change the true/false values of the mods individually. Only mods set to “true” will be loaded.

To add support for a new mod: Add a variable for that mod (in the format MODNAME = true) and then add the necessary loader code. The variable should be placed after the “if CustomLoader then” line but before the first “end” line. The loader code must be placed after the first “end” line. Also, take care not insert a mod’s loader code in the middle of another mod’s loader code- each loader code must flow from it’s “if MODNAME then” line to it’s “end” line without interruption.

To remove support for a mod: Delete that mod’s variable and loader code.

Creating PAKs From Any Mod

The mod loader is perfect for mods in PAK format, but not all mods come this way. Many mods come as a collection of files or an installer. Well, regardless of the mod’s format it can be converted to PAK format so that it can be used with the mod loader. For a basic guide on how to do this click here. I will not be covering the basics, instead I’ll focus on some more advanced aspects of creating a PAK file.

Music and movies files will not work from within PAKs- Painkiller’s Data folder has Music and Movies folders for a reason. These types of files should go into their respective folders and not into the PAK file itself. Generally this only comes into play when creating PAK files from custom singleplayer levels. As far as I know, no current Painkiller mods come with any movie files.

Mods that have their own separate launcher (such as the singleplayer custom level “Hills”) will require some picking and choosing over which files to keep in the PAK. Basically, you will want to take out any custom menus and redundant files so you can splice the mod onto the main game using the mod loader. I will update this guide with more details about this in a future update.

A Note For Future Mod Makers

If you plan on releasing a mod as a PAK file, it might be a good idea to contain the required mod loader code in a readme for that mod. This way users that want to use this mod loader method can just copy and paste the required code instead of having to extract the PAK, determine DoFile paths, then repackage your mod.

You could also create an installer for your mod which asks the user “are you using the local.lua file to load mods?” If the user picks no then the installer creates a simplified local.lua file which contains only the loader code necessary for your mod. If the user picks yes, then the loader code is provided- something like “Paste the following code into local.lua to add support for this mod”. This is the method which I use for my mods.

An alternative solution is to have a “Mod Loader Codes” database online (perhaps here at PKZone.org) which all mod makers can add their loader code to- a user would just have to check the database to find out the necessary loader code for any mod.

Either way, it is important not to force your mod to create a local.lua file… if the user has created their own mod loader then you don’t want to inadvertently overwrite it.

Hopefully this guide has also convinced some of you that mods in PAK format offer a lot of benefits over loose-file-and-folder mods (for both users and mod makers alike).

Happy modding!

~ Leviathan

Background story:

There is still war in America. Accidentally, a secret weapon was released, and everyone died in the area. Soon, a gate from hell opens in one of the command enters, which had been a museum before. An evil creature, a demon stepped out from the portal. He came to collect the souls of the innocent, nothing could stop him.. but others were also interested in this job, and followed him through the hellgate.
They’re just waiting to attack..

Lead your demon to victory, collect all innocent souls, and fight the opponent demons who want to steal the souls you have collected!

—TIPS—

In this level, you don’t have the soulcube in your hand. Reserve your ammo!

Try to find secrets to earn more ammo. Look also for secret door openings!

Watch out for explodable boxes and barrels!

For more details, read the text in the zip file.

Related links:

• Sviatoslav’s channel
• Topic about the mod (russian language)
• Alternative trailer (other music)

This is a part from an upcoming mod that I’m working on with HV, called
Light-Bearer. We hope that we will finish it soon. I just had the idea to
release those maps which are ready to play.

The original maps are:

- DM_Umbra
- DM_Gloomy
- DM_1on1_HydeDM

Other details are included in the readme file.

A helpful package is available for these maps, where you can find those
pictures which will help you to find the secrets, and some useful hints.

Thanks for downloading, have fun!