Diablo 4 Different Versions

[Dorinda Avancena]

Myfriends and I preoredered Diablo IV. Other then the long line for log in, we were all able to log in and play. There is a bug or issue while trying to create a party. It says different game versions cannot play together. We are currently all relogged and sitting in the line to get back in again to see if this has fixed the issue.

Completly closing out Blizzards launcher, and then restarting. seemed to fix the bug. and now, ive been disconnected. 134 minute que to get back in. none of my friends were disconnected. lets see when i get back in if we have the bug again.

The question has come up numerous times: how do I run a mod for an older version of Diablo II when I am patched up to the latest version? That question has almost as many answers as there are Diablo II mods to play. This article will start out with solutions for Windows users, as that is the platform I know. Article feedback on anything I don't cover is greatly appreciated and would appear in future updates.

The first requirement is to have the resources for setting up all the versions you are interested in running. Most mods are for v1.10 final, but some popular mods still use v1.09b or v1.09d, and mods are appearing for v1.11. The latest version is v1.11b. You should have the CD-ROM's for Diablo II and Lord of Destruction; depending on when your CD's were released they would have v1.00 and v1.07 respectively or later. Then you need the clean patch files for each version, you can get them at [url= =adt0387p]Blizzard's Diablo II patch site[/url], our own [url= =category&cat_id=27]File Center[/url], or other locations around the Internet that you trust. You will need to get a set of files for each version you want to run, but with careful file management you only need to to this once.

One method is to reinstall the game completely for each version, each into its own game directory selected at install time. The default directory suggested is C:\Program Files\Diablo II, so one way might be to incorporate the version into the game directory name, like 'D2v109d'. It is the least complicated method, but most wasteful of disk space. (It may be the only possibility for Mac users.) For Windows users, the game creates a number of entries in the Windows Registry, and each install will overwrite the previous install's settings. So the Registry will end up with your latest version installed and you will be ready for Battle.net. In the mod world, the most important setting for each version is the default save directory. (See the appendix for more Registry information.)

Most of the files in Diablo II and Lord of Destruction are static, and you don't need to change them. The files that do change between patches are those with new timestamps: patch_D2.mpq, the DLLs, and game.exe. All of the other new files in your Diablo II directory are logs and other miscellaneous stuff. (The file diablo ii.exe is not the game executable and can be ignored.)

Now for the setup part. If you want to backtrack to previous versions, you need some clean files for each version. The painful way is to reinstall D2 and LoD, then patch your way up to the current version. Another way is to download Blizzard's unreferenced game.exe from the patch site, which will replace your current game.exe and allow using earlier patchers (back to v1.10 beta) on your current setup. A third way is to use a modding tool called an mpq extractor (I recommend [url= =file&file_id=115]WinMPQ[/url]) and get a copy of game.exe right out of d2char.mpq --- v1.00 from the original Diablo II 'Play' CD-ROM, v1.07 from the original Lord of Destruction CD-ROM. File extraction is beyond the scope of this tutorial, but you can get details from The [url= =file&file_id=1086]Beginner's Guide to Mod Making[/url], exercises #1 and #3. At each patch level, make a reference set of the files I mentioned previously and save them in their own directory. Also at each level, copy the game.exe file in the Diablo II directory and rename the copy something like 'game109d.exe', 'game110.exe', and so on---after all, you can't have them all have the same name in the same place.

Now you are ready to configure all these versions for the mods you are interested in. Each mod should have installation instructions, but in general there are two ways to set them up. The preferred method is to create a subdirectory for each mod under your game directory. This assures the mod files do not mix in and corrupt your Battle.net-ready installation. Some mods suggest or even require you install in your game directory instead, so be sure you have those reference sets safely stashed before installing any. Those mods require file swapping to switch between running the mod and running any other form of the game. You can create a subdirectory for even these mods, then move the DLLs and patch_D2.mpq there. Also move any data subdirectory the mod install created, as some mods work on external files (also known as -direct -txt mode, see The Direct Switch tutorial).

Mods in their own directories may have some DLL files and patch_D2.mpq already. If you are running an earlier version, you need all the DLLs and patch_D2.mpq from your reference set as not already present. You can also copy that version's game.exe there. A complete set of clean patch files takes up less than 15MB, so many copies of these files won't chew up much drive space. Be careful not to [i:030a3f30bc]overwrite[/i:030a3f30bc] any files from the mod with files from your reference set!

