Highlighted the red area, and for some reason it seems soooo familiar to me and I can't put my finger on it. In the meantime, here’s our Diablo 2: Resurrected guide if you’re starting the game for the first time and need a smooth leveling up path towards Nightmare and Hell difficulty.Ug 21 17:17:48 pvpgn::bnetd::ipbanlist_check: lastcheck: 1534886223, now: 1534886268, now-lc: 45.Īug 21 17:17:48 pvpgn::bnetd::ipbanlist_check: checking Īug 21 17:17:49 pvpgn::bnetd::sd_accept: accepted connection from :61016 on 199.195.118.250:6112Īug 21 17:17:49 pvpgn::bnetd::conn_create: sessionkey=0x1534886370 sessionnum=0x00000001Īug 21 17:17:49 pvpgn::bnetd::sd_accept: client connected to a bnet listening addressĪug 21 17:17:49 pvpgn::bnetd::handle_init_packet: client initiated bnet connectionĪug 21 17:17:49 pvpgn::bnetd::conn_shutdown: connection already closedĪug 21 17:17:49 pvpgn::bnetd::conn_set_class: added latency check timerĪug 21 17:17:49 pvpgn::bnetd::_client_auth_info: AUTH_INFO packet Īug 21 17:17:49 pvpgn::bnetd::conn_set_gamelang: setting client gamelang to "enUS"Īug 21 17:17:49 pvpgn::bnetd::_client_auth_info: selected "IX86ver1.mpq" "A=3845581634 B=880823580 C=1363937103 4 A=A-S B=B-C C=C-A A=A-B"Īug 21 17:17:49 pvpgn::bnetd::sd_tcpinput: read returned -1 (closing connection)Īug 21 17:17:49 pvpgn::bnetd::conn_destroy: closed bnet connection Connecting to EU or US B.net would not update the LoD, so as a last resort I connected to the ASIA B. Expect an update with hotfix notes to appear on Blizzard’s Diablo 2 forums in the next few days. Hello I recently installed the French 1.14b client straight from Blizz onto my father's computer and then I saw I needed 1.14d for D2DX to work but I was struggling to find that 1.14d patch file. In addition, Blizzard is currently fixing crash bugs and an AVX issue that is preventing players from starting the game up. We’re actively working to find a solution to these issues.” We anticipate this process will take a few hours to complete.įor players unable to create or join game lobbies, we’ve been evaluating activities that have prevented them from being able to play in those sessions. Many of these characters are already in the process of being unlocked. “Furthermore, our team is working to resolve the issue of character lockouts. The current solution for now? Players need to use different names for offline and offline characters apparently using the same name for both is related to the bug.
It’s a temporary measure, as Blizzard is intending to release a permanent fix for the bug on PC, then for consoles.
However, Blizzard took the game offline for unscheduled maintenance, and it was sorted out a couple of hours laters. In fact for the past few days since its Friday rollout, there were reports of disappearing characters. Keeping to tradition with online Blizzard game launches, the company’s latest remaster of Diablo 2 is not experiencing a smooth launch.
0 kommentar(er)
