A field manual, not a course

The Web3 Gaming
Ops Playbook

How one operator actually ran multi-account Web3 gaming operations across two titles — the matrix discipline, the airdrop workflow, the asset-safety rules and the review loop — written from the working notes, not from theory.

207accounts · Pirate Nation
≈ ¥1.62Mrealized across two titles
2full case studies inside
0shortcuts that risk the assets

Chapters

01
Account-Matrix Operations

How a 200+ account fleet is structured, scheduled and kept consistent — tiers, roles, daily rhythm, and the bookkeeping that makes scale auditable instead of chaotic.

02
Airdrop Campaign Workflow

From first announcement to claim day: evaluating a campaign, allocating effort across the fleet, tracking eligibility, and converting points into realized value.

03
Asset Safety & Risk Control

Wallet hygiene, approval discipline, and the rules that kept every account's assets intact through rugs, phishing waves and platform shutdowns.

04
Metrics & Review

The weekly review loop: what gets counted, what gets killed, and how a campaign's real hourly return decides whether the fleet stays or rotates.

05
Case Study — Pirate Nation

207 accounts, ≈ ¥600k realized. The full arc: entry logic, scaling decisions, the exit — and what the numbers looked like at each stage.

06
Case Study — MapleStory N

Dozens of accounts, ≈ ¥1.02M realized. A bigger title, a different economy, and the adjustments the second run demanded.

Read the source on GitHub

Every chapter lives in the repository as Markdown — fork it, diff it, argue with it: github.com/bizanyelab/web3-gaming-ops-playbook

Written by BizAnyE — Web3 operations & community, founder of the Youjian game-asset trading platform. Numbers are realized results from the author's own operations; methods are shared for education, not as a guarantee of returns.