Posted March 08, 2019
Let's face it, most people won't be able to connect to Diablo 1 Battle.net servers anyway, due to the topology of their network or other issues.
In which case using the IPX wrapper (supplied with the GOG version of the game) paired with Hamachi (separate download) is the way to go.
But using Hamachi poses another problem: finding players willing to play, namely finding existing Hamachi networks.
This is why I propose the following network naming scheme for GOG Diablo 1 Hamachi networks:
Hamachi network name: gog_diablo_x where x is a number starting with 1
Password: diablo
Once a network is full and more players are unable to join, a user needs to create another Hamachi network increasing the said number by one (gog_diablo_1, gog_diablo_2, ... etc.).
Anyone wants to play using this method? Feel free to join.
First network is already there: gog_diablo_1 (password: diablo).
In which case using the IPX wrapper (supplied with the GOG version of the game) paired with Hamachi (separate download) is the way to go.
But using Hamachi poses another problem: finding players willing to play, namely finding existing Hamachi networks.
This is why I propose the following network naming scheme for GOG Diablo 1 Hamachi networks:
Hamachi network name: gog_diablo_x where x is a number starting with 1
Password: diablo
Once a network is full and more players are unable to join, a user needs to create another Hamachi network increasing the said number by one (gog_diablo_1, gog_diablo_2, ... etc.).
Anyone wants to play using this method? Feel free to join.
First network is already there: gog_diablo_1 (password: diablo).
Post edited March 08, 2019 by AvidOldschoolGamer