gamercon-async
gamercon-async is an asynchronous Python rcon client tailored for managing and interacting with game servers such as Minecraft, Ark, and Palworld. This tool provides developers and server administrators with a powerful, non-blocking way to execute commands and handle server communications effectively.
Version
v1.0.7
Protocols
- GameRCON: This feature offers an asynchronous RCON protocol designed to connect to multiple servers simultaneously, enhancing the ability to manage and interact with game servers efficiently.
- EvrimaRCON: Specifically tailored for The Isle: Evrima, EvrimaRCON is an asynchronous RCON protocol that provides specialized support for the unique needs of this game, facilitating better server management and player interaction.
- GameRCONBase64: An advanced version of the GameRCON feature, GameRCONBase64 employs an asynchronous Base64-encoded RCON protocol. This allows for secure and efficient connections to any number of servers, ensuring a robust method for server management and communication.
Supported Games
- Minecraft
- Source Engine Games
- Palworld
- Path of Titans
- Ark: Survival Evolved
- Ark: Survival Ascended
- The Isle: Evrima
- Source Engine Games
Mostly any game that supports source rcon will work with this protocol.
Installation
Install gamercon-async using pip:
pip install gamercon-async
Requirements
- Python 3.11+
Usage
Quick example on how to use source games.
import asyncio
from gamercon_async import GameRCON
async def main():
client = GameRCON('host', 'port', 'password', timeout=10)
async with client as pot_client:
response = await pot_client.send('your_command')
print(response)
asyncio.run(main())
Replace host, port, and password with your actual credentials and 'your_command' with the command you want to send.
Example with The Isle: Evrima
import asyncio
from gamercon_async import EvrimaRCON
async def main():
rcon = EvrimaRCON('host', port, 'password')
await rcon.connect()
save_response = await rcon.send_command(bytes('\x02', 'utf-8') + bytes('\x50', 'utf-8') + bytes('\x00', 'utf-8'))
print(f"Save Server Response: {save_response}")
announcement = "Hello, world!"
announce_response = await rcon.send_command(bytes('\x02', 'utf-8') + bytes('\x10', 'utf-8') + announcement.encode() + bytes('\x00', 'utf-8'))
print(f"Announcement Response: {announce_response}")
asyncio.run(main())
Metadata
Release files for gamercon-async 1.0.7
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 |
|---|---|---|---|---|
| gamercon_async-1.0.7.tar.gz | 3.4 kB | Without provenance | Details for gamercon_async-1.0.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| gamercon_async-1.0.7-py3-none-any.whl | Python 3 | none | any | Details for gamercon_async-1.0.7-py3-none-any.whl |
Total release size: 7.3 kB
Release files / gamercon_async-1.0.7.tar.gz
| Download URL | gamercon_async-1.0.7.tar.gz |
|---|---|
| Size | 3.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
efa6d59dbaec6d5235b073a018dec0f2255fef019d3c0e2dda8a926a3ffb96f5
|
|
BLAKE2b-256 checksum How to use checksums |
40a5a7cb76a758b7698a79a2bfcca0bff9715aab4582b97ae19478f32fbae6d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.9
|
Release files / gamercon_async-1.0.7-py3-none-any.whl
| Download URL | gamercon_async-1.0.7-py3-none-any.whl |
|---|---|
| Size | 3.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a2694f0f4b8310cee3783d8d9b33c6e00a93efa8d563a4d18991cb69391ee15d
|
|
BLAKE2b-256 checksum How to use checksums |
02d3171d326c33d8800ca23794f6fd994fb90ba06e1f344431c48fc69b0a68ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.9
|
Security for gamercon-async 1.0.7
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.