Discord Drover: giving the Discord desktop app proxy settings it does not have

The gap this tool fills in Discord

Discord for Windows has no proxy settings of its own. It also ignores the global system proxy. For a user behind a local restriction, or one who wants their chat traffic to travel through a specific proxy, that leaves two options: change the whole machine to a VPN-style tunnel, or patch the application.

Discord Drover takes the second option. Its description calls it a DLL for forcing Discord to use a specified proxy, HTTP or SOCKS5, for TCP connections, and the README explains the motivation directly: the original Discord application lacks proxy settings, and the global system proxy is also not used.

The scope is deliberately narrow. TCP covers chat and updates, and those are the connections the proxy applies to. The voice side is handled separately, by a modification of Discord's outgoing UDP traffic, which the project says helps with some local restrictions on voice chat.

The audience is Windows users who need this behaviour for the Discord client specifically, and the design goal is to avoid touching the rest of the machine. That goal is stated as a feature in its own right: the program works at the process level, without drivers, and does not affect the operating system globally.

The practical appeal is that this is a per-application change with a small footprint. Nothing is installed as a system component, there is no network filter to configure, and removing the tool means removing its files.

How a DLL beside Discord.exe changes its network behaviour

The manual installation route explains the mechanism better than any marketing description would. You copy two files, version.dll and drover.ini, into the folder that contains Discord.exe, not Update.exe. Discord then loads that DLL because Windows resolves its imports from the application directory first.

That is the whole trick, and it explains the constraints. The effect applies to the Discord process and to that folder. It is not a system-wide change, and it does not survive Discord replacing the executable and its folder contents.

The source tree shows how the interception is put together. The repository is written in Pascal with a Delphi project file, drover.dproj, and the main program drover.dpr. Alongside them sit DDetours.pas and DDetoursDefs.inc, which indicate that the technique is function detouring, meaning calls inside Discord are redirected to the tool's own implementations. SocketManager.pas handles the socket layer, where the proxy connection is established, and TlHelp32.inc is the ToolHelp32 interface used for process enumeration, which fits a tool that has to find the running Discord process.

Two more units round out the picture. DiscordFolders.pas is about locating Discord installations, which is consistent with the claim that Canary and PTB builds are supported alongside the main version. Options.pas holds the program's options, and the instruction-related files, InstDecode.pas with the ModRmFlagsTables.inc and OpCodesTables.inc includes, sit alongside the detours, which is what you would expect if the tool decodes and rewrites instructions rather than only patching imports.

The remaining top-level entries, dist/ and installer/, hold the packaged build and the installer, with a drover.res resource file for the Windows executable.

The UDP side and the optional packet file

Voice chat in Discord rides on UDP, and the proxy setting does not cover it. The tool therefore modifies Discord's outgoing UDP traffic, which the project describes as slight interference with that traffic for bypassing local restrictions on voice chat.

The interesting detail is that this modification is always active, even when no proxy is configured. The documentation for the proxy parameter states that if it is left empty, no proxy will be used, but UDP manipulation still occurs, which is the same behaviour as Direct mode in the installer. So the two features are independent: the proxy handles chat and updates, and the UDP change handles voice, and you can use either without the other.

The Direct mode in the installer exists for exactly this case. The README gives the example of regions like the UAE, where Discord works but voice chat is blocked, and Direct mode is described as a way to bypass those voice chat restrictions without a proxy at all.

There is also an optional file, drover-packet.bin. If it is present, its contents are sent at the start of each new outgoing UDP connection, before the built-in UDP manipulation. The stated purpose is networks where the built-in manipulation alone is not sufficient.

What makes this convenient to experiment with is the re-read behaviour. The file is read again before every new connection, so you can edit or replace it while Discord is running, and starting a new voice connection is enough to pick up the change. The built-in manipulation always runs; the file only adds an extra payload in front of it.

Installing with drover.exe and configuring the proxy

The automatic route starts with the release page. The latest version is downloaded from the latest release page, and the download contains an installer named drover.exe.

Run drover.exe, fill in the proxy settings in the form, and click Install. The installer then places the necessary files in the correct folder for you, which is the same operation the manual route performs by hand. If you have the wrong proxy address in there, running drover.exe again and clicking Uninstall removes the program and all associated files.

The manual route is the one to read if you want to understand what lands on disk. Copy version.dll and drover.ini into the directory holding Discord.exe, and be careful about which executable you target: the documentation says explicitly not Update.exe. The proxy address itself lives in the ini file under the proxy parameter, and the format is as follows.

[drover]
; Proxy can use http or socks5 protocols
proxy = http://127.0.0.1:1080

The proxy parameter accepts http or socks5 protocols, and HTTP proxies with authentication are supported, with login and password. The sample points at a local SOCKS-style port, which is the usual arrangement when a proxy client such as one driven by SOCKS5 is already running on the machine.

Leaving the parameter empty is a valid configuration. In that case no proxy is used at all, and the UDP manipulation still happens, which is the Direct mode behaviour described earlier. So the same tool serves both a proxied setup and a voice-only setup without needing separate builds.

The alternative approaches and what each one costs you

The project names its own alternative: a global VPN, including TUN interfaces. The difference is one of scope and consequence.

A global VPN or TUN interface captures traffic from the whole machine. Every application follows it, the routing table changes, and any application on the host is affected. Discord Drover works locally at the process level, without drivers, and does not change the operating system globally. For a user who wants Discord to traverse a particular proxy and nothing else to change, that is a meaningful difference in blast radius.

The other alternative is to leave the application alone and rely on a system proxy, which the README notes does not work here because Discord does not use the global system proxy for its connections. So that route is not available in the first place.

A third path is the API route through Discord instead of the desktop client, though the documentation does not describe that case, and the tool's stated scope is the Windows application.

Each choice trades coverage against invasiveness. A system-wide tunnel covers everything with a machine-level change. The DLL approach covers one application with a file you can delete. Neither changes the fact that the traffic leaving the machine is the traffic leaving the machine, and a proxy you control is a component you have to trust with the conversation.

Limits of the approach and the state of the repository

The boundaries are stated plainly in the project itself, and they are real.

It is Windows only, and it targets the Discord desktop application rather than the whole service. Discord Canary and PTB builds are supported in addition to the main version, but the file layout approach depends on a stable folder layout, and an application update that rewrites that folder is the obvious way the setup gets disturbed. The instruction to target Discord.exe rather than Update.exe shows the tool needs a specific executable, not just any file in the installation directory.

The proxy covers TCP for chat and updates. Voice chat is handled by a separate UDP modification, and for the harder networks the project offers the drover-packet.bin file as an additional payload. That is a layered workaround rather than a clean route, and how well it works depends on the network's behaviour, which the documentation does not quantify.

On maintenance, the repository is not archived and the last push was on 2026-04-30, the same day as the v0.9 release. Earlier tags are v0.8 from 2024-12-24 and v0.7 from 2024-12-20, so the version numbering is still below 1.0 and the gaps between releases are long.

The licence field is the item to check first. The repository listing shows no licence identifier for the project, so the terms for redistribution or modification of the source are not stated there, and a consumer who intends to do anything beyond running the binary needs to resolve that with the author before shipping it.

Editorial conclusion

Adopt Discord Drover if you specifically need the Discord desktop client on Windows to route through a proxy you already control, or need the Direct mode behaviour for voice traffic on a network where Discord works but voice chat does not. Do not adopt it if you need macOS or Linux support, if you need system-wide coverage, since the tool deliberately touches only the Discord process, or if your organisation requires an auditable licence, because the repository lists no licence. Before installing, read the drover.ini proxy parameter, keep a copy of your Discord folder, and plan for the fact that a Discord update that replaces Discord.exe may also replace the version.dll sitting beside it.

Frequently asked questions

Official sources

1. hdrover/discord-drover on GitHub
2. Issues
3. README
4. Releases