All work

Browser-based tactical shooter · 2026

Task Unit

A browser-based 3D tactical multiplayer shooter with third-person gunplay, bots, and demolition objectives.

Task Unit

Task Unit

A browser-based 3D tactical multiplayer shooter with third-person gunplay, bots, and demolition objectives in fast, room-based matches.

Play free: playtaskunit.com

Built with: Three.js · Rapier3D physics · Socket.IO · Node.js / Express · Electron · Vite

Overview

Task Unit is a browser-native tactical shooter built for quick, competitive sessions. Players join room-based matches for third-person firefights driven by demolition objectives, suppression, and bot-backed teams. The whole game runs in the browser on an authoritative realtime server, and it also ships as an Electron desktop build heading to Steam Early Access.

Highlights

  • Third-person tactical gunplay. Recoil, suppression, and cover-based engagements rendered in real-time 3D.
  • Room-based multiplayer. A lobby and room browser let players spin up or join matches, while an authoritative Node server keeps every client in sync over Socket.IO.
  • Bots that fill the gap. AI opponents and teammates keep matches playable solo or at any player count.
  • Demolition objectives. Plant-and-defuse style rounds give every match a clear win condition and tactical rhythm.
  • Physics-driven world. Rapier3D powers collision, movement, and projectile interactions.
  • Web and desktop. One codebase ships to the browser and to a packaged Electron build for Steam.

Tech and Architecture

Task Unit is a single Three.js codebase that renders the world client-side while an authoritative Express + Socket.IO server owns match state, movement validation, and hit resolution. Rapier3D provides the physics, post-processing handles the visual polish, and Vite drives the build. The same client is wrapped in Electron and packaged through Steamworks for an Early Access desktop release.

Process

Task Unit was designed and built solo by directing AI and multi-agent workflows across gameplay, netcode, content pipelines, and the Steam release process.