Here is bug that I encounter right after I start the launcher.
Talic wrote: I guess we didn't understand each other.
As you said "The launcher will replace patch_d2.mpq with the median xl one and D2 game.exe with the 1.13c version".
I did noticed that, since I was unable to install 1.13c patch which was saying that I already have 1.13c version.
But as I said, for Median Xl Launcher to properly work. you need to have a patch_d2.mpq in your game folder, I didn't had that since my diablo 2 setup files are very, very old where after installation you don't have patch_d2.mpq in your game folder.
You see, that was the problem, launcher is looking for file that doesn't exist, at least in my case.
After I read .log file created by launcher it was easy to solve that problem by just installing some patch, 1.13d in my case, after that all worked just fine.
Thank You once again, launcher is really nice.
KaliszM wrote:Here is bug that I encounter right after I start the launcher.
Talic wrote:► Show Spoiler
Why, because I only installed diablo 2 right now to test the launcher, to provide some "feedback".
I'm curious why some have D2VidTst.exe outside D2 folder, it is by default in it, right.
HornedReaper wrote:I tried it but avast is being picky : it gets terminated and can't be launched because the source is "untrusted" yet. I don't thing you can do anything though Quirinus, but i still wanted to post about it so you know.
Can't wait to get back to medianXL (2017), I'm pumped!
Kyromyr wrote:Clicking on settings causes a soft-lock if launcher was run without admin privilege (such as when starting from installer). Closing the settings window by pressing alt-F4 also causes a soft-lock.