Re: Best Quake control configuration setup?

Article View: alt.games.quake2

Article #283584

#283584

From: InfoServ
Date: Mon, 04 Jan 1999 00:00

22 lines
1556 bytes

Hi,

Actually, I like to setup Quake's control keys just like Duke Nukem's.  I've
done a lot Dukematching, so I'm very well used to the way Duke Nukem's
control keys are setup.  They're pretty basic, but it makes everything
readily available.

Up arrow = forward
Down arrow = backward
Left arrow = turn left
Right arrow = turn right
A = jump
Z = crouch
Left control key = fire weapon
Left Alt key = strafe
Home key = look up
End key = look down
Page down = center view

This allows me to keep my hands on both sides of the keyboard.  The rest of
the control keys I leave with defaults.  Try it sometime.  It's pretty cool.
:-)

Technical Details

Message-ID: <369149e6.0@news.compuvar.com>

Path: mbox-mo1.pugleaf.net!unknown!not-for-mail

References:

<36892e9d.24563314@news.u.washington.edu><769h70$sij$1@remarQ.com> <Gg7FU6AgH9i2EwDT@harriben.demon.co.uk><915135279.205219@f1.andara.com> <3guJEDA049i2Ewlc@harriben.demon.co.uk> <76jaqr$lhh$1@news4.wt.net> <hawwk-0201992250510001@usrts2m8.uwinnipeg.ca>

Show Full Headers

Complete Article Headers

From: "InfoServ" <info...@1stnational.com>
Subject: Re: Best Quake control configuration setup?
Date: 1999/01/04
Message-ID: <369149e6.0@news.compuvar.com>
X-Deja-AN: 428800205
X-NNTP-Posting-Host: 207.211.230.20
References: <36892e9d.24563314@news.u.washington.edu><769h70$sij$1@remarQ.com> <Gg7FU6AgH9i2EwDT@harriben.demon.co.uk><915135279.205219@f1.andara.com> <3guJEDA049i2Ewlc@harriben.demon.co.uk> <76jaqr$lhh$1@news4.wt.net> <hawwk-0201992250510001@usrts2m8.uwinnipeg.ca>
X-Trace: 4 Jan 1999 15:08:22 -0800, 207.211.230.20
Newsgroups: alt.games.quake,alt.games.quake2,alt.quake2,de.alt.games.quake,rec.games.computer.quake.editing,rec.games.computer.quake.misc,rec.games.computer.quake.playing,alt.games.half-life,alt.games.unreal,alt.games
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Reply to Parent Message