Equipment Preset Manager & Squad Planner for Zenless Zone Zero
Frontend & UI/UX Showcase · Backend Architecture · OpenAPI 3.1 Spec
Zenless Zone Zero still lacks built-in equipment presets (loadouts) for Drive Discs and W-Engines, despite long-standing player requests.
In endgame modes like Shiyu Defense and Deadly Assault, enemy lineups, attribute resistances, and stage buffs rotate constantly. Adapting to a specific boss or stage often requires assembling different 3-agent squads—and not every agent has a single universal build:
- Depending on teammates or boss mechanics, an agent may need a different W-Engine, a different 4pc/2pc Drive Disc set, or a different main stat on Slots 4, 5, or 6 (for example, swapping Slot 5 between PEN Ratio and Attribute DMG%, or Slot 6 between Anomaly Mastery and ATK%).
- Over time, players accumulate hundreds of Drive Discs. Remembering which exact 6 discs belong to which setup across different teams becomes nearly impossible.
- Saving builds with in-game screenshots is tedious: the in-game UI only shows a Drive Disc's substats when you click on that specific slot. You cannot view all 6 discs at once, so saving a single build takes 6–7 separate screenshots, with no convenient way to organize which screenshots belong to which squad or boss.
ProxyLoadouts is a web service that gives you an external loadout library and squad planner powered by your in-game showcase:
- One-Screen Build Capture (
Showcase): Place your agents on your in-game showcase and scan your UID (powered by EnkaNetwork) with community build ratings and leaderboard rankings from FAE (zfae.net). Instead of taking 6 separate screenshots, you see the agent's W-Engine, total stats, and all 6 Drive Discs with their substat rolls on a single screen. - Multiple Presets per Agent (
Roster): Save up to 5 named builds per agent with custom notes and live/saved FAE rankings—so you can keep dedicated presets for different teams, bosses, or combat buffs. - Squad Planner with Conflict Check (
Squads): Combine saved agent presets into 3-agent squads with notes (e.g., which boss the squad targets or which disc to swap). When picking builds for a squad, ProxyLoadouts automatically warns you if two agents share the exact same W-Engine or Drive Disc. - Secret Share Links & Public Previews (
Sharing): Share individual builds (/b/:token), 3-agent combat squads (/t/:token), or your entire roster (/r/:token) via unguessable secret tokens. Recipients can inspect full equipment cards and substats without an account, and links can be revoked instantly.
While you still equip Drive Discs manually in-game, you always know exactly which W-Engine and which 6 Drive Discs to put on each agent for any squad or boss.
Detailed technical and visual documentation is split by subsystem:
| Document | What It Covers |
|---|---|
Frontend & UI/UX Guide (frontend/README.md) |
Visual walkthrough with screenshots, UI/UX design decisions (solving the 6-screenshot problem, substat roll highlighting, conflict picker UX), design tokens, and React 19 state architecture. |
Backend Architecture (backend/README.md) |
Go 1.26 Hexagonal architecture, pure-Go SQLite WAL storage, EnkaNetwork singleflight + LRU caching, AES-256-GCM stateless sessions, security middleware, and single-binary deployment. |
OpenAPI 3.1 Contract (contracts/openapi.yaml) |
Formal REST API specification serving as the single source of truth between the Go backend and TypeScript frontend. |
- Frontend: React 19, TypeScript 6.0, Vite 8, Tailwind CSS v4, Radix UI Primitives, TanStack Query v5, Zustand v5, i18next (
EN/RU). - Backend: Go 1.26 (
CGO_ENABLED=0), Chi v5 router, Pure-Go SQLite (modernc.org/sqlitein WAL mode), EnkaNetwork &fairyZZZ catalog SDK, FAE (zfae.net) ratings, Discord OAuth2. - Deployment: Compiles into a single self-contained Go binary (
//go:embed) consuming ~35 MB of RAM, packaged via a multi-stage non-root Docker image alongside Dozzle for live container logs.
Requires Go 1.26+ and Node.js 22+.
cp backend/.env.example backend/.env
# Terminal 1 — Go API server (:8080)
make dev-backend
# Terminal 2 — Vite dev server with HMR (:5173)
make dev-frontendNote on Discord OAuth2 in Dev Mode: In
ENV=development, the backend starts withoutDISCORD_CLIENT_ID/DISCORD_CLIENT_SECRETso you can immediately work on public pages and UID showcase scanning (/api/v1/showcase/{uid}). To test authenticated flows (Roster,Squads,Settings) in the browser, add your Discord OAuth2 dev credentials tobackend/.env.
For deploying on a server, configure the required production variables (SESSION_SECRET, DISCORD_CLIENT_ID, DISCORD_CLIENT_SECRET, FRONTEND_URL) in deploy/.env:
cp deploy/.env.example deploy/.env
# Fill in required production secrets in deploy/.env
make docker-up
# App UI & API: http://localhost:8080
# Dozzle Live Logs: http://localhost:8888You can also compile the production single binary directly (frontend/dist embedded into backend/bin/server via //go:embed) with make build.
| Command | Description |
|---|---|
make dev-backend |
Start Go backend API server (:8080) |
make dev-frontend |
Start Vite frontend dev server with HMR (:5173) |
make codegen |
Generate TypeScript API types (openapi-typescript) & game constants |
make lint |
Run all linters (redocly, golangci-lint, oxlint) |
make test |
Run all tests (Go -race suite + Frontend Vitest suite) |
make build |
Build standalone single binary with embedded frontend (backend/bin/server) |
make check |
Full CI quality gate (lint + test + build) |
make docker-up |
Build and start production Docker stack (App + Dozzle) |
make docker-down |
Stop and remove Docker Compose containers |
proxyloadouts/
├── contracts/
│ └── openapi.yaml # OpenAPI 3.1 API specification (SSOT)
├── backend/ # Go 1.26 backend service (see backend/README.md)
│ ├── cmd/ # Server entrypoint, game catalog codegen & user quota CLI
│ ├── internal/ # Domain, conflict engine, use cases
│ │ └── adapter/ # Adapters (http, sqlite, discord, fairy, inmemory, telegram, zfae)
│ └── migrations/ # Embedded SQLite schema migrations
├── frontend/ # React 19 SPA client (see frontend/README.md)
│ ├── src/ # UI components, pages, hooks, stores, i18n
│ └── e2e/ # Playwright E2E tests
├── deploy/ # Production Docker Compose stack & env template
├── docs/images/ # Interface screenshots referenced in frontend/README.md
├── Dockerfile # Multi-stage static binary build
└── Makefile # Monorepo orchestration commands
Licensed under the GNU Affero General Public License v3.0 (AGPLv3).
Disclaimer: ProxyLoadouts is an independent fan-made project and is not affiliated with or endorsed by HoYoverse / COGNOSPHERE PTE. LTD. All Zenless Zone Zero game assets and trademarks belong to their respective owners.