The Blood of Dawnwalker Sells 1 Million Copies in Roughly 48 Hours: How a Small Team of Ex-Witcher 3 Veterans Outdid AAA With About 160 People#

Hi everyone, Long Zhuiri here. This week our editorial desk was nearly taken over by a single piece of news — Rebel Wolves, the studio founded by core veterans of The Witcher 3: Wild Hunt, sold over 1 million copies within roughly 48 hours (less than 2 days) of the launch of their dark fantasy action RPG, The Blood of Dawnwalker. When the news first hit our group chat, I was holding a cup of cold coffee, watching three hundred-plus messages scroll past in a matter of minutes — a revenue story argued into our editorial drama of the year.

By tradition, a topic like this is more than I can argue through alone, so I dragged Chasun into it. Chasun is the closest thing our desk has to a calculator, the designated debunker of anything that merely “feels impressive,” someone who insists on breaking every emotion down into tables and numbers; I am exactly the opposite — what I care about is what each of the people behind those 1 million copies felt in the moment they sat down in front of the screen. In this feature, we take the “small team outdoes AAA” story apart from these two completely different angles.

1. First, the Numbers: Just How Solid Is “1 Million in 48 Hours”#

The data first, so this doesn’t read like two editors talking to themselves. The Blood of Dawnwalker officially launched on September 3, 2026, and the studio announced on September 5 that global sales had passed 1 million copies. Do the math, and from going on sale to the official million-seller confirmation took just about 48 hours, less than two days. Meanwhile, the scores it picked up from major outlets look like this:

1.1 The Review Scores at a Glance#

Chasun spoke first after studying the numbers: “There’s something very interesting about this score set — it isn’t the fractured kind of high score where ‘outlets rave and players rage.’ Scores in the 83-and-84 range usually mean outlets and players feel largely the same, with little inflation. For a brand-new IP with no established fanbase, built by a small team, this kind of ‘consensus high score’ is harder to earn than simply scraping past 90.”

I added a line from the side: “Right — I’ve seen far too many 9-out-of-10 games whose players refunded them into liquefaction. Scores are just the doorway; 1 million copies is the vote of real money.”

1.2 Why “1 Million in 48 Hours” Is a Big Deal Right Now#

You might think 1 million copies is nothing in today’s market. Chasun immediately slapped a comparison table on me, and only after tracing it line by line did I register the weight of this.

Chasun pointed at the last row: “See, once this row sits here, plenty of readers’ first reaction will be ‘160 people isn’t exactly small.’ But swap what it’s being measured against — it’s going head-to-head with the top-tier AAAs that run five or six hundred people on budgets heading north of two hundred million dollars. Taking 160 people into that weight class and hitting 1 million copies in two days — luck doesn’t explain that.”

2. Who Exactly Is This Team: From 15 People to 160 in Four Years#

To understand where the 1 million came from, you have to look at the people first. Rebel Wolves is no fly-by-night outfit that appeared out of nowhere — it is a band of veterans who “waded through” The Witcher series.

2.1 The Core Lineup: CDPR Veterans Head Out#

At the team’s core is Konrad Tomaszkiewicz, who served as game director on The Witcher 3: Wild Hunt and as a senior producer on Cyberpunk 2077. Leaving alongside him was a large group of core members who had fought at CD Projekt Red side by side for years. What these people share above all: they built a world-class narrative RPG with their own hands — they know how a game of that caliber runs from the inside.

Chasun cut in here: “That matters far more than ‘how many years of experience.’ The market doesn’t lack veterans of a decade or more, but the overwhelming majority of them worked a single station on an assembly line. This group actually saw the finished product and understands how every link of a top-tier RPG — story to combat to levels — meshes with the next. They carried that ‘complete methodology’ out of the big studio, and that is the capital that lets them fight at small scale.”

2.2 From 15 to 160: A Restrained Growth Curve#

Per the team’s public disclosures, Rebel Wolves started with only about 15 people and, over 4 years, grew to about 160 by the time the game shipped. Note the rhythm of that expansion — not a one-shot leap to several hundred, but steady additions paced to development milestones.

I’ve laid out the growth curve below so you can see just how restrained they were:

Chasun ran the math: “160 people × 4 years — even estimated at Europe’s high per-head development costs, this team’s total labor cost is probably a rounding error next to a comparable top-tier AAA. In other words, with a smaller budget they built a product bold enough to arm-wrestle top RPGs on volume. That is the core economic logic of ‘outdoing AAA’ — not making the same thing with less money, but using a structural cost advantage to make something just as competitive.”

3. The Industry View (Chasun): How Do 160 People Beat 500?#

This section is mainly Chasun’s to deliver, with me playing the heckler in the next seat. This is honestly how our editorial desk works — nobody wins by authority; every view gets put out in the sun.

3.1 Is the Budget Spent on “Repeat Labor” or on “Creation”?#

A large share of a AAA budget never goes into creation at all — it goes into management and coordination. The more people, the steeper communication costs climb, exponentially. A single task passes through design, programming, art, level design, QA, localization, outsourcing, and more between request and delivery; every handoff is a cost, and every rework is extra money.

Chasun: “The biggest dividend of a small team is a short communication radius. In a 160-person studio, an idea might need only one meeting between a handful of people from proposal to shipped change. That ‘flatness’ isn’t laziness — it’s money and energy saved and slammed back into the content itself.”

I pushed back: “You’re right, but let me say a word in defense of the big studios. Their processes aren’t stupidity — they exist to absorb risk. Once you have hundreds of people, only process keeps output stable. A small team can bet 160 people on innovation because everyone there can carry more responsibility; a big studio without process would have 500 people in chaos in no time. So this isn’t right versus wrong — it’s two entirely different organizational philosophies.”

3.2 50-70 Hours of Content: A Small Team’s “Art of the Trade-Off”#

The Blood of Dawnwalker officially promises 50-70 hours of content. From a team of about 160, that is no small boast.

Chasun tapped the top two rows: “Look closely — they didn’t build ’the world’s biggest map’; they built the densest map. That’s the smartest play available to a small team — if you can’t out-volume a giant, compete with lower redundancy and higher information density. 50-70 hours sounds like a lot, but think it through, and chances are not one second of it is filler built to make you run across the map.”

3.3 The Core Innovation: Turning “Traditional RPG Waste” Into “Gameplay”#

Chasun saved for last the point he most wanted to make — the game’s biggest mechanical innovation: the 30-day time limit, together with the Dawnwalker’s dual day-and-night forms.

What is the greatest time-waster in the traditional open-world RPG? Players wandering aimlessly with nothing to do. The Blood of Dawnwalker simply hands you a real 30-day deadline — inside this open world you must make your choices against a countdown, with no infinite deferral. The setting forcibly eliminates, at the design level, the weakest part of an open-world RPG: meaningless freedom.

“Do you know what that means?” Chasun’s eyes lit up. “It means the same volume of content, with a higher share of it genuinely experienced. In an RPG with no deadline, a player might spend 20 of 50 hours wandering; in an RPG with one, every minute pushes you toward a meaningful decision. That’s doing addition with design and multiplication with experience.”

I picked it up: “Now we’re at the heart of it. One of us counts data and the other talks feelings, but on this mechanic we agreed for once — it serves both art and efficiency. In narrative it is dark-fantasy fatalism; in design it is the optimal solution for cost efficiency. One mechanic solving both at once is, to me, this team’s most remarkable achievement.”

3.4 Marketing and Publishing: The Role Bandai Namco Plays#

One more piece belongs here: this small team could carry its target scale partly because of its publisher. The game’s publisher is Bandai Namco Entertainment, handling worldwide promotion, distribution channels, and multilingual localization.

I raised this at a planning meeting, and Chasun immediately added two observations worth writing down:

Chasun stressed this one: “This is a classic ‘small developer plus big publisher’ structure. Rebel Wolves never had to build its own marketing and localization departments — precisely the areas where big studios pile on resources and small teams bleed energy. Every ounce they saved went to the one place that decides a game’s quality — the game itself. So strictly speaking, ‘outdoing AAA’ isn’t only the development team’s achievement; it’s also this pairing hitting its mark.”

I’ll admit I felt something about this point. Many small teams die from “doing everything themselves” — development, marketing, and platform operations all at once, and none of it done well. Handing what you’re bad at to people who are good at it is itself a quiet form of professional competence.

4. The Player and Narrative View (Long Zhuiri): It Reminded Me of the Afternoon I First Played The Witcher 3#

Chasun’s analysis ends there; now for what I felt. However pretty the data, a game is finally something a person sits down and plays.

4.1 The Dawnwalker Identity Is the Narrative’s Core Engine#

The “Dawnwalker” is a being caught between human and vampire. Human by day, monster by night — power beyond the human on one hand, the pull of bloodlust on the other. This identity is not a simple “you got stronger”; it is an open question about the boundary between person and monster.

I value this kind of design enormously. Many RPGs hand the player a “hero”; The Blood of Dawnwalker hands the player a symbiote that could lose control at any moment. Every decision you make in the game answers the question, “When power cannot be tamed, are you still human?” That is a far more elevated premise than “save the world.”

4.2 The 30-Day Limit: Making Every Choice “Hurt”#

As a player, the 30-day limit is my favorite part — because it is the design that truly turns your choices into costs.

• Save this town, and you may be abandoning another place that needed you;
• Choose to suppress the bloodlust, and you may pay for it in reduced combat strength;
• Make a decision on day 20, and on day 28 you discover the consequence you never foresaw.

That pressure of “time running you down” is something the overwhelming majority of open worlds cannot give you. It forces you to take every decision seriously, instead of the usual arrangement — you can always reload anyway, and there’s always more time.

4.3 Why It Reminded Me of The Witcher 3#

Honestly, certain moments in The Blood of Dawnwalker took me straight back to the afternoons I spent on The Witcher 3. Not because it copies The Witcher 3, but because of that feeling of “the whole world taking seriously what I’m doing.”

This team, grown out of The Witcher series, carried over intact the taste of “every side quest is worth doing, every NPC has a story” into the new game. I would even say that taste is worth more than a big studio spending tens of millions on one stunning cutscene.

You might ask why that feeling of “every decision being taken seriously” has become so hard to find in today’s big-studio games. My answer may sting a little: it’s not that the big studios can’t make it — it’s that their scale and processes make it ever harder to pay that much attention-cost to every detail. In a big studio’s system, a side quest may be one row in a tracker, filled in by a single designer; in a small team, it might be something the founders argued over repeatedly. Players can feel that difference in attention, even if they can’t name exactly what changed.

Here’s an example. In many open-world games, NPCs stand in place repeating the same line like a machine. In The Blood of Dawnwalker, as your choices across the 30 days accumulate, the same character’s lines and attitudes change. And that change isn’t a crude “affinity switch” — the character genuinely remembers what you did. That kind of detail is affordable only when few hands are involved; the more people, the harder it gets — every detail becomes “work to be handed off within a process,” the more handoffs, the higher the polish costs, and eventually it’s usually cut.

So the way I see it, a small team’s real competitiveness isn’t “fewer people, therefore cheaper” — it’s “fewer people, therefore attention concentrated on the blade.” That is something no budget can buy, and the last thing that should be lost in the age of AI tools.

5. Lessons for the AI Era: What a Small Team Outdoing AAA Means for Game Development#

At this point comes the most contested part of the feature. One of us argues from industry, the other from craft, and together we owe you a clear account of what this means long-term — especially now, with AI reshaping the games industry.

5.1 Clashing Views: Success “Because of AI,” or “Despite No AI”?#

This one consumed a whole afternoon of editorial debate, Chasun and I on opposite sides.

Chasun’s view: In a sense, Rebel Wolves’ success sets the template for indie development in the AI era. When AI tools sharply lower the barrier to art assets, localization, even parts of programming, games that once required hundreds of people may someday need fewer. This team proved that “headcount is not a prerequisite for quality,” and that hands enormous confidence to every small and mid-size studio.

My rebuttal: I’d argue the opposite — The Blood of Dawnwalker’s success was not saved out of AI, but out of its creators’ taste and judgment. AI can save you time; it cannot invent a mechanic like the 30-day limit or a narrative angle like the Dawnwalker. What it actually proves is this: when a team pours every saved resource back into creative quality, good content still beats piled-up volume. AI is an amplifier — it magnifies what was already there. With good taste, AI helps you do more and better; without it, AI just helps you manufacture mediocrity faster.

5.2 The Long-Term Lessons for the Industry#

Argue as we might, a few points of consensus won over the entire desk, and I’ll set them out as three:

1. “Scale” is no longer the moat — “density” is. The “giant maps” and “massive content” big studios pride themselves on are being challenged head-on by small teams using “higher information density, lower redundancy.” Players don’t want big; they want every inch to be worth it.
2. A core creative team’s “complete methodology” is worth more than “headcount.” Rebel Wolves’ greatest asset isn’t its roughly 160 people — it’s the group that saw a top-tier RPG through to shipping and knows how every link meshes. That experience of “having finished a complete work” is something AI cannot replace.
3. AI will amplify the divergence in “taste” and “judgment.” As tool costs approach zero, the industry’s dividing line stops being “who has more hands” and becomes “who has better taste and bolder ideas.” That may make the industry harsher — and may let genuinely good games surface faster.

5.3 A Few Reference Points for Developers in China#

Having covered the international case, our desk also briefly discussed what this means for Chinese games and domestic indie teams. The topic wanders a little, but I think it’s useful to you too, so it goes in as written.

Put those together and they point at one plain truth: small and mid-size teams shouldn’t compete with big studios on “who is bigger,” but on “who is more focused and who judges better.” As The Blood of Dawnwalker teaches: doing one thing deeply moves players more than doing many things widely. That holds true in every country’s game industry.

6. Editorial Wrap-Up: Why This Game Moved Us#

By the end of this feature, Chasun and I — for once — stopped sparring. Each of us contributed a single-line summary for everyone reading this.

Chasun (industry and data view): On the numbers, The Blood of Dawnwalker is one of the cleanest “cost-versus-reputation” balance cases in recent years. With about 160 people and 4 years, it built a product that fights top-tier AAA to a standstill on both scores and sales. The games industry’s “cult of scale” is loosening — a AAA-caliber work does not necessarily need a AAA-sized team.

Long Zhuiri (player and narrative view): What I’d rather say is that it made me believe something again — games are finally made out of creators’ taste and sincerity, not out of budgets. When a team that started at 15 people spends 4 years turning “the boundary between human and monster” into a 50-70-hour work that 1 million players are glad to pay for, that says more than any score: good stories and good ideas remain this industry’s scarcest and most valuable goods.

Whether the “1 million in 48 hours” pulled you in, or the Dawnwalker’s identity moved you, my advice is to play it yourself. Data can mislead and scores can distort — but when a world takes every one of your decisions seriously, no one can fake how that feels.

Thanks for reading, everyone — see you next week.

— Long Zhuiri and Chasun, NTGame Editorial Team