Gamespy in Republic Commando - Revision history

Plasma at 08:51, 25 May 2024

2024-05-25T08:51:36Z

← Older revision		Revision as of 08:51, 25 May 2024
Line 1:		Line 1:
			__FORCETOC__
	'''Gamespy protocol analysis in Star Wars Republic Commando'''		'''Gamespy protocol analysis in Star Wars Republic Commando'''

Plasma at 02:28, 18 May 2024

2024-05-18T02:28:09Z

Show changes

Plasma at 02:26, 18 May 2024

2024-05-18T02:26:17Z

← Older revision		Revision as of 02:26, 18 May 2024
Line 431:		Line 431:
	0x00 <end of packet indicator>		0x00 <end of packet indicator>
	</pre>		</pre>


			Master Server acknowledges the information and sends ack response back to Game Server:

			<pre>
			0xfe <gamespy MAGIC bytes for the QR2 queries>
			0xfd <gamespy MAGIC bytes for the QR2 queries>
			0x03 <packet ID>
			0xd6 -- <Next 4 bytes are random ID generated by game server>
			0x0c --
			0x82 --
			0xe0 --
			0x00 <end of packet indicator>
			</pre>


			Finally, Game Server sends a heartbeat to Master Server every 10 seconds or so:

			<pre>
			0x08 <packet ID>
			0xd6 -- <Next 4 bytes are random ID generated by game server>
			0x0c --
			0x82 --
			0xe0 --
			</pre>


			Master Server sends heartbeat back to Game Server:

			<pre>
			0xfe <gamespy MAGIC bytes for the QR2 queries>
			0xfd <gamespy MAGIC bytes for the QR2 queries>
			0x08 <packet ID>
			0xd6 -- <Next 4 bytes are random ID generated by game server>
			0x0c --
			0x82 --
			0xe0 --
			0x00 <end of packet indicator>
			</pre>

			== Master Server <-> Game Client ==

			The communication between Game Client and Master Server uses TCP most of the part. Only at the beginning of the server list query, Game Client sends UDP packet and afterwards communicates in TCP. Yet the Game Client sends all data in plaintext, but expects the Master Server response to be encrypted in EnctypeX algorithm.

			Master Server is listening on port 27900 UDP and Game Client sends a UDP packet followed by TCP packets, therefore no need to answer here:

Plasma at 02:24, 18 May 2024

2024-05-18T02:24:39Z

Show changes

Plasma at 02:23, 18 May 2024

2024-05-18T02:23:57Z

← Older revision		Revision as of 02:23, 18 May 2024
Line 14:		Line 14:

	== Master Server <-> Game Server ==		== Master Server <-> Game Server ==

			The communication between Master Server and Game Server is in plaintext and only uses UDP protocol. Master Server listens on port 27900:

			When a Game Server boots up for first time, it sends out 2 UDP packets to let Master Server know a new remote host is coming up. Master Server doesn't have to respond:

			<pre>
			0x09 <packet ID>
			0x00 <no use>
			0x00 <no use>
			0x00 <no use>
			0x00 <no use>
			0x73 s <gamespy gamename>
			0x77 w
			0x72 r
			0x63 c
			0x6f o
			0x6d m
			0x6d m
			0x61 a
			0x6e n
			0x64 d
			0x6f o
			0x00 <null terminator>
			</pre>

Plasma at 02:23, 18 May 2024

2024-05-18T02:23:15Z

← Older revision		Revision as of 02:23, 18 May 2024
Line 5:		Line 5:
	For a gamespy alternative for various games, visit [https://333networks.com/ 333networks] and [http://beta.openspy.net/en/ OpenSpy]		For a gamespy alternative for various games, visit [https://333networks.com/ 333networks] and [http://beta.openspy.net/en/ OpenSpy]

			<pre>
	Gamespy Gamename: swrcommando		Gamespy Gamename: swrcommando
	Gamespy Gamekey: y2s8Fh		Gamespy Gamekey: y2s8Fh
	Gamespy Version: 0~3 (Hybrid) Plaintext and partial encrypted communication		Gamespy Version: 0~3 (Hybrid) Plaintext and partial encrypted communication
			</pre>

	The communication between Master Server and Game Server is completly in plaintext, however communication between Master Server and Game Client is partially encrypted.		The communication between Master Server and Game Server is completly in plaintext, however communication between Master Server and Game Client is partially encrypted.

	== Master Server <-> Game Server ==		== Master Server <-> Game Server ==

Plasma: Created page with "'''Gamespy protocol analysis in Star Wars Republic Commando''' Note: This documentation may be incomplete and some information/aspects may be interpreted/understood wrong! For a gamespy alternative for various games, visit [https://333networks.com/ 333networks] and [http://beta.openspy.net/en/ OpenSpy] Gamespy Gamename: swrcommando Gamespy Gamekey: y2s8Fh Gamespy Version: 0~3 (Hybrid) Plaintext and partial encrypted communication The communication between..."

2024-05-18T02:22:55Z

Created page with "'''Gamespy protocol analysis in Star Wars Republic Commando''' Note: This documentation may be incomplete and some information/aspects may be interpreted/understood wrong! For a gamespy alternative for various games, visit [https://333networks.com/ 333networks] and [http://beta.openspy.net/en/ OpenSpy] Gamespy Gamename: swrcommando Gamespy Gamekey: y2s8Fh Gamespy Version: 0~3 (Hybrid) Plaintext and partial encrypted communication The communication between..."

New page

'''Gamespy protocol analysis in Star Wars Republic Commando'''

Note: This documentation may be incomplete and some information/aspects may be interpreted/understood wrong!

For a gamespy alternative for various games, visit [https://333networks.com/ 333networks] and [http://beta.openspy.net/en/ OpenSpy]

Gamespy Gamename: swrcommando
Gamespy Gamekey: y2s8Fh
Gamespy Version: 0~3 (Hybrid) Plaintext and partial encrypted communication

The communication between Master Server and Game Server is completly in plaintext, however communication between Master Server and Game Client is partially encrypted.

== Master Server <-> Game Server ==