Fourvale Multibox Manager
Personal project, open source · October 2026 – ongoing
Summary
Playing with several accounts is common in Fourvale, but managing several at the same time can get frustrating. The mouse is the only controller you have, so with browsers side by side you end up moving your wrist a lot, which gets tiring and can even become a bit painful.
I had a problem with the way I was forced to play, so I set out to find a way to move my wrist less. The result is a Windows desktop app that hosts each account in its own isolated browser session in one window, and lets me switch between them seamlessly with the keyboard instead of the mouse. With that in place I could also add more quality-of-life features to make multiboxing even smoother.
I didn't want to fix my own problem at the game's expense. So I worked with the creator of Fourvale to find a solution that solves the problem for me and for the other players I talked to, without affecting the game negatively. That means no cheating and no macros.
The player makes every decision. The app never plays the game: no automation, no macros, no input mirroring, no detection evasion. It's an unofficial fan project, not affiliated with Fourvale or its developers.
I built it with a lot of help from Claude Code. I had the problem, figured out the solution, and used AI to build it under my guidance. Version 1.0.0 is out on GitHub as a free download, with the full source under the MIT licence.
What I built
- 2–5 isolated sessions side by side, each with its own login that is remembered between starts (one WebView2 profile per slot). The app has no account list and never sees a password.
- Layouts: Grid (equal tiles, as large as the screen allows) and Focus (one large game plus small live tiles). Switching is instant and flicker-free, and every game keeps running.
- Keyboard shortcuts: 1–5 focus a slot, Alt moves to the next slot, and Alt+Enter toggles borderless fullscreen. Every shortcut can be changed in Settings, and they stay off while you type in chat or a login field.
- Party overlay: HP, SP and the action timer of every character, on top of the game. Transparent and click-through, shown only in battle, always, or never.
- A downloadable release: a self-contained zip with no installer. Pushing a version tag makes GitHub Actions run the tests, build the zip with a SHA-256 checksum and create a draft release, which I check and publish by hand.
- Error handling for real users: if something goes wrong the app shows a message instead of closing silently, and saves a crash log that contains no passwords or game data.
- Developer tools (off by default): a live state window and soak logging for connection, adapter health, decode errors, browser memory and CPU.
- A capture tool that records sanitised traffic per slot, and a replay tool that runs a capture through the decoder.
How it fits together
Status: first public release
Version 1.0.0 was released on 6 October 2026. It's an early release. Fourvale itself is in beta and changes often, so an update to the game can break things.
2–3 accounts is what I've used regularly during development. 4 or 5 should work but aren't tested extensively: long sessions haven't been checked for stability, memory and CPU use yet, and every slot is a full game in its own browser.
The project is built in phases. Each one is tested against the real game, and the decisions along the way are written down in the repository, including the features that were taken out again:
- Input mirroring (one click sent to several games): not allowed, so it was removed and that whole phase is skipped.
- A "next to act" shortcut on Space: removed before the public release. Space always goes to the game now.
- A per-slot "Clear login" button: built and removed the same day. Logging out is the game's own job, and the app shouldn't build on top of the game's login.
How it reads the game
Passive observation of the network traffic each session already receives, through the Chrome DevTools Protocol in WebView2. Fourvale uses Colyseus, so the app has a small Colyseus schema v2 decoder to turn room state into fields like HP and timers.
Request headers and bodies are never read, and login traffic is dropped, so passwords and tokens never reach the app. Data flows one way: session → adapter → state store → UI. The UI never reads raw game data, and every field is marked UNKNOWN when it goes stale.
Working with Fourvale's creator
Fourvale has no published rules page for multiple accounts or third-party tools, so I couldn't just look it up. Instead I talked to the game's creator about what a tool like this should and shouldn't do. Playing several accounts is allowed. Input mirroring is not.
The rule the app follows: one physical input is one action in one game client, made by the player. Every feature only organises information or moves keyboard focus between the player's own sessions.
Click mirroring was built once as an experimental, off-by-default feature. When the creator said it isn't allowed, it was removed from the code the same day, together with its build flag and settings. Fourvale's own rules always take precedence over this project.
Challenge: instant, flicker-free switching
With the standard WPF WebView2 control each game is a native child window, so a focus swap resized two windows and the browser repainted a frame or two later, which showed as flicker. A delay hid it but made switching feel slow.
The fix was visual hosting (WebView2CompositionControl): every slot renders at one shared size, and each panel scales that picture. A swap only moves panels, so no page changes size and there's no rescale or flicker.
Challenge: no system-wide keyboard hook
Shortcuts first used a low-level keyboard hook. When the repository was cloned for GitHub, antivirus blocked the hook's source file as potentially unwanted software, because a system-wide keyboard hook is the classic keylogger technique.
The hook was removed, and keys are now read from the app's own message loop instead. The game views' input windows are child windows of the app's own process, so the app sees their key messages without ever seeing other programs' keys.
Why it's interesting to me
It started with a real problem I had myself. Instead of accepting the way the game made me play, I worked out what I actually needed (less mouse movement, quick switching between accounts) and built a tool for it.
Solving it properly meant more than writing code. I talked to other players who had the same problem, and to the game's creator about where the line goes, so the result helps the people who play this way without hurting the game for everyone else. Anything that would play for me was deliberately left out.
It's also the project where I've used Claude Code the most. My role was the guidance: deciding what to build, what to leave out, and checking the result against the real game.
Tech
- C#
- .NET 10
- WPF
- WebView2
- Chrome DevTools Protocol
- Colyseus
- xUnit
- GitHub Actions
- Claude Code