What is the best/easiest client for regular Quake Servers

[gandalfnet]

Hey guys,

help get me up to speed, people are trying to connect to quake.trinicom.com with ezquake and I downloaded it only to find it seems to be quake world only.

Also, can anyone point me to a "dummy's" guide to setting up your quake client and firewall settings.

I sent people to quake one and most get it together quickly but there is a lot of intrest from the non techical players on FB who want to jump in again and play, but do not have (or remember) the details

Cheers
Gandalf

[Syluxguy28O3]

proquake.

[Mindf!3ldzX]

^ what he said. I would never bother to fiddle with QW anything, just don't see a point starting now, in 2013 ;p

Stick to NetQuake / newest ProQuake as server client ~ read about it here

http://quakeone.com/news/site-news/8...phase-1-a.html

Baker is now the author of modern ProQuake anything.

[Mr.Burns]

Hi Gandalf

Paraphrased from a recent QuakeOD article....
Normally I would suggest that non technical players get something like Proquake working first and then move on to the more Eye Candy rich clients as and when they feel the need. The reason behind this is that

a) Proquake is a mature client and is usually rock solid,

b) it is relatively well supported by Baker.

c) later versions have had significant work put in to it by the mighty Baker including network fixes, stability improvements and so forth.

d) in my experience PQ seems to be compatible with almost anything.

e) Installation is normally a case of downloading it from this site and place the executable and associated files in your quake directory structure and then fire it up with something like the following in your command line:

glpro.exe  -ip n.n.n.n -noipx -width 640 -height 480 -bpp 32 -winmem 128 -game proquake

Let's have a look at the above to see what we are actually doing here:
glpro.exe is the name of the relevant quake executable you wish to use
-ip n.n.n.n is the internal Ip address of the gaming PC. This is not strictly necessary but if they are connecting through a NAT'd firewall this can sometimes solve issues.
-noipx Simply tells quake that we do not wish to use the IPX/SPX protocol
-width 640 -height 480 sets the screen resolution for the game
-bpp 32 sets 32 bits per pixel
-winmem 128 tells Quake to reserve 128 meg of memory in which to run. I seem to recall that this has been deprecated and heapsize is the preferred option (eg. -heapsize 131076)
-game proquake tells the quake engine to use whatever files are in the Proquake folder. Initially there probably wont be much content in the folder but once you first run Proquake it will create its config files in there and can help to keep things separate if you run different clients with different settings. This is normally a setting used with mods but iin this scenario it is optional

Normally that's it and you are up and running and typing connect MyQuakeServer.com normally gets me in to the nearest server.

I'm sure that some of the experts here (such as Rook, Baker, Spike, MH) will come up with better solutions but this is just what works for a relative newb like me and I hope it helps others

Kind regards

Monty

[powerzord]

Try win quake or q95.bat

[foq]

Use the latest version of wqpro for hosting a server.

The command line should look something like this:

wqpro.exe -dedicated 16 -game ctf -mem 128

If running multiple servers, you will need to add -port as well. By default the server will run on port 26000, so if you're going to run a second server along with that one, you would add -port 26001. Use -game to tell the server what mod to load. If you're running a CTF server, you may have your CTF mod files in a folder called ctf, so use -game ctf. Any server variables, such as any aliases you may want to write up for whatever reason, sys_ticrate, hostname, rcon_password, etc should be set in the autoexec.cfg file, which would be in the appropriate folder you set earlier with -game.