How do we run the mods after they are set up? How do we keep character files from one mod away from all other mods or the unmodded game? You need mod management now. Newer mods come with a feature called plugY, which includes the ability to use and choose custom mod save directories (edit plugY.ini's save path for your own selection). The Keep also has a number of mod management tools on hand. The bare minimum is the mod shortcut shown in The Direct Switch tutorial. The Mod Running Script available in our management tools area and a Windows shortcut each need a little customizing if you have multiple gameXXX.exe files. Edit the Target field in a shortcut to have the proper gameXXX.exe name, or edit the path information if you put a game.exe in each mod folder. If you use the Mod Running Script, open the file in Notepad and edit the line [color=#d1ff00:030a3f30bc]D2CmdLine = chr(34) & D2Path & 'game.exe' & chr(34) & '-direct'[/color:030a3f30bc] and enter the desired file reference. [color=#ff8f6f:030a3f30bc]Please note:[/color:030a3f30bc] the Mod Running Script will launch the version referenced in the Windows Registry, so if you have two or more complete installations the script will only work on the one installation with Registry keys.

Now you should be able to run each mod, and still access Battle.net with a clean and current version of the game.

[size=18:030a3f30bc][align=center:030a3f30bc][color=cyan:030a3f30bc]Acknowledgements[/color:030a3f30bc][/align:030a3f30bc][/size:030a3f30bc]

Fusman - the Direct Switch tutorial

Bonescythe & FoxBat - the original VB script I adapted for the Mod Running Script

MickyBIs - multiple version method I constantly refer to

Members of the Phrozen Keep - for continuing feedback, methods I have learned over the years, and some great mods!

Blizzard Entertainment - for the game that keeps on playing

[size=18:030a3f30bc][align=center:030a3f30bc][color=cyan:030a3f30bc]Appendix - Registry Settings[/color:030a3f30bc][/align:030a3f30bc][/size:030a3f30bc]

Blizzard uses the Windows Registry for a number of settings related to game configuration, Battle.net, and where your save files end up. We will focus on two settings here, the Install Path and the Save Path. Different versions of Windows, and different computer setups, may store this information in either or both of two places, HKEY_CURRENT_USER or HKEY_LOCAL_MACHINE. There are several keys which may or may not be on your machine:

HKEY_CURRENT_USER\Software\Blizzard Entertainment\Diablo II]'InstallPath'='C:\Program Files\Diablo II'

[HKEY_CURRENT_USER\Software\Blizzard Entertainment\Diablo II]'Save Path'='C:\Program Files\Diablo II\Save\'

[HKEY_CURRENT_USER\Software\Blizzard Entertainment\Diablo II\Save Path]='C:\Program Files\Diablo II\Save'

[HKEY_LOCAL_MACHINE\SOFTWARE\Blizzard Entertainment\Diablo II]'InstallPath'='C:\Program Files\Diablo II'

[HKEY_LOCAL_MACHINE\SOFTWARE\Blizzard Entertainment\Diablo II]'Save Path'='C:\Program Files\Diablo II\Save\'

[HKEY_LOCAL_MACHINE\SOFTWARE\Blizzard Entertainment\Diablo II\Save Path]='C:\Program Files\Diablo II\Save'Link to this article: Select all

Hello, I understood that while the accounts are unlinked, each does have a separate character list, one belongs to the Xbox battle net account and the other to the PC battle net account. What I am trying to reach is the following - having the option to play the Xbox characters (different ones from the PC ones) on my PC if I am out of reach of my Xbox. Basically, using the Xbox battle net account to log into the PC version of the game and progressing my Xbox characters as I bought two versions of the game.

Is this achievable? Because right now I can only have ONE pool of characters even though I have bought two versions of the game, paid twice the full price, so I would expect to have a pool of characters for Xbox and a pool of characters for PC, depending on which Battle net I use for log in on which ever of those two platforms.

There are three different versions of the game on offer, with each offering increasingly more cosmetic items depending on how much money you spend. Which version best suits your needs will be up to you, so we've compared each of the three Diablo 4 editions below.

The Standard Edition is the base edition of Diablo 4. Purchasing this edition of Diablo 4 will get you the Caparison of Faith Mount Armor. Additionally, you will get some cosmetics for other Blizzard titles, including:

3a8082e126