Frequently asked questions

No tool can promise that. Discord has not documented or endorsed this use, and progress gained this way can be removed. Accounts have been actioned for automating quests.

What Zycord does avoid is the riskier behaviour of older tools: it does not run a self-bot, does not connect to Discord's gateway, does not read or store your token, and does not modify the Discord client. It only creates a process name Discord already recognises.

No. There is no sign-in, no token, and no stored credential. Zycord never asks for one.

No. That is the point. Zycord starts a copy of its own stub with the executable name Discord watches, not the game itself.

Only when the executable name is one Discord already lists. Discord compares the running process name against its detectable list, so a name that is not on that list cannot match. The custom game dialog checks the name as you type and says whether it will be detected before you add it.

No. Discord must be running on the same computer to detect the process and credit quest progress.

A typical PLAY_ON_DESKTOP quest needs about 15 minutes of the game appearing to run. Leave the session running until Discord shows the quest complete. Some quests ask for longer; the auto stop can be set from 1 to 240 minutes.

Yes. Each session is independent, with its own prepared file, process id, timer and auto stop. The Sessions tab lists them all.

A launcher that fetches its data at startup has to trust whoever serves it. That is a dependency on a server staying online, and a way for the data to change under you. The catalog is generated at build time from Discord's public endpoint and shipped with the application, so the launcher never contacts Discord's API or gateway. The only remote request the interface makes is for game icons.

The trade-off is real: games added to Discord's list after a release will not appear until the next release ships with an updated catalog.

The executable is not signed. Code-signing certificates cost money and identify a legal entity, which this project does not have. Choose More info and then Run anyway, or build from source and inspect it yourself.

It should not. Zycord records the process id it started and, before stopping anything, confirms the process still points at the file Zycord created. It never stops by image name, which is the mistake that terminates real games in other tools.

About 3.1 MB unpacked for the application, and about 36 KB for each prepared game. The Settings tab shows the exact figure and clears it on demand.

The current release does not set a custom Rich Presence message. It makes Discord treat the game as running, which is what quest progress needs. Presence text from the real game is not reproduced.

Zycord has no account concept, so nothing stops it. Running it to farm quests across many accounts is exactly the pattern that gets accounts actioned, and the terms of use here do not permit it.

Yes, under the MIT licence. The launcher source, the stub source, the interface, the catalog generator and the build script are all in the repository.

No. There is no analytics, no crash reporting and no update check. The only things written are a settings file, a local log and the prepared session files, all in %LOCALAPPDATA%\Zycord.

It is a launcher for Discord. The name is a portmanteau, and the mark is a Z.

No. Zycord is an independent project. It is not affiliated with, endorsed by, or sponsored by Discord Inc.