Differences between Q1, Quake World and Net codebases (qc)

[JasonX]

edit by Spirit: This thread was taken over by offtopic arguing, please see the forked new thread at viewtopic.php?f=9&t=4850
-----


What is the difference between the QuakeC codebase of Quake, Quake World and NetQuake?

[leileilol]

Quake's a dumb client.
Quakeworld is not. It tries to extrapolate from what it recieves instead and relies more on broadcast messages.

Also Quakeworld generally strips a lot of things, so if you love particle() and punchangles, you're going to have to adjust.

[Dirge Inferno]

[r00k]

Dumb meaning its not intelligent in terms of latency prediction. Though, it's all i've used for quake1. Since movement/shots fired are sync'd u dont seem to notice much sub 50 ping. In QW u can run around like a freakin hippy at a nudist colony but have to wait for latency to get your shots out, which seem to come late but hit direct, something odd about that gameplay. QW mods though are WAY behind the times. CTF is not active and CA uses 1997 code bluh plain f'ugly.

EDIT: KTX is not a QuakeC mod, so this is the exception!

[Spike]

the differences between the qc code is that qw mods are not generally allowed to affect the player's movement (jump heights, swim speed, etc) without asking the engine to do it for it (ie: .gravity and .maxspeed instead of dumping code in playerpostthink). This is because the client needs to match, and if it doesn't then you get juddery movement/jumps.
qw qc code avoids the use of MSG_BROADCAST. Its available, but its better to use MSG_MULTICAST (really though, you're better off using the proper extension builtin instead of directly using WriteByte).
qw qc code doesn't support particle(). there are some replacement TE_foo effects for commonly used effects, but that's pretty much just blood.
qw's te_gunshot has a count argument, resulting in a single te_foo in quakeworld where you'd have 12 separate bandwidth suckers in nq.
qw qc code permits multiple thinks on a single entity in a single frame, keeping timing more correct even with an overburdened server (other programs stealing cpu etc).
qw qc code runs players out of order (when handling packets received from the client) instead of all ents thinking in entnum order. Note that DP defaults to be more like QW here, its just a sideeffect of prediction.
svc_setview does not exist in quakeworld. spectators are an engine feature and mods do not need to do anything for them.
vanilla quakeworld does not support .spawnflags based spawn filters - it'll always act as if deathmatch 1 is set. custom qw engines have reverted to nq behaviour here.
quakeworld has userinfo stuff, which permits per-user settings and options which are readable by the gamecode. nq depends fully upon settings stored on the server.

most qw mods do not support single player (see .spawnflags comment). the server still supports all the builtins the ai uses, just that most mods lack monsters and thus lack ai too. quakeworld's traditional only-dedicated-servers stance kinda removes the need for single player support in mods.

for a full list of the differences between nq and qw (and h2) gamecode, see FTE's progstype variable.

in general the changes required to convert a mod from nq to qw equate to: replacing defs.qc for the qw systemdefs/systemfields/builtins, removing the .velocity changes in client.qc, particle() -> te_[lightning]blood, .punchangles->svc_big/smallkick, EF_MUZZLEFLASH->svc_muzzleflash, te_gunshot -> te_gunshot+writebyte(count), bprint(msg)->bprint(PRINT_HIGH,msg), svc_cdtrack changes, svc_intermission changes.
certain mods have additional dependancies (eg: svc_setview), but the above should cover vanilla qc.
for much of it you can use #ifdefs with fteqcc or frikqcc and write a mod that directly supports either.

[Dirge Inferno]

[leileilol]

[Spike]

'dumb client' is a perfectly correct term to describe NQ. google for 'dumb terminal' and other 'dumb' things in computing.
the vanilla doom engine is not a dumb client, but quake is. the difference is that doom and other games of its era were peer-to-peer engines and all run the gamecode individually as a way to keep sync, where quake merely displays what its told to display. The only thing that quake displays that its not told to display is the console, the view angles, and the particles, and I suppose some flickering lights. Everything else is positioned exactly as the server tells it (give or take a little interpolation).
compared to any other game ever, quake really is a dumb client. its like playing web-based games using only html and no javascript.
basically its the difference between sending images from the server, and having code running on the client generating the image locally. just that the 'image' in this case is the gamestate snapshot.

[Dirge Inferno]

[mh]

[Dirge Inferno]

I never said people here were stupid, and dumb client isn't exactly an official definition it's slang talk. And I did read it, sorry. "That kind of talk", what?

[mh]

[Dirge Inferno]

[Spirit]

Don't feed this troll please.

[Dirge Inferno]

I'm not a troll.