And black bars on the sides, that thing got old decades ago.Ģ. Then go and fix it, stop cutting corners, there are more complex games out there, and dont tell us you cant mess with the code, you already did. This way, you'd happily play online on 2.0 while supporting TCP/IP with their trashy classic network code. So why not just leave this old client/server code intact, with a new 2.0 client code in addition to that. The original client/server code in Diablo 2 was developed in a different day and age when Blizzard North wasn't even that great at it.īesides, how serious attacks to or gamer safety did Diablo 2 cause during the ages when it's had TCP/IP support? Given Blizzard's arguments, it ought to have been horrible, but was it really? Maybe bot developers have benefitted somewhat? Who knows? Dupe testing on a local machine before going live? But they say Diablo 2: Resurrected already has seen bots though, so. So, how does it matter that this ancient server code remains in Diablo 2: Resurrected for it to act as a server in TCP/IP scenarios? It will most certainly not have anything to do with 2.0 in the slightest. Diablo 2: Resurrected does not play on regular. And if you know a thing or two about the servers by reverse-engineering the code, you can develop hacks that work on ! Boom, security problem.īut. This can be a security issue because with that, you may be revealing server code as well in case it's similarly designed. So, it already has the client and server code.
Since Diablo 2 supports TCP/IP, Diablo 2 needs to be able to act both as a client and a server.
Yeah, the bit about TCP/IP is so suspicious and hand-wavy.
0 kommentar(er)
