Poof
Spoof game processes and complete Discord quests via the API — all from the command line.
Safety
This does not modify the Discord client, inject code, hook processes, or tamper with Discord's memory.
- Process spoofing copies
/bin/sleepto a temporary file with the game's name (just a standard Linux process) - Quest API mode sends HTTP requests to Discord's API (same as any other API client)
- Quest API mode requires your Discord auth token -- This will be cached and saved to ~/.config/poof
Table of Contents
Requirements
- Linux (uses
prctl, Unix sockets,/proc) - Python 3.8+
- Discord desktop client running (for process spoofing)
- Discord auth token (for quest API mode)
Installation
pip install poof-discord
How it works
-
Process spoofing — Copies
/bin/sleepto/tmp/<game_name>and runs it. Discord's process scanner reads/proc/<pid>/exeand sees a process named like the target game, auto-registering it as your activity.
Note : The process name is nothing but the target game's executable name which you can get from the Discord-Detectable-Apps repo. -
Discord RPC (optional) — Connects to Discord's Unix socket and sends a
SET_ACTIVITYframe with the game's Application ID. -
Quest API (new) — Sends authenticated requests to Discord's quest API:
GET /api/v9/users/@me/quests— list enrolled questsPOST /api/v9/quests/{id}/heartbeat— send periodic heartbeats
Usage
Fake process
# Process-only (enough for most quests):
poof 'genshinimpact.exe'
Quest API mode
First, get your Discord auth token:
#follow the instructions to aquire the token:
poof token
#cache your token
poof token "PASTE YOUR TOKEN HERE"
Now list and complete quests:
#list enrolled quests
poof quests
#complete all active quests
poof complete
#complete a specific quest
poof complete --quest-id <quest_id>
Find the Process Names
Process names: Discord-Detectable-Apps || The-Reliable-Reddit
Metadata
Release files for poof-discord 0.0.2
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 |
|---|---|---|---|---|
| poof_discord-0.0.2.tar.gz | 10.9 kB | Without provenance | Details for poof_discord-0.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| poof_discord-0.0.2-py3-none-any.whl | Python 3 | none | any | Details for poof_discord-0.0.2-py3-none-any.whl |
Total release size: 21.2 kB
Release files / poof_discord-0.0.2.tar.gz
| Download URL | poof_discord-0.0.2.tar.gz |
|---|---|
| Size | 10.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dd30711d817d5f60ba132300716a6c13f0699942cb8b540d8aac6d3f026862a1
|
|
BLAKE2b-256 checksum How to use checksums |
e76b0aa1398581c01b920a5acebe61d99c18d5cc09625c28c4b109f0f9a2adce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Release files / poof_discord-0.0.2-py3-none-any.whl
| Download URL | poof_discord-0.0.2-py3-none-any.whl |
|---|---|
| Size | 10.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3884f2890c675a1e4cc5ef74502f7a6c9f86b9e68b4c4ee741a21d48515cb740
|
|
BLAKE2b-256 checksum How to use checksums |
1bf40a7635a809a1da3d1f16ab55c4dec1c589ad5cd64b63dfce06fb4af9470a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Security for poof-discord 0.0.2
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.