The error-prone Diablo 3 was again hit by Error 73, per reports.
The Diablo 3 forum was filled with messages from players who claimed that they could not connect to the server and were receiving Error 73 instead, Ubergizmo reported Nov. 1.
The report claimed that the thread extended to nearly 30 pages.
Developers reportedly have not yet taken any action to fix the problem.
Diablo players previously encountered this problem in May when Diablo 3 servers sent out Error 73 and Error 37 messages to players who tried to log in.
Error 73 is a message that appears when the servers are down. The login servers of Diablo have a limited capacity and when millions of players log on to the game, the server is unable to bear the load.
In August, Diablo 3 faced an opening day bug and players got Error 3006.
Blizzard, sent new hotfixes for the game October-end. The fixes included issues where Sokahr, the Keywarden became stuck at 1 point of health.
"Other fixes include a fix to an issue that caused the Butcher to go idle when performing his Charge attack during 'The Imprisoned Angel: Kill the Butcher,' part and which allowed some players to continue to dual-wield two-handed weapons under extremely rare circumstances, a fix for the crash that could occur when gold dropped in bad locations, and more," iTechPost reported.
Diablo 3 was released May 15, 2012.
