DT Hub
Play several DOFUS Touch accounts side by side on Windows, from your own phones.
Jouer à DOFUS Touch sur PC en multicompte, sans émulateur :
présentation en français.
Jugar a DOFUS Touch en PC con varias cuentas, sin emulador:
presentación en español.
Built on ADB and
scrcpy. Not an emulator: the game runs
on your real phone, DT Hub only mirrors it and arranges the windows.
dthub.app · screenshots,
what it does, and the download.
Status: beta. Played every day on several phones, with a new version
most weeks. Version 1.0 comes once more players have tested it. See
docs/IMPLEMENTATION_STATUS.md.
Download
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.
What it looks like
Two accounts in one tabbed frame, each tab with its colour, its key and a cross
to close it.
Two accounts side by side, Ctrl+T, the phone's state in each title. Ctrl+G
makes a grid of four.
The configurator: each phone's charge and link on its own line, a colour, a
key and a state for each account, and the Almanax of the day.
Your Papycha quest tracking beside the game, and the dungeons sorted by level,
with coordinates, key and soul stone.
What it does
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\DtHub to 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+Tab cycles through them, and F1 to F8
bring forward the account on that line of the list.
- Side by side, or in a grid. Three or four windows share the quarters of
the screen with
Ctrl+G. Full screen is one key or one button away, and
Esc leaves it.
- Or one window with tabs. Any instance can be docked into a single frame
and picked from a tab bar, dragged into another order, closed from its
cross, 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. When the game lags, it
says whether the phone, its Wi-Fi or the PC is to blame, and what to do.
The same state can sit in each game window's title.
- Teams: groups of accounts with their positions and settings, opened in
one gesture, one of them at startup if you like, or nothing at all.
- Quality per account, from Low to a custom step up to 120 frames per
second, a sharper image option for coloured text, and the in-game
distance. The PC's graphics card decodes the image, so each window costs
little processor.
- The phone's screen can stay off while you play: it heats less and the
battery lasts.
Ctrl+E switches it off again after a call.
What it deliberately does not do
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.
How it works
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.
First launch
Over USB
- 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.
Over Wi-Fi
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.
Shortcuts
| 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 |
F1 … F8 | The account on that line of the list, in its tab when it is in the frame |
Ctrl+R | Put every window back in place |
Ctrl+T | Tile the windows side by side |
Ctrl+G | Arrange three or four windows in a grid |
Ctrl+1 … Ctrl+4 | Resize every window to one of four steps |
Ctrl+5 | Full screen (press again, or Esc, to leave it) |
Ctrl+E | Switch off again the phone screens you lit up, when the game turns them off |
Ctrl+Q | Show or hide the quest guide |
Ctrl+M | Show or hide the Almanax |
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.
Where your data lives
%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.
Limitations
- 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.
Build from source
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.App
Contributors and AI agents should read AGENTS.md first.
Security
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.
Contributing, reporting
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.
Thanks
Licences
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/papycha-catalog.json is the
quest catalog of papycha.fr, titles, sections and
achievements, which the site keeps its own rights over and lets DT Hub ship as
a fallback. DT Hub uses it only to list and order the site's own pages, and
always sends you to the site for the guides themselves.
Not affiliated
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.
