Money making guide/Killing Vorkath (Toxic blowpipe)
Lua error in ...ribunto/includes/Engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil). The listed profit rate assumes kills per hour, but up to 28 is possible with maxed stats and gear. Your expected profit will vary depending on your kills per hour.
For overall boss strategy, please see the strategy page for Vorkath.
As special attack energy is required for this setup, please note that it is required to have at least a Restoration pool or similar form of special attack restoration - the Clan Wars FFA portal does not regenerate special attack energy. If you lack a pool in your own POH, it is necessary to use someone else's to be able to maintain a consistent kill rate, though using someone else's POH will result in much longer delays between trips and therefore much less profit.
Before the fight starts, equip your melee gear with a Bandos godsword equipped and use the special attack on Vorkath with Piety and Protect from Magic active. If aiming for multiple kills per trip, using one spec initially may be ideal to save special attack energy; otherwise, use two. Even if at the start of a new trip both specs miss or hit very low, it usually isn't faster to teleport out and restart with full special attack energy.
After landing the special attacks, equip your range gear and pray Protect from Magic and Rigour. Protecting from Magic is necessary to prevent dragonfire damage from Vorkath; unfortunately, with the blowpipe strategy, range damage must be tanked and will be a primary source of damage intake per trip.
You should expect 1-4 kills per trip, limited by food, although up to 4-5 is possible. It is advisable to reserve special attack energy for successive kills, as long as supplies are high, as more kills per trip generally translate to more kills per hour and profit.
See also
All prices on this page are cached, meaning they may be out of date.
To force a new cache of this page, click this link.
If a money making method is out of date, you can edit it or leave a message on the talk page.