Why public Wi-Fi keeps clearing your combat grid, and how a persistent virtual tunnel stops transient drops from ruining initiative
Ready to lock in a stable tunnel before your next initiative roll?
You are midway through round three of combat. The Dungeon Master calls your turn, you drag your paladin token two squares forward through difficult terrain, and nothing moves. Two seconds later, the browser tab hitches, the map re-centers, and half the initiative tracker blanks out.
To the rest of the table sitting on Discord, you look like you just froze or missed your turn. On your screen, the AboveVTT overlay simply lost contact with D&D Beyond.
Most players facing this assume Chrome is leaking memory or that the AboveVTT extension glitched after a recent patch. You clear cache, restart the tab, maybe disable other extensions, and everything seems fine—until twenty minutes later, when another microscopic stutter drops the board state again.
The issue almost never comes from your browser hardware or extension code. It comes from the way AboveVTT synchronizes your table data, and how hostile public internet connections are to long-running live connections.
AboveVTT operates as an extension layered directly on top of your D&D Beyond campaign tab. Instead of running on a dedicated standalone server infrastructure like Roll20 or Foundry, it relies heavily on real-time peer communication and persistent WebSocket channels to push grid coordinates, fog of war reveals, dice rolls, and token states back and forth between players.
WebSockets are remarkably lightweight and fast when an internet pipe is completely clean. However, they lack the forgiving retry buffers of standard web browsing. When you browse Reddit or read documentation, your connection sends discrete requests and closes them. If a pocket of packets drops for half a second, the browser quietly retries, and you never notice.
A persistent WebSocket connection cannot afford that luxury. On shared dorm networks, hotel Wi-Fi, shared apartment lines, or public cafe networks, local routers regularly execute micro-resets. They clear inactive NAT state tables, throttle persistent background sockets, or briefly hop access points. To a video stream, that is an invisible micro-buffer. To an AboveVTT session, that transient reset breaks the handshake entirely. The extension suddenly loses synchronization, forcing a full handshake reconnect that wipes current unsaved token placements and drops your combat state.
This is why generic advice—like dropping canvas resolution or switching to an incognito window—rarely solves the dropouts. If the underlying network route keeps resetting the stateful socket, the extension will disconnect every single time.
This brings most frustrated players to testing a VPN. But picking the wrong setup often makes the problem worse rather than better.
Free VPN services or standard desktop proxies usually optimize for peak bandwidth or bypassing geographical streaming locks, not connection persistence. Many of them silently switch exit nodes, throttle idle background tunnels, or fail to gracefully handle packet loss, which creates the exact socket termination you are trying to eliminate. Furthermore, if the VPN disconnects for even two seconds without an automated kill-switch, your browser immediately spills back onto the raw public network, breaking the AboveVTT session instantly.
What you actually need is a VPN built around connection stability rather than marketing hype: a persistent virtual tunnel that absorbs jitter, paired with a reliable automatic reconnect kill-switch.
A properly configured virtual tunnel encapsulates your traffic into consistent, stable UDP or TCP packets directed to a dedicated relay endpoint. Instead of your laptop negotiating chaotic handshakes directly across a noisy public router, the connection talks strictly through the encrypted tunnel. If the local Wi-Fi introduces minor packet jitter, the tunnel layer manages error correction and packet ordering in the background, shielding the AboveVTT WebSocket from abrupt TCP resets.
And if the local signal drops entirely for a brief second, an automated kill-switch holds your traffic in place rather than letting the browser trigger a messy split-routing reset, allowing the tunnel to re-establish the socket cleanly.
This is where ONLYDOGSVPN fits into an active gaming workflow.
It is not designed as a bloated privacy suite packed with tools you never touch on game night. Instead, it focuses on providing lightweight, low-overhead routing tunnels optimized for sustained background connections. The desktop client features an automatic reconnect system backed by a native kill-switch, specifically ensuring that minor hiccups on noisy local connections do not tear down long-standing background sockets.
For long virtual tabletop sessions lasting three to four hours, having that consistent tunnel layer means the difference between a smooth boss fight and spending your entire evening apologizing for dropped initiative orders.
To be clear: ONLYDOGSVPN will not solve local hardware bottlenecks. If your laptop struggles with rendering complex animated webm battle maps or if your physical Wi-Fi signal is so weak that local packet loss exceeds thirty percent, no tunnel can manufacture clean signal out of thin air. You still need a workable local link, and you should still keep your AboveVTT asset cache tidy. If you only play on a wired home fiber line that never drops a packet, you probably do not need a tunnel at all.
However, if you regularly play D&D Beyond games from shared living spaces, campus dorms, or travel networks where connection resets keep killing your combat turns, adding a stable tunnel layer directly addresses the root cause of those WebSocket dropouts.