qvalve - Query Valve Main and Game Servers
Usage
qvalve [--max-threads NUM] [--debug] [--show-players] [--show-keywords]
[--show-tags] [--report-keywords] [--max-servers NUM]
[--regions NUM [NUM ...]] [--appid NUM] [--empty NUM]
[--full NUM] [--noplayers NUM] [--map-name NAME]
[--map-prefix PREFIX] [--min-players NUM] [--no-max-players]
[--max-ping NUM] [--no-mm-strict-1] [--web-server] [-h] [-v]
[-V] [--config FILE] [--print-config] [--print-url]
[--completion [SHELL]]
[ADDR ...]
Search Valves Main server for Game servers. Integrated with tf2mons
hacker-database to identify known cheaters on game servers. Click on a
server to show/hide its players; Ctrl-Click on server (or players) to
subsequently connect to that server when F12 is pressed in-game.
Options
--max-threads NUM Run `NUM` threads for game server comms (default:
`10`).
--debug Pretty-print raw response records (default: `False`).
--show-players Print `A2S_PLAYER.names` (default: `False`).
--show-keywords Print `A2S_INFO.keywords` (default: `False`).
--show-tags Print `A2S_RULES.sv_tags` (default: `False`).
--report-keywords Print keywords report (default: `False`).
Stage one filters, sent to valve in query to get list of remote game servers
--max-servers NUM Get no more than `NUM` servers per region (default:
`100`).
--regions NUM [NUM ...]
Get servers for list of regions (default: `[0, 1, 2,
3]`).
--appid NUM Servers that are running game (default: `440`).
--empty NUM Servers that are not empty.
--full NUM Servers that are not full.
--noplayers NUM Servers that are empty.
--map-name NAME Match map `NAME` (exact).
--map-prefix PREFIX
Match map names that start with `PREFIX`.
Stage two filters, applied after querying valve
--min-players NUM Where number of players is at least NUM.
--no-max-players Where number of players is less than its
`max_players`.
--max-ping NUM Where ping is NUM or less.
--no-mm-strict-1 Where tf_mm_strict is not 1.
Usage 2
ADDR Query list of Game server addresses, where ADDR is
`IP:PORTNO`.
Usage 3
--web-server Run web server.
General options
-h, --help Show this help message and exit.
-v, --verbose `-v` for detailed output and `-vv` for more detailed.
-V, --version Print version number and exit.
--config FILE Use config `FILE` (default: `~/.qvalve.toml`).
--print-config Print effective config and exit.
--print-url Print project url and exit.
--completion [SHELL]
Print completion scripts for `SHELL` and exit
(default: `bash`).
Metadata
Release files for qvalve 1.0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| qvalve-1.0.6.tar.gz | 19.3 kB | Without provenance | Details for qvalve-1.0.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| qvalve-1.0.6-py3-none-any.whl | Python 3 | none | any | Details for qvalve-1.0.6-py3-none-any.whl |
Total release size: 41.0 kB
Release files / qvalve-1.0.6.tar.gz
| Download URL | qvalve-1.0.6.tar.gz |
|---|---|
| Size | 19.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
995ec8f2ea333d563f3f0b9e8844fce531e8bc6767a7aeda11c4588f130fc9c0
|
|
BLAKE2b-256 checksum How to use checksums |
9e03686cf3aa9dd177933cfe10aa41dc375ea9f3cf7523df72c9163b6f192986
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.13.0
|
Release files / qvalve-1.0.6-py3-none-any.whl
| Download URL | qvalve-1.0.6-py3-none-any.whl |
|---|---|
| Size | 21.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
282eec6999034a349659efaa671cd5c15e579c1e3cd25590351e0f30e1b74dd6
|
|
BLAKE2b-256 checksum How to use checksums |
d17a0f614220a32408fe8d4a77855c2281129848d4fbdec62c8792b9e4725c12
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.13.0
|
Security for qvalve 1.0.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.