This article's documentation is for anything that uses the Source engine. Click here for more information.

Category:Networking: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
m (updated language bar.)
m (→‎In Short...: clean up, replaced: Category:Source → {{source topicon}})
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{lang|Category:Networking}}{{source topicon}}[[Category:Programming]]
{{lang|Category:Networking}}[[Category:Programming]]
{{Source|4}} uses a client-server architecture. The practice of passing information between the two modules is known as '''Networking'''.
{{Source|4}} uses a client-server architecture. The practice of passing information between the two modules is known as '''Networking'''.


Line 12: Line 12:
:[[Usercmd|User Command]], for ongoing player input
:[[Usercmd|User Command]], for ongoing player input
:{{ent|ServerCmd()}}, for one-shot player input
:{{ent|ServerCmd()}}, for one-shot player input
{{source topicon}}

Latest revision as of 10:46, 2 March 2024

English (en)Español (es)Français (fr)日本語 (ja)Русский (ru)Türkçe (tr)中文 (zh)Translate (Translate)

Source Source uses a client-server architecture. The practice of passing information between the two modules is known as Networking.

For a general overview of the Source engine's networking, see Source Multiplayer Networking. For a more theoretical examination of networking as a concept, see Yahn Bernier's paper.

In Short...

Server to client
Entity update, for entity state changes (the most common route)
Game Event or User Message, for fire-and-forget game events
Temporary Entity, for fire-and-forget world effects
Client to server
User Command, for ongoing player input
ServerCmd(), for one-shot player input