🚀 go-pugleaf

Ashley Dunn <asd...@nytimes.com> wrote in article
<01bc21a7$c03cdb00$d265...@dpc101210.direcpc.com>...
> Just curious how many times other people have been killed by rogues and
> sorcerers. Everytime I play with a rogue I get shot repeatedly in the
back.
> When I was a warrior I was zapped several times by sorcerers. These
weren't
> pkillers, just crummy players. It's really aggravating. I am a 39th level
> sorcerer. I usually play with a 39th level warrior who can take almost
any
> hit, but I have to admit i've come very close to killing him a few times.
> Getting killed by friendly fire is almost as aggravating as getting TK'd
or
> PK'd.
> 
> 
It isn't that bad.  If you're playing in a friendly game, someone who
killed you with friendly fire is pretty likely to res you and not steal
your stuff.  Friendly fire is usually an accident, and if you play as a
warrior and get killed overmuch by it, it means that you're probably
running in front of the other players while they're shooting.  You may get
with an overzealous mage on occasion, but a decent player will res anyone
he (or she) kills by accident.  Hell, if I do it, I try to give the other
guy something for his trouble.  Not much, say a full heal potion or
something, but there's no point in pissing the other players off.  Don't
get so worked up about it, just tread more carefully and let the other guys
have their kills.  

BTW, Anyone else discouraged by the new Diablo Wear patch?  The author has
singlehandedly ruined what little economy remained in Diablo...sure, you
could dupe stuff before but now there's little purpose to go hunt for that
King's Sword of Most Heinous Whup-Ass.  Blizzard should forget Starcraft
for a few weeks and fix Diablo (can't do much about the items, but why not
fix that $@^*ing TownKill problem?  Or better yet, why not make it
impossible for players to kill each other!  True, you couldn't avenge the
stealing of items then, but what's the point?  You can get a new one in
fifteen seconds if you want.

-Caramon

> fix that $@^*ing TownKill problem?  Or better yet, why not make it
> impossible for players to kill each other!  True, you couldn't avenge the
> stealing of items then, but what's the point?  You can get a new one in
> fifteen seconds if you want.
> 
> -Caramon
 
Bad idea.  Then there could be no duels (and those can be fun between
non-cheaters) and it would be too easy to do multiplayer cooperative. 
Where would be the challenge if a warrior could kill things while a mage is
using chain lightning?  Better yet, what if that warrior is walking through
a fire wall cast by the mage mopping up the weakened creatures?  Player
killing is a nescesary part of Diablo, it's just the cheating that makes it
annoying.

Kilgar
 
 

>Just curious how many times other people have been killed by rogues and
>sorcerers. Everytime I play with a rogue I get shot repeatedly in the back.
>When I was a warrior I was zapped several times by sorcerers. These weren't
>pkillers, just crummy players. It's really aggravating. I am a 39th level
>sorcerer. I usually play with a 39th level warrior who can take almost any
>hit, but I have to admit i've come very close to killing him a few times.
>Getting killed by friendly fire is almost as aggravating as getting TK'd or
>PK'd.
>

Well I am a Rogue and have learned to use a more controlled approach
to combat.  My 31st level Rogue does about 100 points of damage with a
single arrow.  I don't start autofiring my bow like crazy at the
monsters.  I basically let them come to me.  And as they get closer I
use precise point & fire tactics.  They go down easy, and it saves me
the walk for the loot!  When I play with a warrior.  I play off the
Warrior.  He tends to get surounded most of the time because he has to
make contact with his enemy.  I lock a target next to him and click
off a single shot.  NOT multiple hits.  This is the key.  It is very
likely the single shot kills the creature, any additional arrows smack
into the Warrior.  If the first shot doesn't do it fire a second.  But
using calm single or double shots.  Is alot more effective than the
"fully automatic" bow.  I only rock&roll when i'm surrounded.  I try
to pick off the guys behind the first line of attackers.  I let the
Warrior handle the front line.  I remove the re-inforcements.  Don't
panic in combat.  Death is nothing.

Sorcerers however are alot more dangerous with thier nova spells and
flame wave and wall of fire.  too many times I had to kill an over
zealous sorcerer, because he was popping off flame waves while I'm in
the lead.  Duh.  I can't count the times they trapped me in a room of
monsters beacuse they cut off the exit with a wall of fire.  Or the
number of times I barely slipped around a corner just in time to evade
several waves of the nova spell.  I charge into a room and he follows
by tossing in a few grenades after I 'm inside?  I just stay behind
the idiots and cover them or most times take off and head for separate
areas to clear out.

Most of the time if the players are decent and have any real time
gaming experience.  They can generally work as a good team.  Remind
each other of your combat prefrences, and switch leads back and forth.
for an even chance.   I have heal other hot keyed, and use it
frequently during intense combat.  

And another thing,  Don't stand in the doorway if someone goes into
the room ahead of you.  this blocks thier exit.  Either back two from
the door or come inside.  It is quicker to kill you to get you out of
the way, then to stop and type "Get out of the way, Diablo is right
behind me"  The trick is to never stop moving.

See you in hell.
And stay out of the corners.

Damn, now I gotta go play Diablo.

On Fri, 28 Feb 1997 20:18:02 GMT, wm...@execpc.com (Tony T) wrote:


>Why not have it a mutual choice; i.e., if you dont MIND being attacked
>be idiot players, switch it on.
>
>If you want to play the way it was meant to be palyed, switch it off.
>
>simple.

That wouldn't really be too good. You see, people will use this as a
"cheat" in duels. One could just swtich it "off" when he is about to
die.
                           
                           ////////////////////////////////
                           /// CodeName: AcCeSsDeNiEd  ///
                          ////////////////////////////////