Please consider reimplementing TCP/IP in D2R
Nov-03-2022 PSTTCP/IP support must be included in D2R as it offers a variety of choices and advantages to users without any major foreseeable negatives.
It will give a variety of possibilities to players, for example:
(SP means Single Player MP = Multiplayer)
Direct connections are typically more stable than playing MP via Bnet servers of Diablo 2 Resurrected Ladder Items for sale.
- Being able to access the /players command when playing with your friends, you can run your content on the /players 8 command without needing eight players.
A lot of flexibility (less dependence on Bnet servers to play even when the servers are crashing and switching between MP and SP using similar characters).
Modded multiplayer could be an option (Note that I'm not advocating to make private servers available, it's a completely separate discussion) It's a lot of fun to play some game's skill/monster/item overhauls with a few friends.
- Less specialized benefits, such as the ability to host real LAN events and auto-rushing SP characters.
The possible downsides include "security dangers" and possibly attracting more pirates, but I believe that restoring TCP/IP could bring in more sales that could surpass the loss that could be incurred from pirates. Many users didn't purchase D2R due to the absence of TCP all by itself. I'm not sure it's going to be a huge amount of work, cheapest d2r ladder items especially when you consider that TCP was inside the TA (and possibly in the beta, but I can't recall) but was disabled. It appears to be fairly simple to implement.
I encourage you to contribute your comments and suggestions I'm hoping that this thread will gain momentum and that TCP isn't forgotten or swept under the carpet. Lost forever.