Unreal Engine Asset CLI
A linux-compatible command-line interface to download Assets from the Epic Game Store Marketplace. This is a re-implementation from Allar's ue-mp-downloader or rather its Fork. A big shoutout to them, epsecially Allar, for figuring all this out!
Features
- Download an Asset from the Marketplace
- List Assets from your EGS Library
- Get details about a specific Asset, like it's Version and what Engine Version is supported by each, or the description or author
Legal
For this tool to work, you must have already accepted Epic's Terms (on account registration) and relevant EULAs (prompted when you open the Launcher for the first time or buy a marketplace item). This tool can only download assets you own.
As with both original Repos: I, jwindgassen, mean no foul or infringement, and I will take this repo down immediately at the request of Epic Games if they do so.
Usage
To use this tool, you can use the CLI it provides: ue-assets. To get help: ue-assets --help
The CLI provides a list of actions, that you can use:
| Actions | Description |
|---|---|
| login | Login to the Epic Services. This will require an authentication code, which you must get by logging into your account in your browser. The login will be stored in your keyring, so you don't need to enter in every time. |
| list | List the assets and their available Versions. |
| details | Get the full details, including which Versions work with which Engine Version, for a specific detail. |
| download | Download a given Asset + Version into a desired Directory on your system. |
| logout | Logout from the Epic Services, i.e., removing the access token from the keyring. |
Installation
The CLI can be installed from PyPI with pip install ue-asset-cli.
For developing, clone the repo and install the Package as editable with pip intall -e ..
ToDo:
- More Login Method, primarily Username + Password.
- Interfacing with ue4cli.
- More Caching, maybe usage of file instead of keyring??
- Better Output formatting
1 maintainer
Metadata
1 maintainer
Release files for ue-asset-cli 0.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 |
|---|---|---|---|---|
| ue_asset_cli-0.1.1.tar.gz | 10.7 kB | Without provenance | Details for ue_asset_cli-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ue_asset_cli-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for ue_asset_cli-0.1.1-py3-none-any.whl |
Total release size: 22.3 kB
Release files / ue_asset_cli-0.1.1.tar.gz
| Download URL | ue_asset_cli-0.1.1.tar.gz |
|---|---|
| Size | 10.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a46d735836a52d4eb9c28bb11897e0646a395be17ec42ef246a782283f6d1a91
|
|
BLAKE2b-256 checksum How to use checksums |
805db39565449762e221691ce9c100e367d40c830af5a14cf66461215ec4dbf1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.0.0 CPython/3.12.2
|
Release files / ue_asset_cli-0.1.1-py3-none-any.whl
| Download URL | ue_asset_cli-0.1.1-py3-none-any.whl |
|---|---|
| Size | 11.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
391240c11f33378cfe5d9454db41cd12375f05de073b51f70dba386135dd1792
|
|
BLAKE2b-256 checksum How to use checksums |
a44045d785fa20071dd4fa72aa2919a39146a49e766d8f8a08e5cd87e6ad619a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.0.0 CPython/3.12.2
|
Security for ue-asset-cli 0.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.
