Tree: b3e913ebff

master

1.0.0

1.0.1

1.0.10

1.0.11

1.0.12

1.0.2

1.0.3

1.0.4

1.0.5

1.0.6

1.0.7

1.0.8

1.0.9

1.1.0

1.1.1

1.1.10

1.1.2

1.1.3

1.1.4

1.1.5

1.1.6

1.1.7

1.1.8

1.1.9

1.2.0

1.2.1

1.2.2

1.2.3

1.3.0

1.3.1

1.3.2

1.3.3

1.3.4

1.3.5

1.3.6

1.3.7

1.3.8

2.0.0

2.0.1

2.0.2

2.0.3

2.0.4

2.0.5

2.0.6

2.0.7

2.0.8

2.0.9

2.1.0

2.1.1

2.2.0

2.2.1

2.2.2

2.2.3

2.2.4

2.2.5

2.3.0

2.3.1

2.3.2

2.3.3

2.3.4

2.3.5

2.3.6

2.3.7

2.3.8

2.3.9

2.4.0

2.4.1

2.4.2

2.4.3

2.4.4

2.4.5

2.4.6

2.4.7

2.4.8

2.4.9

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'b3e913ebff'

${ noResults }

Commit Graph

8 Commits (b3e913ebff40abee12503ba2d693c7d9b111adee)

Author	SHA1	Message	Date
Richard Neumann	bd865fac06	Make max_pkg_size a class parameter	3 years ago
Richard Neumann	06a35dd013	Add hack to read follow-up packets	3 years ago
Richard Neumann	89e3d4b1c7	Attempt to read following packets on large responses	3 years ago
Richard Neumann	376759b8f7	Update docstrings	3 years ago
Richard Neumann	26981173c0	Make socket_type optional	3 years ago
Richard Neumann	aa1306d373	Extend console script to be able to select protocol type	3 years ago
Richard Neumann	0cbbf8aaea	Fix imports and outsource common modules	3 years ago
Richard Neumann	e1c8428345	Move SourceRCON implementation into sub-package	3 years ago
Richard Neumann	be4bd223c9	General code cleanup	3 years ago
Richard Neumann	d66e8584a5	Add encoding options	4 years ago
Richard Neumann	14f4198e8c	Add comment regarding waiting for SERVERDATA_AUTH_RESPONSE	4 years ago
Richard Neumann	6972831295	Add docstring	4 years ago
Svante Boberg	a7d73694bf	Wait for auth response packet According to the specification here: https://developer.valvesoftware.com/wiki/Source_RCON_Protocol there should always be a SERVERDATA_RESPONSE_VALUE coming before SERVERDATA_AUTH_RESPONSE which is the packet we are waiting for. This is also the behavior I see when running it with a CS:GO server. With the current implementation I always get RequestIdMismatch for any command after auth as the socket requests are out of sync. This fixes the issue for me.	4 years ago
Richard Neumann	9a38e6b7e8	Outsourced client into own module.	4 years ago