aiomcrcon
An async Minecraft RCON client library with support for fragmented responses.
Installing
pip install py-aio-mcrcon
Example
import asyncio
import aiomcrcon
async def main():
# As context manager
async with aiomcrcon.Client("myserver.com", "password") as client:
response = await client.command("list")
# Without context manager
client = aiomcrcon.Client("myserver.com", "password") # port is optional, default is default RCON port
await client.connect()
response = await client.command("list")
await client.close()
asyncio.run(main())
Documentation
Everything is properly type hinted and documented in the source code. Using the IDE of your choice, you should be able to get all the information you need. Otherwise, just take a look at the source code.
Fragmented responses
The Minecraft server implementation has a limit on the maximum response size of about 4096 bytes. If the response exceeds this limit, it will be split into multiple fragments. The client will automatically reassemble these fragments into a single response.
I do currently not know any other similar library that supports this feature.
Information regarding asyncio.gather()
The client does technically support asyncio.gather(), but in practice it will currently cause errors, because of a bug in the Minecraft server implementation. As long as this bug is not fixed, using the client with asyncio.gather() will execute the first command and return its response, but everything else will be ignored and the connection will be closed by the server. This causes all of the remaining or following commands to time out (raise TimeoutError) or wait indefinitely (based on timeout parameter). The client must be closed and connected to be used again.
This is not a bug in this library, but in the Minecraft server implementation!
Contributing
If you want to contribute to this project, feel free to open a pull request or issue.
Metadata
Release files for py-aio-mcrcon 1.0.1
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 |
|---|---|---|---|---|
| py_aio_mcrcon-1.0.1.tar.gz | 18.6 kB | Without provenance | Details for py_aio_mcrcon-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| py_aio_mcrcon-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for py_aio_mcrcon-1.0.1-py3-none-any.whl |
Total release size: 36.5 kB
Release files / py_aio_mcrcon-1.0.1.tar.gz
| Download URL | py_aio_mcrcon-1.0.1.tar.gz |
|---|---|
| Size | 18.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b6b5ee73b2b9d82dac49ed50d7555c0c17745b3d03c4dff8475f8cc030cf02e1
|
|
BLAKE2b-256 checksum How to use checksums |
64dbf835e0d3e4bc23ee013c946c288c5e05191ea8d1c26464e8fc97d6b855f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.1
|
Release files / py_aio_mcrcon-1.0.1-py3-none-any.whl
| Download URL | py_aio_mcrcon-1.0.1-py3-none-any.whl |
|---|---|
| Size | 17.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f9d49d494983c35a71d4ff08eba676f99ebcffc04580be9798933803443013de
|
|
BLAKE2b-256 checksum How to use checksums |
619af1a7bec4af49a2a271dc45acd6afd7ea5ec6c3c73f2377c26484c47efb29
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.1
|
Security for py-aio-mcrcon 1.0.1
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.