🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.games.quake3
Article #286716

small vs. big Player-Models

#286716
From: Paul Schmidinger
Date: Fri, 06 Oct 2006 08:42
17 lines
1546 bytes
Hello,

maybe the questions seems stupid to the more experienced players, but here 
it is:

Concerning die "hit-detection" of quake, it would seem logical that big 
models (as Tank Junior) can be hit more easily than smaller models (as the 
orb). Is that correct? And if yes, does the engine do anything to compensate 
this (dis)advantage? (My guess is "yes" and then "no", due to my experiences 
with a tiny penguin-model as a bot)

I'm just curious, I do not intend to to choose the models depending on the 
answer to maximize my "advantages".

Kind regards,
Paul
-- www.eigelb.at 
Technical Details
Message-ID: <6d5a4$452616d8$c2d0233c$30742@nf5.news-service.com>
Path: mbox-mo1.pugleaf.net!number1.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!t-online.de!feeder.news-service.com!post.news-service.com!nf5.news-service.com!not-for-mail

Show Full Headers
Complete Article Headers
Path: mbox-mo1.pugleaf.net!number1.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!t-online.de!feeder.news-service.com!post.news-service.com!nf5.news-service.com!not-for-mail
From: "Paul Schmidinger" <email.on.website.nospam@eigelb.at>
Newsgroups: alt.games.quake3
Subject: small vs. big Player-Models
Date: Fri, 6 Oct 2006 10:42:03 +0200
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-RFC2646: Format=Flowed; Original
Message-ID: <6d5a4$452616d8$c2d0233c$30742@nf5.news-service.com>
X-Complaints-To: abuse@news-service.com
Organization: newssurfer.de
Lines: 19
NNTP-Posting-Host: 194.208.35.60 (194.208.35.60)
NNTP-Posting-Date: Fri, 06 Oct 2006 10:42:00 +0200
X-Trace: 6d5a4452616d86775869930742
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit