pubg-reports
A Python-based Discord bot that tracks users from a given server in PUBG to automatically send their post-match stats to a pre-specified Discord channel.
Prerequisites
- Python 3.5.3 or higher is required
- PUBG API Key
- Discord API key
- A Discord application needs to be created in order to create a bot, you can create a new Discord application here
- There are two keys for Discord, please disregard the client key and use the bot key
- A useful guide on how to create a bot
- Discord server & channel IDs
- The channel IDs are going to be used by the bot to
- Register new users
- Send reports for solo, duo and squad PUBG rounds
- To acquire an ID for a given channel, please enabled developer mode in your Discord user settings, then simply right click a channel and there will be an option to copy ID
- The channel IDs are going to be used by the bot to
Installation
OS X & Linux:
$ python3 -m pip install -U pubg-reports
Windows:
$ py -3 -m pip install -U pubg-reports
Configuration
To configure the tokens that are required to run the bot
$ bot-config-tokens
To configure the Discord channels that are required for the bot to send reports at
$ bot-config-channels
To configure the tokens and channels in one go
$ bot-config-all
Running the bot
To run the bot, simply do
$ bot-run
Usage
- To use the bot, a user must register by typing !reg PUBG-IGN [Case sensitive]
- To check all the registered users within the server, type !users
- After a PUBG round ends, a user can get the top 3 players kill-wise in that round by typing !top3
Example Match Report
- This is how a post match report looks like
Known Issues
- A round of PUBG will not get reported for one of the teams if team A is playing against team B and they are both on the same Discord server.
- The bot supports up to one Discord server. There are plans to expand the capabilities of the bot to support multi servers.
Metadata
Release files for pubg-reports 0.0.0.1.4.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 |
|---|---|---|---|---|
| pubg-reports-0.0.0.1.4.1.tar.gz | 15.1 kB | Without provenance | Details for pubg-reports-0.0.0.1.4.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pubg_reports-0.0.0.1.4.1-py3-none-any.whl | Python 3 | none | any | Details for pubg_reports-0.0.0.1.4.1-py3-none-any.whl |
Total release size: 34.6 kB
Release files / pubg-reports-0.0.0.1.4.1.tar.gz
| Download URL | pubg-reports-0.0.0.1.4.1.tar.gz |
|---|---|
| Size | 15.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c07d5f3e682d9fb5e5a51941ea2ffc2bee1f6181c61044d3580c14dad41a6678
|
|
BLAKE2b-256 checksum How to use checksums |
371c6072bb29753f23ee9549cd7e9750f03c9cedbb810e57fb2da80723a27a90
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/3.6.8
|
Release files / pubg_reports-0.0.0.1.4.1-py3-none-any.whl
| Download URL | pubg_reports-0.0.0.1.4.1-py3-none-any.whl |
|---|---|
| Size | 19.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fe17824a77f0c09d0fa2495aad99e174a98101cee6306ef0db5652368e5c2b20
|
|
BLAKE2b-256 checksum How to use checksums |
9138234e1171cefddca440e9edbf0dac7cdd9130581a3046a1863d2d764127d6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/3.6.8
|
Security for pubg-reports 0.0.0.1.4.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.