🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.games.warcraft
Article #120661

Re: Levelling on a PVP Server

#120661
From: Babe Bridou
Date: Fri, 12 Aug 2005 09:29
43 lines
3239 bytes
Christian Stauffer wrote:
> "chocolatemalt" <chocolatemalt@dim=dot=com.invalid> wrote:
>
> > My feelings exactly.  Currently anyone lvl < 47 is shown as grey to a
> > lvl 60 -- I think it would be reasonable to make everyone lvl 40-47
> > normal "grey" to a lvl 60, just as it is today (or more generally,
> > anyone 13-20 lvls below you) and this means no HK or DHK.  Anyone more
> > than 20 lvls below you could be represented as a darker shade of grey,
> > and have an accelerating DHK associated... a lvl 60 killing a lvl 39
> > would get 10 a cont pt penalty, a lvl 30 would be 100, lvl 20 would be
> > 200, etc... the numbers might need tweaking, but I think the concept is
> > solid.
>
> One word: Raids.
> Babe wrote DHKs would be abused, and believe me: He's right.
> I HATE it to get killed in a fight where I have no chance, but
> the software can't tell when this is the case and when not.
>
> > The current system doesn't encourage "sport", just rotten behavior.
>
> Implement DHKs, and you will see level 60s running from a zerg of
> lower levels.
>
> > I
> > suspect Blizzard was worried about exploits and mechanics, and if they
> > get that ironed out then we will indeed see a discouragement of
> > hypogonadism in uber players.
>
> Good luck. I thought a lot how algorithms should look like that figure
> out when a fight between a level 60 and a level 30 is fair game and
> when it should be punished, and I haven't found an answer yet.
>
> Chris

Moreover pit a lone level 60 warrior in front of 50 level 20s and see
who wins in the end.

No way the 60 should get any dishonourable kills there. He should be a
hero for surviving.

Considering a single level 60 has little to no chance against 5 level
40s, again, I'm strongly opposed to DHK mechanisms in PVP.
Technical Details
Message-ID: <1123838987.220699.100610@g44g2000cwa.googlegroups.com>
Path: mbox-mo1.pugleaf.net!number1.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nx01.iad01.newshosting.com!newshosting.com!news.glorb.com!postnews.google.com!g44g2000cwa.googlegroups.com!not-for-mail
References: <ddaoj1$coj$1$8302bc10@news.demon.co.uk> <ddcs8k$1ur$1@news5.zwoll1.ov.home.nl> <1123683564.973957.143560@g43g2000cwa.googlegroups.com> <chocolatemalt-199BCD.11345410082005@news.isp.giganews.com> <42fa76e2$0$19402$c3e8da3@news.astraweb.com> <nILKe.413$O07.257@newssvr23.news.prodigy.net> <chocolatemalt-E1469E.13554511082005@news.isp.giganews.com> <42fc6864$0$1164$5402220f@news.sunrise.ch>

Show Full Headers
Complete Article Headers
Path: mbox-mo1.pugleaf.net!number1.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nx01.iad01.newshosting.com!newshosting.com!news.glorb.com!postnews.google.com!g44g2000cwa.googlegroups.com!not-for-mail
From: "Babe Bridou" <babebridou@hotmail.com>
Newsgroups: alt.games.warcraft
Subject: Re: Levelling on a PVP Server
Date: 12 Aug 2005 02:29:47 -0700
Organization: http://groups.google.com
Lines: 44
Message-ID: <1123838987.220699.100610@g44g2000cwa.googlegroups.com>
References: <ddaoj1$coj$1$8302bc10@news.demon.co.uk> <ddcs8k$1ur$1@news5.zwoll1.ov.home.nl> <1123683564.973957.143560@g43g2000cwa.googlegroups.com> <chocolatemalt-199BCD.11345410082005@news.isp.giganews.com> <42fa76e2$0$19402$c3e8da3@news.astraweb.com> <nILKe.413$O07.257@newssvr23.news.prodigy.net> <chocolatemalt-E1469E.13554511082005@news.isp.giganews.com> <42fc6864$0$1164$5402220f@news.sunrise.ch>
NNTP-Posting-Host: 159.50.203.8
Mime-Version: 1.0
X-Trace: posting.google.com 1123838994 19465 127.0.0.1 (12 Aug 2005 09:29:54 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Fri, 12 Aug 2005 09:29:54 +0000 (UTC)
In-Reply-To: <42fc6864$0$1164$5402220f@news.sunrise.ch>
User-Agent: G2/0.2
Complaints-To: groups-abuse@google.com
Injection-Info: g44g2000cwa.googlegroups.com; posting-host=159.50.203.8; posting-account=HISiDQwAAAAWH958dce_yC6xy21dfOql
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit