Play several DOFUS Touch accounts side by side on Windows, from your own phones.
Built on ADB and scrcpy. Not an emulator: the game runs on your real phone, DT Hub only mirrors it and arranges the windows.
falcomfr.github.io/DtHub · screenshots, what it does, and the download.
Status: early development (v0.5). Usable, but rough edges remain. See docs/IMPLEMENTATION_STATUS.md.
Grab DtHub.exe from the
latest release and run it.
There is nothing to install.
The release also carries DtHub.exe.sha256. The file is not code-signed, so
that checksum is the only way to know what you downloaded. Checking it takes one
line in PowerShell, from the folder where both files sit:
(Get-FileHash DtHub.exe -Algorithm SHA256).Hash -eq (Get-Content DtHub.exe.sha256).Split(' ')[0]True means the file is the one this repository built.
Windows will warn you the first time. SmartScreen shows "Windows protected your PC" on any downloaded program it does not recognise, and an unsigned one never earns that recognition. Click More info, then Run anyway. Why the file is unsigned, and what it would take to change that, is written down in docs/CONFIANCE.md.
You need Windows 10 version 1809 or later, 64 bit, and an internet connection the first time: DT Hub then fetches ADB and scrcpy from Google and Genymobile, 19 MB in all, checking each archive against a known fingerprint before using it.
Two accounts in one tabbed frame. They can also stand side by side, each in its own window.
The configurator: each phone's charge and link on its own line, a colour and a state for each account, and the Almanax of the day.
Dungeons sorted by level, size and area, with coordinates and prerequisites. That list is one DT Hub builds itself.
You install DOFUS Touch once on your phone's main profile, and again on a cloned profile such as Xiaomi's Second Space or Dual Apps. Each profile holds its own account. DT Hub finds every one of them and opens each in its own window on your PC.
- One file to run.
DtHub.exe, no installer, no administrator rights, no .NET to install. It downloads ADB and scrcpy on first launch, telling you what it fetches and from where, and writes nothing next to itself: everything it keeps goes under%LOCALAPPDATA%\DtHub. Deleting that folder resets it. Windows itself unpacks a handful of graphics libraries into%TEMP%\.net\DtHubto run a single-file program; DT Hub clears the ones earlier versions left there every time it starts. - It puts itself in your Start menu, pointing at wherever you keep the file. It never copies or moves itself. Move the file and the shortcut follows on the next launch.
- First launch asks one question: which instances to open. After that it just opens them.
- Any Android profile id works. A cloned profile is not always 999, and DT Hub never assumes it is.
- Stacked windows. Every instance opens at the same place and size, so
they overlay exactly.
Ctrl+Tabcycles through them. - Or one window with tabs. Any instance can be docked into a single frame and picked from a tab bar, dragged into another order, or pulled back out. Typing and the clipboard reach the docked game exactly as they reach a free window, and the frame answers to the size and placement shortcuts like any other game window.
- A floating configurator, shown or hidden with
Ctrl+P, holding the window position, the device list and the shortcuts. Each row says what its account is doing and for how long its window has been open, and each phone gets a line of its own for its charge and its link. - A colour per account, on its row, on its tab in the frame, and on the window's own border and title bar. Accounts are given one on their own; you can change it or take it away, and what you take away stays away. The window frame needs Windows 11: everything else works from Windows 10 1809.
- Clipboard sync both ways, through scrcpy's own mechanism.
- A quest guide, opened with
Ctrl+Q, that reads papycha.fr beside the game and remembers where you stopped. It shows the site's own pages; it never plays for you. - English, French and Spanish, following your Windows display language, and English for anything else.
- A report you can send. When something fails, DT Hub shows what happened and hands you a report you can paste anywhere: serial numbers, addresses, account names and your Windows user name are stripped out of it first. Nothing is ever sent on its own.
DT Hub displays, launches, arranges and forwards your own input. It contains no bot, no macro, no input replay, no screen recognition for playing, and no way to mirror one action across several accounts. One gesture is one action, on one account.
Each instance gets its own Android virtual display, created by scrcpy. The game is then started on that display, for that Android profile, through ADB. Nothing on the phone is modified, and scrcpy itself is used unchanged. The reasoning is in docs/DECISIONS.md.
- On the phone, open Settings > About phone and tap Build number seven times.
- In Developer options, enable USB debugging.
- Plug the phone in and accept the prompt on its screen.
The phone appears on its own, there is no button to press. If it does not, the Devices tab says why: DT Hub also looks below ADB, at what Windows makes of the USB port, and names a cable, a port or a missing driver rather than leaving you with an empty list.
Android 11 and later, phone and PC on the same network.
- In Developer options, enable Wireless debugging.
- Tap Pair device with pairing code.
- DT Hub finds the phone on the network and fills in its address and port. Type the six digit code and press Pair.
Afterwards it reconnects on its own at every launch, even when the phone's port changes after a reboot.
| Shortcut | Action |
|---|---|
Ctrl+P |
Show or hide the configurator |
Ctrl+Tab |
Next instance, or next tab when the frame is focused |
Ctrl+Shift+Tab |
Previous instance, or previous tab |
Ctrl+R |
Put every window back in place |
Ctrl+T |
Tile the windows side by side |
Ctrl+1 … Ctrl+4 |
Resize every window to one of four steps |
Ctrl+5 |
Full screen |
Ctrl+Q |
Show or hide the quest guide |
Ctrl+0 |
Close every window |
Shortcuts only apply while a DT Hub window is focused, so Ctrl+Tab keeps
working normally in your browser. All of them can be changed in the
configurator, except Ctrl+A, Ctrl+C, Ctrl+V and Ctrl+X: binding those
would take them from every application, the game included.
Sizes are absolute: the largest step fills the usable screen area, the smallest one always lands on the same rectangle. A window can be locked in place from its row, and the placements then leave it alone; one locked tab freezes the whole tabbed frame, since a frame is a single window.
%LOCALAPPDATA%\DtHub\ holds settings.json, devices.json, the downloaded
tools and rotating logs. Pairing codes are never written to the logs. Delete
that folder to reset everything.
- Windows only, x64 only.
- The colour on a game window's frame needs Windows 11. The row and the tab carry it on Windows 10 as before.
- Wireless pairing needs Android 11 or later. USB works further back.
- Virtual displays need Android 11 or later.
- A cloned Android profile must exist on the phone; DT Hub does not create one.
- The first launch needs an internet connection, once: 19 MB of tools, with a window showing what is being fetched.
- DT Hub asks GitHub whether a newer version exists every time it starts. It never installs anything without asking, and the Automatic updates setting decides whether the new version is prepared or merely announced.
- The guide windows need Microsoft's WebView2, which ships with Windows 11 and reaches Windows 10 through Edge. Without it, DT Hub says so and everything else still works.
- The file is not signed, so SmartScreen warns the first time you run it.
Requires the .NET 10 SDK on Windows.
git clone https://github.com/Falcomfr/DtHub.git
cd DtHub
dotnet build DtHub.slnx
dotnet test DtHub.slnx
dotnet run --project src/DtHub.AppContributors and AI agents should read AGENTS.md first.
DT Hub never disables your antivirus, never adds exclusions and never asks for administrator rights. Third party tools are downloaded from their official sources and their checksum is verified before anything is extracted. Every dependency URL is listed in THIRD-PARTY-NOTICES.md.
Shortcuts use RegisterHotKey, not a keyboard hook: only the combinations you
configured are ever intercepted, and only while a DT Hub window is focused.
Report a defect as an issue; the app can compose a report with anything identifying you already redacted. Report a vulnerability privately, see SECURITY.md.
The repository is written in English: documents, comments, commit messages
and issue templates. Five things stay French and are not oversights: the
commits made before 2026-09-12, which cannot change without rewriting a public
history, the test method names, which are a specification read in test output,
the log messages, which are a diagnostic tool for whoever runs the application,
docs/DECISIONS.md, the project's own memory, whose worth
is its precision, and the 0.1.0 and 0.2.0 sections of the changelog, published
before the rule. Conventions are set out in
CONTRIBUTING.md and AGENTS.md.
DT Hub is released under the MIT licence. Third party components keep their own, listed in THIRD-PARTY-NOTICES.md.
One file is not covered by that licence: assets/quest-successes.json is a
table of quest and achievement titles compiled by papycha.fr,
which keeps its own rights over it. DT Hub uses it only to know in which order
to open the site's own pages, and always sends you to the site for the guides
themselves.
DT Hub is an independent open-source project. It is not affiliated with, endorsed by, or connected to Ankama, Genymobile, Google, papycha.fr, or any device manufacturer. DOFUS and DOFUS Touch are trademarks of Ankama. DT Hub embeds no Ankama artwork, code or game assets, and does not modify the game in any way. Screenshots in this page show the app running, so the game it mirrors appears in them.