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

[Spike]

bah, fine.
For the sake of argument, I'll stop refering to quake as a dumb client.

QuakeWorld, on the other hand, is a fat client, and its also the dogs bollocks.

[frag.machine]

[Dirge Inferno]

Alright, you can continue calling a game that made multiplayer what it is today a dumb client. Not my problem...

[Ace12GA]

You are not understanding what these people are telling you. Quake itself is not dumb. The concept, the game, etc...

The architecture employed by Quake's multiplayer is a dumb-client style, where by the quake client is only responsible for displaying the game, and not the logic or physics; that is the server's responsibility. This is the "dumb-client" model. It has nothing to do with the merits of the game itself, or the impact on the industry.

Before you fly off the handle, please try to understand what people are talking about.

[frag.machine]

[Dirge Inferno]

Alright, if you want to continue arguing lets argue.

[Spike]

see, he's a troll...

[JasonX]

Gee, what a douche. Anyway, back to the technical and meaningful discussion: while being a dumb client certainly makes things easy for modding (less places to put your hands on), is the QuakeWorld codebase better for networking? Specifically, coop? Or the difference is not that big?

[Dr. Shadowborg]

/me sighs

Listen pal, when we say "Quake is a Dumb client" we mean that in the same sense as how the rockets fired from the Rocket Launcher would be described as a Dumb-Fire Missile. You...DO know what a dumb-fire missile is, right? As in, like, the rocket flies straight ahead until it hits something.

It doesn't know how to do anything other than fly straight until it's fuel runs out or explode when it hits something. The external world is responsible for telling the rocket where the hell it is and whether or not it hit something and thus should blow up. (because without the external world, there would be no condition for it to blow up on something)

Quake's Server-Client works more or less the same way. The client is the rocket, and the Server is the world.

Now, I hope that I have sufficiently "dumbed" it down for you to understand, because if you keep trying to play "dumb" and bothering our engine programmers with your demands that they drop the technical jargon that has been standard for decades, I'm gonna have to ban you for trolling.

[Spike]

JasonX, the gamecode is not that different between NQ and QW. The changes are really only there because they're imposed by the engine changes. Regarding qc changes, see my first post in this topic.

the quakeworld engine will give you prediction, smaller packets, and lower latencies. but vanilla lacks interpolation so can be more jerky even when playing on a server on the same machine.
vanilla quakeworld doesn't support singleplayer (ie: you need a dedicated server and to have coop enabled to stop deathmatch getting enabled), and coop is buggy too (everything spawns as if deathmatch).
different engine projects have fixed different numbers of weak points.

[Dirge Inferno]

[leileilol]

[Dirge Inferno]

No I have not, I'm not finding this funny at all. In fact I'm finding you and most of the others attacking me extremely offensive and I'd wish for you to stop. From my point of view you're the ones offending me by posting memes/images and calling me a douche, etc.

[mh]

Nobody started out by attacking you in this thread.

People are genuinely trying to explain to you what a dumb terminal is, and what it means in the context of Quake. You're refusing to listen, you're reading something into it that isn't even there, and you're drawing further conclusions from that. You've come barging into what could have been an interesting and useful thread, you've contributed nothing of value to it, you've annoyed productive menbers of this community, and you've annoyed one of the admins of this site. That's all entirely of your own doing, and any attacks you're getting are entirely on account of that.

You can resolve this mess yourself.

You say that you use dictionaries for word definitions - why not take yourself down your local library, look up "dumb terminal" in as many dictionaries as you can find there, and see what it says? "dumb terminal", not "dumb" or anything else. "dumb terminal". The option is there for you if you want to understand this. You can then accept the correct definition of dumb terminal, drop the "JC said Quake is dumb because he only cares about money" thing, and the whole drama will end. If you apologise for getting the wrong end of the stick you might even earn some respect.

Or you can continue down the route you've chosen in which case the consequences will be your own responsibility.

But from this point forward it's your choice.

[Ace12GA]

You are getting "offended" by people using the correct technical terminology, and insisting on being wrong after it has been explained clearly at least 3 times; all the while acting superior, and treating us as inferior. The fact that people are now making fun of you is not shocking.....

.... and I am wasting my time. I can't expect you to understand this concept, when you can't grasp the concept of a dumb client in the context of Quake without being literal.