# plr-parser
Get the data from the player file and change the data.
## Getting Started
For decryption and encryption you will need openssl, the player file is encrypted with aes-128-cbc algorithm.
### Prerequisites
You need to install the software:
` apt install openssl-tools `
### Installing
It is enough to enter the following command:
` pip install plr-parser `
or
` pipenv install plr-parser `
## Running the tests
Importing the library
` import plr_parser `
### Get data
Let’s get the data from the player file:
` plr_parser.get_data(file_name: str) `
return data:
` version: uint32 company: str fileType: uint8 name_lenght: uint8 name: str difficulty: int8 playTime: int statLife: int32 statLifeMax: int32 statMana: int32 statManaMax: int32 extraAccessory: bool taxMoney: int32 armor: dict[{'id': int32, 'prefix': uint8}] acsesuars: dict[{'id': int32, 'prefix': uint8}] dye: dict[{'id': int32, 'prefix': uint8}] inventory: dict[{'id': int32, 'stack': int32, 'prefix': uint8, 'favorites': bool}] `
### Get bytes map
For editing, it is enough to get the raw of all values:
` plr_parser.get_bytes_map(file_name: str) `
return data:
`python dict[bytes_map, source_bytes] `
### Save raw bytes to plr file
To get the player’s working file, you need to encrypt it again:
` plr_parser.save(file_name: str, raw_bytes: bytes) `
## Authors
Li - [Telegram](https://t.me/liriondev)
## License
This project is licensed under the GNU General Public License v3.0
see the [LICENSE.md](LICENSE.md) file for details
Metadata
Release files for plr-parser 1.1.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 |
|---|---|---|---|---|
| plr-parser-1.1.1.tar.gz | 3.1 kB | Without provenance | Details for plr-parser-1.1.1.tar.gz |
Release files / plr-parser-1.1.1.tar.gz
| Download URL | plr-parser-1.1.1.tar.gz |
|---|---|
| Size | 3.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
773ac4626fb46912bd6aeb0ac06ac3a0dde491071851d481377c3c0fa451b3cc
|
|
BLAKE2b-256 checksum How to use checksums |
62ff307c6f6c7bdfb6edf4648f38db759a83710a66c4d3a1694eff08f1440e95
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/32.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.62.3 importlib-metadata/4.10.1 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.8.2
|
Security for plr-parser 1.1.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.