Diablo III China client might have a local server? (+ request for 2.8.1 opcode login support)

[Espionage724]

Install:

"%ProgramFiles(x86)%\Battle.net\Battle.net.exe" --game=d3cn "--gamepath=%ProgramFiles(x86)%\暗黑破坏神III" --install

Update/validate:

"%ProgramFiles(x86)%\Battle.net\Battle.net.exe" --game=d3cn "--gamepath=%ProgramFiles(x86)%\暗黑破坏神III" --repair

Standalone launch (doesn't show in Bnet client for me):

"%ProgramFiles(x86)%\暗黑破坏神III\x64\Diablo III64ra.exe" -launch -w

• Diablo III64ra.exe reports Cheats: ENABLED in D3Debug.txt

• Has different command line flags too (there's more than these):

-battlenetgameaddress
-serverbindaddress
-serveradvertaddress
-servernetadapter
-serveradvertaddressreqh
-disablegameserver
-publicbnetserver
-p4client
-p4port
-p4user
-productionbnetserver
-betabnetserver
-buildserver
-loadworld

• -data allows using another D3 folder (setting to enUS D3 has in-game in English; D3 folder needs moved/renamed no-spaces):

"%ProgramFiles(x86)%\暗黑破坏神III\x64\Diablo III64ra.exe" OnlineService.SSO=true -launch -w -data C:\d3

• 暗黑破坏神III folder can be named something like d3cn instead (Bnet defaults to that name)
• Keeping that folder name might require Control Panel -> Region -> Administrative -> Change System Locale -> [x] Beta: Use Unicode UTF-8 for worldwide language support
• Version 2.8.1.101167 (newer than D3 and PTR) and seemingly doesn't allow log-in US/EU/KR (says a newer version available and prompts restart)
• Not sure how to change Bnet server URL (--battlenetgameaddress= doesn't seemingly work), but OnlineService.SSO=true seems to affect it (Bnet client above Play button has a small globe) along with the region Bnet client is signed-in with (separate from the region Play globe; you can sign-in Bnet with US and choose Asia region but that seemingly does a different Bnet address for D3 than Bnet with CN/China sign-in (something like cn.actual.battle.net vs cn.battlenet.com)
• -nullrender disables game client rendering (might be useful if there's commands to immediately launch a server?)

---

I'm curious to mess with it more if someone could help me out with NetEase account linking! (it can seemingly authenticate with actual CN servers but Bnet wants a NetEase account link that requires sending a SMS for Registration Verification that seemingly doesn't pass on NetEase's end without a Chinese number?) Doesn't seem the same like US DI's (Immortal) NetEase thing.

---

Since Diablo III64ra.exe appears to have a local server, maybe this project could support the log-in/auth for 2.8.1.101167 and not need the server emulation bits? I tried changing some version numbers in server source but no luck (D3 client log-in shows Error 3 or something).

When running Diablo III64ra.exe it default-connects to st21.bgs.battle.net, and 127.0.0.1 st21.bgs.battle.net in HOSTS seemingly works.