M17 Released!

Game news and forum updates
User avatar
Texalic
Core Lord
371 | 54
Common Love Badge
Earned over 20 cookies
Common Supporter Badge
Donated 1 time
All works great, thank you all who are involved in the process of making the best mod ever. :thumb:

Changes are visible from the very start, I really like it. :clap:
User avatar
tylerfar
Pit Knight
119 | 1
Great Supporter Badge
Donated 5 times
Hey Folks,

Thanks to all of you for keeping this game fresh.

I am having similar issues with others regarding the line halt error that is listed on the first page of the forum. I dont mean to be redundant, but I am not tech savvy enough to understand the process as to how to try and fix the error.

Ive been playing MedianXL via the launcher with no issues, I updated it to run the game earlier today, and the halt exception appears when attempting to join a game (im sure its the same situation for everyone else that ran into the problem) I just dont understand the tech jargon well enough to fix it. Can anyone PM me a dumbed down version that might help me bypass this issue?

Thanks
mxl17
Dark Huntress
10 | 0
Dear god what's the drop rate for a "Runestone" now?

Been maybe 10 levels dry of a single one.
5/6 of the other stones.
User avatar
Meddle
Vampiress
39 | 5
Great Supporter Badge
Donated 5 times
so even using the instructions for D2SE mod manager i bricked my vanilla diablo2 which is a huge shame since the reset is coming and i have friends who want me to play it with them. (i get the "failed to retrieve" error on vanilla d2 but median works fine)

i'll have to reinstall everything and not play any median for now i guess :\
leroy989
Imp
4 | 2
Now one more QoL that would really improve things, if it was possible to ever get it working with new core, then having the ablity to hold shift+click items to quick transfer items back and forth from stash and inventory.
User avatar
tylerfar
Pit Knight
119 | 1
Great Supporter Badge
Donated 5 times
I wiped my old files and reinstalled D2/LOD/Median XL. It got me into the game, but the launcher opened in windowed mode, I went to change the settings and now im getting a critical error while trying to initialize DirectDraw, any suggestions?
User avatar
CrownOfHorns
Dark Huntress
10 | 0
So I reinstalled D2 which was 1.14b. Installed the 1.13c patch and then Median XL. Came up with a "Failed to retrieve process" error. Ran as admin and came up with d2data.mpq corrupt. Dying to play on this 4 day weekend.
User avatar
Solfege
Harpylisk
1461 | 209
Common Posting Badge
Posted over 1.000 messages
Legendary Popularity Badge
Has a thread with over 250.000 views
Great Love Badge
Earned over 100 cookies
Common Guide Badge
Created a complete character guide
K, been fighting with this "2239" error for 3.5 hours now. Game works fine on SP, but error pops up when trying to create/join game on TSW. Using standard D2SE/PlugY setup (PlugY disabled when joining TSW, obv) via WINE on Linux. Read through forum threads/posts and tried the suggested solutions ppl offered. Anyone on Linux have this problem and/or could help me figure out what I'm doing wrong?
Nicolas72
Jungle Hunter
25 | 1
Solfege wrote:K, been fighting with this "2239" error for 3.5 hours now. Game works fine on SP, but error pops up when trying to create/join game on TSW. Using standard D2SE/PlugY setup (PlugY disabled when joining TSW, obv) via WINE on Linux. Read through forum threads/posts and tried the suggested solutions ppl offered. Anyone on Linux have this problem and/or could help me figure out what I'm doing wrong?


I had the same problem earlier but after fiddling with the plugy.ini it worked.
Here is mine (Linux Mint-Wine-D2SE&Plugy)

[GENERAL]
ActivePlugin=1
DisableBattleNet=0
ActiveLogFile=0
DllToLoad=MXL.dll
DllToLoad2=[GENERAL]
ActivePlugin=1
DisableBattleNet=0
ActiveLogFile=0
DllToLoad=MXL.dll
DllToLoad2=
ActiveCommands=1
ActiveCheckMemory=1
ActiveCommands=1
ActiveCheckMemory=1

This is the only important part. After that the error disappeared. Also make sure your plugy is version 10.0
User avatar
Solfege
Harpylisk
1461 | 209
Common Posting Badge
Posted over 1.000 messages
Legendary Popularity Badge
Has a thread with over 250.000 views
Great Love Badge
Earned over 100 cookies
Common Guide Badge
Created a complete character guide
Nicolas72 wrote:
Solfege wrote:K, been fighting with this "2239" error for 3.5 hours now. Game works fine on SP, but error pops up when trying to create/join game on TSW. Using standard D2SE/PlugY setup (PlugY disabled when joining TSW, obv) via WINE on Linux. Read through forum threads/posts and tried the suggested solutions ppl offered. Anyone on Linux have this problem and/or could help me figure out what I'm doing wrong?


I had the same problem earlier but after fiddling with the plugy.ini it worked.
Here is mine (Linux Mint-Wine-D2SE&Plugy)

► Show Spoiler


This is the only important part. After that the error disappeared. Also make sure your plugy is version 10.0


Yeah, mine looks like that, too--except I didn't have the "DisableBattleNet=0" line, but adding it didn't change things. And yeah, it's PlugY 10.00. Thanks for the help, though. I'll keep playing around with it a bit longer.

I just don't get why SP works fine, but TSW doesn't. Almost positive it's something super simple that I'm overlooking...

Edit:
It seems PlugY is the thing loading MXL.dll, so having the "Use PlugY" box unchecked means MXL.dll isn't being loaded. Same error in SP now with box unchecked, but no problems in SP or TSW as long as box is checked. fml.

@Nicolas72, giving you a cookie for your efforts, and because my stupidity is embarrassing. :lol:
Edited by Solfege 8 years.