Advertisement
Guest User

8/v/ Diablo 2 private server -update1

a guest
Oct 3rd, 2016
83
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.04 KB | None | 0 0
  1. Diablo 2 private server installation guide v1 -by 8/v/ doom2/diablo2 anon
  2. last upated: 10/1/2016
  3.  
  4. pre-requirements:
  5.  
  6. -32bit linux (or Windows with 32bit compatibility)
  7. -Diablo 2 / LoD assets (ie, the installed MPQs, DLLs, EXEs, INIs)
  8. -WINE (with patched sock.c)
  9. -SQL server (mysql/mariadb/postgres)
  10. -PvPGN source (or Windows appropriate binaries)
  11. -D2GS Windows binaries
  12. -general linux ability (eg, navigate, edit, compile)
  13.  
  14. current system / file information used for this guide:
  15.  
  16. -Slackware 14.2 (32bit) available from:
  17. http://mirrors.slackware.com/slackware/slackware-iso/slackware-14.2-iso/
  18.  
  19. -Diablo 2 / Lord of Destruction available from:
  20. **non/scurv/ link for people with legit CD install problems
  21. https://battle.net/account/management/download/
  22.  
  23. -WINE 1.8.3 with build script from:
  24. https://slackbuilds.org/repository/14.2/system/wine/
  25.  
  26. -WINE sock.c patch from:
  27. https://bugs.winehq.org/attachment.cgi?id=8866&action=diff
  28.  
  29. -PvPGN v.1.99.7.1-PRO available from:
  30. https://github.com/pvpgn/pvpgn-server
  31.  
  32. -D2GS 1.13d-build01 available from:
  33. http://pvpgn.pro/download/d2gs
  34.  
  35. Step 1) untar/bzip WINE, and manually apply patch to wine/server/sock.c:
  36.  
  37. Step 2) tar/bzip WINE, move it to its SlackBuilds directory, and run the build script
  38.  
  39. Step 3) install the WINE slackbuild package found in /tmp/
  40.  
  41. Step 4) untar/gzip pvpgn, make the build directory, and edit the cmake config to
  42. build WITH_MYSQL.
  43.  
  44. Step 5) cmake, make, then make install pvpgn
  45.  
  46. Step 6) edit the following path/etc/pvpgn/bnetd.conf settings appropriately:
  47. storage_path = "sql:mode=mysql;host=hostname;name=user;pass=pass;default=0;prefix=pvpgn_"
  48. track = 0
  49. servername = "diablo 2"
  50.  
  51. Step 7) add a realm to path/etc/pvpgn/realm.conf with your IP for d2cs:
  52. "Name" "d2 server for anons" yourip:6113
  53.  
  54. Step 8) edit the following path/etc/pvpgn/d2cs.conf settings appropriately:
  55. realmname = Name
  56. servaddrs = yourip:6113
  57. gameservlist = yourip
  58. bnetdaddr = yourip:6112
  59. motd = “optional info”
  60.  
  61. Step 9) edit the following path/etc/pvpgn/d2dbs.conf settings appropriately:
  62. servaddres = yourip:6114
  63. gameservlist = yourip
  64.  
  65. Step 10) unrar D2GS to the same directory as your Diablo 2 assets
  66.  
  67. Step 11) run wine regedit, import d2gs.reg, and edit the following keys under HKEY_LOCAL_MACHINE/SOFTWARE/D2Server/D2GS:
  68. D2CSIP = yourip
  69. D2DBSIP = yourip
  70. EnableGSLog = 0 (optional, D2GS makes big logz)
  71. EnableNTMode = 0 (optional, runs D2GS.exe as Windows service)
  72. MaxGames = 100 (*defaults to 1 so remember to change this!)
  73. MOTD = “optional info”
  74.  
  75. Step 12) create SQL db and grant privileges (db and user info from Step 6)
  76.  
  77. Step 13) start the daemons in the following order (check logs):
  78. *in Windows you may need to allow firewall access per app on first run.
  79. **the linux user running bnetd/d2cs/d2dbs needs r/w permissions to the
  80. **path/etc/pvpgn and path/var/pvpgn directories.
  81.  
  82. a) bnetd (will create db tables very first run)
  83. b) d2cs
  84. c) d2dbs
  85. d) wine D2GS.exe
  86.  
  87. Step 666) run Diablo 2 client and join the modified gateway to kill Diablo
  88. *client setup outside the scope of this guide
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement