
Wuhua Mixin's servers were cut by its own developer at 00:10 on October 31. Sixteen days later, on November 16, Bilibili said it had filed a lawsuit and applied for arbitration. The game is still not running normally.
What happened at 00:10
Chengdu Longyuan Network Technology cut access to the official Wuhua Mixin servers without notifying the publisher. Its studio, Cipaishe, published an "operating entity adjustment" notice at almost the same moment, citing "irreconcilable differences over operating direction" with the publisher, and said operations would return to the development team.
Players saw a stranger's error message
Restarting the client did not show a maintenance notice. It showed: "This account has not yet obtained test eligibility." Ten minutes earlier they were doing dailies. Ten minutes later their account behaved as if it had never existed.
Two statements, two stories
Bilibili: unilateral breach
Fifteen hours later, bilibili's game publishing centre responded: Longyuan breached its contract unilaterally without any notification, terminated server access, and demanded players move their data to a third-party server. It added that Longyuan had recently run into debt disputes of its own, that Bilibili had been trying to help through various means, and that it had preserved evidence and backed up player account assets. It told players not to hand out passwords or verification codes.
Cipaishe: a disagreement over direction
Cipaishe's notice gave one cause — "a disagreement over operating direction" — promised existing assets would not be affected, and published a migration plan: top-ups paused on the old client, a web top-up portal opened, in-game items and physical merchandise for players who migrate.
Put the two notices side by side and the sharpest word is not in either headline. It is "migrate": who migrates to whom, to where, and who owns the data afterwards — none of it is stated.
74.77 million yuan in enforcement, and how debt reached the product
Citing public corporate and enforcement records from Tianyancha and Qichacha, Caijing Network reports that Chengdu Longyuan's total enforced amount is 74.77 million yuan, including 72 million yuan tied to a development contract dispute with Zhongshouyou. The company was listed as an enforcement target in August 2026 for 2.768 million yuan. On October 29, its legal representative Wang Wei was placed under consumption restrictions. Its 2025 annual report shows exactly one employee paying social insurance. Back in October 2024, founders Li Longfei and Yin Xueyuan had already become enforcement targets over a dispute with Baozou Comics, with 19.19 million yuan unfulfilled.
This is third-party corporate data, not a court ruling. But look at the timeline: consumption restrictions on October 29, servers cut in the early hours of October 31. Two days apart.
The most expensive step: handing over your top-up history
The migration page asks players to answer account questions: game UID, registration date, in-game birthday, friend list, most recently obtained SSR character, and the date and amount of their most recent top-up.
For a player, that is private data. For an account thief, that is an answer key. By November 2, multiple community members reported being hacked after asking publicly for help verifying their details. Bilibili's support team noted that Cipaishe's pass and migration page are not authorised by Bilibili.
The thefts were a design flaw, not an accident
Using "your most recent top-up amount" as an identity check means asking players to announce, in public, a number only they and the server should know. Anyone who asked a group chat "is this what I should fill in?" handed over their account.
November 16: damage control, not a resurrection
On November 16, bilibili's publishing centre announced progress: it has filed suit and applied for arbitration over the dispute, and has completed backups of players' legitimate accounts, character data and in-game assets. It said Longyuan's and its affiliates' debt disputes have entered judicial enforcement, that it does not recognise Longyuan's unilateral authorisation of a third party to operate the game and collect payments, and warned players against unofficial binding, registration and top-up channels.
Note the wording: litigation and arbitration. That moves the fight from social media into court, where the prize is liability, not a revived product. The game has been effectively offline for 16 days; for a live-service title that lives on patch cadence, two weeks of silence is a user-base reset.
My read
The lesson is not who is right. It is the account-ownership clause in publishing contracts. Publishers run the account system, the payment channel and customer service, but ownership, migration rights and inheritance of account data often come down to one line: "to be negotiated by both parties."
When a developer's cash flow breaks, that line becomes a migration form for players. Bilibili did the right thing by backing up data early and taking the dispute to court. It cannot buy back 16 days, and it cannot recover the accounts already stolen.
Can you still play Wuhua Mixin
A: The client was restored after Bilibili intervened, but there has been no normal version update since October 31. As of November 18, who operates the game still depends on the litigation and arbitration outcome.
Who actually holds player data
A: Bilibili says it has backed up legitimate accounts, character data and assets; Longyuan is pushing migration through a third-party pass. Both data sets exist, and a court will decide.
Will this affect other licensed games
A: Yes. It demonstrates how developer debt reaches the product: once a partner is under enforcement, servers, payment channels and accounts can all go down together.
Similar disputes are not rare; ongoing coverage of publishing and licensing is on gghubs.com. Figures here were verified against public reporting and third-party corporate records; rulings should be checked against court announcements.
How many games on your phone would disappear if the developer cut the line tonight? If it asked for your top-up history to get your account back, would you type it in?