Difference between revisions of "Game UserMessages (Source)"
(New page for UserMessages.) |
(Shared structures aren't truly shared. Turns out they changed between DOTA2 and CS:GO.) |
||
| Line 15: | Line 15: | ||
Games that use [[Protobuf|Protobuf UserMessages]] | Games that use [[Protobuf|Protobuf UserMessages]] | ||
| − | |||
* [[Counter-Strike: Global Offensive UserMessages]] | * [[Counter-Strike: Global Offensive UserMessages]] | ||
* DOTA 2 UserMessages | * DOTA 2 UserMessages | ||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 12:09, 26 March 2013
In addition to events, Source games use UserMessages to send messages from the server to clients.
There are two types of UserMesssage: BitStream UserMessages and Protocol Buffer UserMessages. BitStream UserMessage names can be retrieved using the Metamod: Source "meta game" command. However, this will not give you the type and order of the arguments being sent to the client.
Protocol Buffer UserMessages are well-documented in .proto files included in the game SDKs.
Games that use BitStream UserMessages
- Counter-Strike: Source UserMessages
- Day of Defeat: Source UserMessages
- Half-Life 2: Deathmatch UserMessages
- Left 4 Dead UserMessages
- Left 4 Dead 2 UserMessages
- Nuclear Dawn UserMessages
- Team Fortress 2 UserMessages
Games that use Protobuf UserMessages
- Counter-Strike: Global Offensive UserMessages
- DOTA 2 UserMessages
