     <>

Diablo II v1.09b
Diablo II: Lord of Destruction v1.09b

Anti-PK Guide
by M. Fitzpatrick
krusader at starmail dot com
Release 1: Sat 03 Nov 2001

     <>

Introduction

     In this new day and age, massively multiplayer online games enjoy a broad
player base: from across national boundaries and age generations we can all
enjoy common interests through Internet gaming.

     But with this broader and broader player base each year, an exponentially
increasing problem arises: how to safeguard those who choose to be cooperative
in their play from those who enjoy being malicious and destructive against
others.

     Though Blizzard has made great leaps from Diablo to Diablo II in terms of
limiting PK-- player killing or player killers-- and protecting those who do
not wish to partake of it, there remain gaps that malicious users can and will
exploit.  The best defense against these exploits is knowledge, and so this
guide begins:

     <>

Player Killers: Who, Why, Where?

     Player killers are rampant on battle.net: ask anyone.  Expansion or
classic, hardcore or not, they're everywhere.  To complicate the problem, the
largely adolescent playerbase is almost universally unsympathetic to those who
are PK'd: in their words, anyone who gets PK'd is an idiot and completely
deserved it, and even non-PK's will tell you so to your face.  Indeed, chances
are I'll receive a few nasty emails calling me a whiner just for writing this.
So it goes; it's a jungle out there, and I get enough spam already not to care.

     There are statistical tendencies, of course.  High-achieving characters
are likely to be long-standing player killers; nearly half of the top ladder
spots will belong to PK's at any given time.  PK favors straightforward, high-
damage classes over more complex ones: thus, sorceress is the favored PK class,
followed by barbarian.  And-- apologies to the American crowd, but the USWest
and USEast realms tend to be loaded with larger concentrations of PK than
the Europe and Asia ones.  While morning players enjoy friendly and helpful
company, evenings and weekends U.S. time are prime hours for PK.

     However, regardless of these tendencies, care must always be taken, in
every game, especially hardcore.  Why?  Common sense might dictate that PK's
would avoid hardcore, but this is entirely untrue.  Players are too safe in
non-hardcore games... without corpse looting allowed in any form, the loss to
PK is limited to death's toll: 25% of gold on hand and in storage.  On the
other hand, the potential loss in hardcore is grave indeed, and this is
precisely what attracts and drives malicious personalities.  Hardcore players
beware, and read on:

     <>

The Hermit Method

     Diablo II offers better player security than similar multiplayer games
(notably Phantasy Star Online) and so playing only password-locked games with
trusted friends is an unattractive and unnecessary solution, even for hardcore
players.  There's value, of course, to gaming with online buddies exclusively,
but this guide will concentrate more on other methods to avoid PK.

     <>

The Backup Method

     This method, popular since the original Diablo, remains a good way to
protect oneself, though only for non-realm (that is, open) characters.  Regular
backups of the player information files can greatly reduce the (small) losses
PK can inflict upon open characters.  For utilities that can accomplish this,
consult www.planetdiablo.com's Files section: a backup tool as well as other
useful downloads are offered there.

     <>

Basic Precautions

     Be distrustful of high-level characters you don't know joining your game
alone.  If somewhat-high level characters join in a group, they're probably
looking to run the secret level, but a single 50+ character joining a normal
game is suspect.

     Don't accept favors, party with, or even play in the same game with known
PK's.  No matter how smart you think you are, PK's know more tricks to kill you
than the average player can imagine.  Though I'll try to keep this document as
up-to-date as possible, a decade of Internet use should have taught the world
one thing: never underestimate a malicious user's ability to get to you.

     You're completely safe while in town; you're completely vulnerable while
out of town.  Remember this.  Don't step away from the game without going back
to town first, no matter how deep in the dungeons you are.  The reason for this
is:

     <>

PK Exploit One: Map Hack

     The map hack, a trainer-like utility which modifies a user's interface,
is popular because it makes the more irritating levels in the game more
manageable.  Entire maps, monster locations, and player locations are available
at a glance.

     In the hands of a PK, however, it becomes a dangerous tool to hunt down
unsuspecting players and kill them.

     When you hear the Hostile warning, always assume the PK already knows your
precise location.  Being far from town and any waypoint-- deep in a dungeon,
for instance-- gives you some time before the PK can reach you, but never think
you're too well-hidden to be found.  The map hack sees across acts, across
areas, everywhere.

     <>

PK Exploit Two: Waypoint Ambush

     Blizzard did well to make Hostile mode available only while in town, but
care must still be taken: PK's have learned to enable Hostile and traverse
waypoints very quickly.

     If you're a large distance from any town access point (waypoints, town
gate boundaries, and-- take note-- Act 2 sewer entrances), you may safely
create a town portal, return to town, and wait it out.  However, anytime you
are near a town access point, be prepared to quit the game immediately upon
hearing the Hostile warning.  Again, assume the PK knows exactly where you are,
and can get to you in an instant.

     In Windows, Alt-F4 is the best method for escaping ambushes of this type:
most Windows users are familiar with the keystrokes already, and it'll drop
your character from the game immediately.  Exiting normally through the menu is
also an option, if you're quick.

     <>

PK Exploit Three: Fire Ambush

     If a sorceress, while in the same party or neutral, lights a fire wall
beneath you or raises hydras around you, it won't hurt you.  However, if she
uses a town portal, the fire wall and hydras stay lit, and if she goes
hostile-- well, you guessed it.

     PK's who use this ambush will usually ask you a question before opening
the town portal to distract you, or be partnered with someone else who'll
distract you-- sounds crazy, but it has happened.  If you must type a
response, open a portal and do it in town.

     <>

Summary

     * Watch out for a high-level character in a low-level game.
     * Avoid known player killers.  If a known player killer joins your game
or goes hostile with anyone else in your game, quit the game or wait for them
to leave.
     * Take breaks in town, and only in town.
     * When you hear the Hostile warning, be paranoid: assume the PK is after
you and nobody else, will kill you in one hit, knows precisely where you are,
and will reach you with the fastest means available.  More often than not,
you'll be correct.  Open a portal and return to town immediately.
     * Be extra cautious when close to a town access point (waypoints, town
boundaries, and Act 2 sewer entrances): be prepared to strike Alt-F4 rather
than open a portal, because a PK can reach you instantly.
     * Be cautious to an extreme when grouped with a fire-using sorceress you
don't trust: don't become distracted for any reason.  If she opens a town
portal while a fire wall or hydra is still lit, you have to hit Alt-F4 even
before she enters it.  Once she does enter it, you're one click away from
being dead.
     * Spread the word!  Perhaps Blizzard will close these exploits, like
they did, thankfully, with the former Town Portal Ambush in 1.09... perhaps
not.  Either way, until then, protect yourself and protect your friends:
there's no way to avoid falling victim to these exploits unless you know
they exist.

     <>

Contact

     My email account isn't reliable-- should an attempted email to krusader at
starmail dot com bounce, you may use my business account, mattfitz at oco dot
net.  Please identify this guide in the subject of your email so I know it's
important.  All contributions, clarifications, questions and concerns are
welcomed and appreciated-- I'll be happy to credit you in the next update!

     <>