#PROJECT BRUTALITY DUAL WIELD HOW TO#
#PROJECT BRUTALITY DUAL WIELD DOWNLOAD#
#PROJECT BRUTALITY DUAL WIELD FREE#

REVI A 1 A_WeaponReady(WRF_ALLOWRELOAD | WRF_ALLOWZOOM) Setting these two flags on WeaponReady allows us to trigger a reload or grenade ('zoom'). TNT1 A 0 A_PlaySound('weapons/rifle/clip')

Ready plays the draw animation then falls through to ReadyLoop. We deal with taking ammo manually - these ammo type properties are just here so that the ZDoom HUD highlights them. Inventory.Pickupmessage 'Now you'll see why they call me Revolver!' Inventory.PickupSound 'weapons/rifle/clip' Obituary '%o was revolved by %k's revolver.' Standard weapon properties - put it at the end of slot 2. To avoid conflicts with files from other projects when they're merged together, I name the file extension after the project - ZDoom doesn't care about the extension and will pick it up as a DECORATE lump regardless. Then we create our parent DECORATE lump, which will go in the root project folder and will just refer to the pistol's dedicated file. The sprites can all be dumped into the sprites/weapons/revolver folder - we don't need to change any of them.

#PROJECT BRUTALITY DUAL WIELD DOWNLOAD#

In this example, the folder that will contain our pk3 contents is 'extension-example-pk3' - a copy of this is available in the PK3 Tools download above. Using a folder structure like this for a PK3 that just contains a weapon would normally be a bit of an overkill, but it makes things consistent with how the weapon files are laid out in BDLite so that when the files are combined everything is in the right place.

#PROJECT BRUTALITY DUAL WIELD FREE#

The project root directory is then free to fill up with works in progress, graphic source files and miscellaneous other garbage. We start off by laying out our PK3 folder - I usually create a folder per project, then a 'pk3' folder under that which will contain what we want to be packaged into the PK3. You could also get the player to load the separate PK3s one after the other or provide a batch file to do it, but I prefer to hand the player one unified PK3 for a project.ДЇor this miniature project example, I'll use the revolver sprites from Project Brutality, because this weapon has all the states I need (crucially, the reloading sprites).

#PROJECT BRUTALITY DUAL WIELD HOW TO#

Given its nature Project Brutality is never easy, but starting out with such weapons will significantly reduce the difficulty for a good portion of the level set.Over on the ZDoom forum, TheEternalStruggler had a request for a pistol weapon, so I'll show how to add one on top of BDLite by creating a project on top! You could equally just go in and add all this to the PK3 as it is, but this guide will demonstrate how you can build on top of BDLite by defining any extras you need and then merging the projects together. You know, the one that can shrink enemies to the point you can squish them under your boot or possess them to fight for you. ** Rarely, this can cause enemies with the Hell Rifle to spawn in the first level.

This has been averted in the latest builds of Project Brutality 3.0 where the HMG has been replaced with the Nailgun. In previous versions of Project Brutality in which Possessed Commandos utilised a Heavy Machine Gun, the weapon hurts more per-bullet than every other machine gun in the game you still needed the minigun occasionally for the sheer volume of fire, but there was little reason to use the other repeating weapons once you acquire the big gun. * DiskOneNuke: Given the variety of enemy spawns and spawn mutators, it's perfectly possible to fight soldiers wielding the more traditionally late-game guns in the first level and loot them off of their deceased owners.

Project brutality dual wield