🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.games.diablo
Article #284

Suggestion to keep battle.net FUN for all!

#284
From: nice... Ian Mercado
Date: Wed, 22 Jan 1997 00:00
30 lines
1761 bytes
I just sent this e-mail to sup...@blizzard.com.  This may have
already been discussed, in one of these groups, but since my feed
isn't the best out there, I figured I'd post it anyway.  Any comments
or additions you guys may have are welcome.  I'd hate to see
battle.net become a place to avoid because of an abundance of pkillers
and cheaters that are beginning to swarm over the place.


To sup...@blizzard.com:

"Seems like you guys should come up with some kind of game creation
options (as is done in Descent I and II) that allow a person to
specify parameters for a game, like whether pkilling is allowed, what
level range of characters are allowed to play, whether or not
characters can bring weapons/armor/spells into the game, whether or
not they can leave with them, etc.

"This would give multi-player Diablo an entirely new dimension which
the game-creator can control.  It would also help to numb the effects
of the pkillers/cheaters that are destined to shortly make battle.net
a no-fun place to be.  It would also still place no "burden of proof"
on the battle.net servers for tracking attributes of characters.

"This is a fantastic game, and I hope you guys are willing to put in
some extra effort to ensure that its multi-player appeal will last for
a long-long time!"

Ian
(NiceGuy)
Technical Details
Message-ID: <5c57q5$3cc@lendl.cc.emory.edu>
Path: mbox-mo1.pugleaf.net!unknown!not-for-mail

Show Full Headers
Complete Article Headers
From: nice...@worldnet.att.net (Ian Mercado)
Subject: Suggestion to keep battle.net FUN for all!
Date: 1997/01/22
Message-ID: <5c57q5$3cc@lendl.cc.emory.edu>
X-Deja-AN: 211459167
organization: Emory University
newsgroups: comp.sys.ibm.pc.games.action,comp.sys.ibm.pc.games.rpg,comp.sys.ibm.pc.games.adventure,alt.games.diablo
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit