Skip to content

Valko's 8-Day Cancellation Didn't Fix What Broke Love and Deepspace

Ryan McDonald · · 5 min read · Open Mic

Put this on while you read

Valko's 8-Day Cancellation Didn't Fix What Broke Love and Deepspace
Photo by Alef Morais on Unsplash

On June 22, 2026, Infold Games revealed Valko, the 6th love interest coming to Love and Deepspace in its Version 6.0 update. 8 days later, on June 30, they cancelled him. Permanently removed from every server, not delayed or redesigned, with a promise that no new love interest would ever be added to the game again.

8 days is not enough time to fix a character. It’s barely enough time to understand what broke.

The Reveal That Died in 8 Days

Love and Deepspace had run 5 love interests for years, each with a devoted fanbase and a content pipeline built around romancing them. Valko’s trailer dropped with the usual fanfare: new art, new voice lines, a promotional video called “Home 2.0.”

The backlash arrived from 3 directions at once. None of them were the same complaint wearing different clothes.

Chinese players objected first. while Infold built an entirely new character from scratch, the kind of resourcing complaint any product team recognizes.

Then a line in the “Home 2.0” promotional video was read as echoing language from a 2024 domestic violence murder case in China. Players combing through an earlier chapter’s files then found asset codes and placeholder data connected to Imperial Japanese Army Unit 731, the WWII biological warfare division. 3 separate causes: neglected priorities, a tone-deaf line in the promo video and a production oversight nobody caught before it shipped.

Infold folded all 3 into one response: cancel Valko, apologize and move on.

What 8 Days Solved

The Caleb problem, the actual resourcing grievance underneath the loudest backlash, was never about Valko existing. It was about 5 characters getting starved while a 6th got built. Killing the 6th character doesn’t feed the other 5. It only stops the bleeding. The job of fixing what actually caused Caleb’s 500 dry days is a job Infold never started.

The Second Backlash

Global fans who’d never seen the offending video or the buried asset codes woke up to a cancelled character they were still excited about. . Protesters showed up at Papergames’ Shanghai headquarters with funeral chrysanthemums and exorcism offerings, some mourning the character’s death, some mourning the decision to kill him. By Anime Expo 2026, the community wasn’t unified around a resolution. It was split into 2 camps, each certain the other had won.

Never Again

Infold offered compensation: free outfits and photo poses. Then Infold announced the policy: no new love interests, ever, only existing characters going forward.

A permanent ban on an entire content category doesn’t fix a resourcing complaint, a bad script line or a production oversight. Infold is admitting it doesn’t trust itself to run that process again. The 5 existing love interests didn’t get their neglect solved. They got a smaller team competing for the same limited resources forever, because the option to bring new investment and new attention to any character is now permanently closed.

◆ Before you read on

What's the PM move here?

Think about who actually got heard in this story versus who was just loudest.

Backstage Pass ■ Access Granted

What 8 Days Bought and What It Didn't

A cancellation answers a crisis, not the complaint underneath it. Infold moved fast enough to stop the immediate backlash. 8 days is a genuinely quick reaction. But the resourcing grievance under the loudest complaints was about 5 neglected characters, not the new one Infold cancelled. Killing Valko didn’t touch that. When you cancel something under pressure, ask whether you’re addressing the root complaint or just removing its most visible trigger.

3 separate problems dressed as 1 crisis need 3 separate fixes. A staffing complaint, a tone-deaf script and a QA miss got bundled into a single “cancel it” decision because bundling is faster than diagnosing. But each of those problems has a different owner and a different fix: a roadmap conversation, a review process for promotional copy and a file-hygiene pass on old assets. Treating 3 causes as 1 crisis means you fix none of them properly.

A permanent ban outlives the crisis that caused it. “No new love interests, ever” tells the team it can’t be trusted to run its own launch process again. A 6-month pause to fix the review pipeline protects users. A permanent ban protects the team from ever having to prove it learned anything.

The 5 characters Chinese players were defending are still short on story updates. The global fans who wanted Valko still don’t have him.

◆ Your Take

The next time backlash forces a fast decision, are you fixing the resourcing problem underneath it or just removing what's loudest?