CAUTIONUrgent notice: 0949 is caused by SEGA changing the bl server, which broke the machines. It’s nationwide; every SEGA title that uses bl will die
Updated 3/2, 4:30 p.m. This blog will keep updating on developments
TIPIt’s 9 p.m. now. Testing shows things are basically recovered. After you unplug the machine and restart it, check the net recharge records for refund information; if there is any, there’s no problem
0. Case provided by
That day the machine stayed on overnight until the maintenance shutdown; when it was powered on again at seven, it reported 8106. The 8103 happened right after finishing one round, because the den had been running 3x tickets nonstop
Many thanks to 红咸 on QQ for providing the case
1. SEGA ALL.Net billing mechanism
SEGA presumably has a revenue statistics system. Player actions such as inserting coins make the machine generate a billing log
To prevent arcade owners from running off and screwing over the company, this data isn’t stored on an ordinary hard drive but written directly into the machine’s encrypted area
Because its storage space is limited, when the machine connects to the network or during scheduled maintenance, it reports the bill to ALL.Net. Only after the server confirms receipt does the machine clear the records in the dongle, freeing space for a new day
2. What 8106 and 8103 mean
2.1 The 8106 warning
First, the system allows the warning to be manually turned on/off. When storage reaches the configured threshold and the machine has the ALL.NET warning enabled, it shows 8106 ALL.Net system warning
Why can it be turned off?
It’s like the low-fuel warning light in a car: a mechanic can pull the bulb out through the backend, but that doesn’t stop the fuel from running out. It’s essentially self-deception
2.2 8103 machine breakdown
When its storage is completely full or hits the limit threshold, the machine triggers 8103 ALL.Net system error
The thinking in Japan was probably: since we can’t record new bills, to prevent revenue loss we must refuse all play requests. So the machine locks up, won’t accept coins, and can’t be played normally
3. Why are cases appearing now?
The Chinese server’s 舞萌 DX uses a semi-buyout mechanism and shouldn’t need the same AA as the Japanese server, but SEGA’s underlying game code never had this accounting logic stripped out — it’s still quietly keeping books. Why the case appeared this time, my personal guess is a server-side cause
The recent server overhauls have all been patching up a pile of crap. When the operator adjusted the servers, it probably accidentally killed the relevant code logic, so the machine’s bill uploads aren’t processed / the server can’t properly receive them or send the clear-configuration, and the billing data keeps piling up in storage and can’t be cleared
4. Why the case came from a rhythm game den first, not a commercial arcade
Why did you give a rhythm game den case first? What if the den secretly changed something? If commercial arcades have no cases so far, then it’s fine
How to put it — an ordinary commercial arcade might take only a few hundred coins a day, so even if uploads fail for a few days it can still hold on. But machines with a time pass are different: players don’t need to spend money for multiplier tickets, so they just hammer ALL with 3x. On top of that, many rhythm game dens run 24h, which is inherently more pressure than an ordinary commercial arcade. That’s why the rhythm game dens’ machines hit the wall of their physical limit first, and why we have today’s case analysis
5. Solution
For 8106, you can turn off the all net warning in the net recharge records; 8103 has no fix
CAUTIONIf the machines at your arcade show this problem, make sure the arcade staff provide photos of the machine at the time of the error and other information to after-sales support
6. Current situation
If the higher-ups don’t fix the server-side bill receiving/clearing mechanism, or push a patch to strip the useless code out of the machines, then as time goes on, even ordinary arcades with low coin volume will eventually fill up and blow up along with the rest
While I’m at it, a recommendation for a maimai server monitoring site: Is the Wahlap Server Dead? — Real-time maimai server status monitoring, and maimai server failure and maintenance records
