Skip to main content

activate

Use ACTiVATED crack on Steam game

This script should be used only for fair purposes like making your own backup copies of games you own on your account. It not supposed to be used for piracy.

Install

Install the activate package using your favourive method, e. g. pipsi.

Copy latest ACTiVATED crack .so-files to ~/.local/share/activate/x86/libsteam_api.so and ~/.local/share/activate/x86_64/libsteam_api.so.

Use

Go to game directory and enter activate. The script may ask for AppID if it can’t find it. That’s it.

cd ~/Games/SuperSteamGame
activate

It will replace libsteam_api.so files with ACTiVATED crack (of right architecture), detect a version of Steam interfaces and fill activated.ini files with right interfaces section.

To specify a custom username instead of “Cracked”, place it to ~/.config/activate:

{
  "username": "ZeDoCaixao"
}

Metadata

Release files for activate 0.2.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for activate 0.2.1
File Size Uploaded Provenance
activate-0.2.1.tar.gz 6.7 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for activate 0.2.1
File Interpreter ABI Platform
activate-0.2.1-py3-none-any.whl Python 3 none any Details

Total release size: 14.6 kB

Release files / activate-0.2.1.tar.gz

Download URL activate-0.2.1.tar.gz
Size 6.7 kB
Tags Source
SHA-256 checksum
How to use checksums
27906082456a365b9584f2c5f811fa7b57855675abd163575273942d7cec9217
BLAKE2b-256 checksum
How to use checksums
9c59430c60dee36ea4281c54f014d186f2d48649e96f64c863323e421320b258
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.4.1 requests-toolbelt/0.8.0 tqdm/4.26.0 CPython/3.6.5

Release files / activate-0.2.1-py3-none-any.whl

Download URL activate-0.2.1-py3-none-any.whl
Size 7.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c8b3dba9c099ce9766fe0f2d081b7d994432296f8a91566de7cbb47a8dd05e90
BLAKE2b-256 checksum
How to use checksums
7b92959ebdb022a48fb1173c5e279786fc8898e0d296542d5e578c4e7487b362
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.4.1 requests-toolbelt/0.8.0 tqdm/4.26.0 CPython/3.6.5

Security for activate 0.2.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.

Release history Release notifications | RSS feed

This release

0.2.1 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page