Diablo II Auto Teleport: Download or Mirror Download - Optimized teleport plugin that can be used together with maphack or separately to move in between waypoints. Looking for an older version? Download Teleport 1.2 or Teleport 1.2a - Auto Teleport 1.2a fixes chat bug for those who have it in newer versions.
What I'm trying to describe here is how to have two copies of Diablo 2 running on the same computer without the use of any third party programs. This means that this guide will not provide any information on hacked dll files, or loader programs of any sorts.To my knowledge, the only way to accomplish this is with the Window's XP feature called 'Fast User Switching'. Note that as far as I know, Fast User Switching is not available on computers who are part of a network domain, so if you're playing D2 at work or something, then you won't be able to do this (besides, you should be working anyway ).We'll get into Fast User Switching soon, but first I'd also like to mention that it's important you have two sets of valid CD-Keys if you wish to do this. When you log onto battle.net, it'll authenticate both the D2 Classic CD-Key and D2 Expansion CD-Key, even if you're playing Diablo II: Lords of Destruction. The only way to have two copies of Diablo 2 logged onto the same battle.net realm at the same time is if both copies have a unique D2 Classic CD-Key and D2 Expansion CD-Key (totaling 4 CD-Keys).
If you do not have the Diablo 2 expansion, then battle.net will only authenticate your Diablo 2 Classic CD-Key, of course.Fast User Switching First, verify that you have Fast User Switching enabled on your Windows XP machine.
The need for official 1.13c thread that explains everythingEDIT: Read Thyiad's post below (#18) for answers.Let me start by saying(1) I have not upgraded to 1.13a or 1.13b or 1.13c yet. I decided to wait for the final official release. Which happened yesterday, I believe.(2) I would like to upgrade to the final version, i.e. 1.13c(3) Because of (1), I have not followed any of the '1.13 and blah-blah' threads.I believe I'm not the only one who decided to wait for the final version before upgrading, so I think a general explanation thread with basic info about 1.13c is needed. There is no such info here yet:Basically I would be grateful if someone wrote a post like this one:about 1.13c.If it helps, I would like to know the following:(1) I have 1.12 with RRM, RWM and modified.dll. Can I download update from here:and install it right away?If not, do I have to uninstall everything, or just the.dll, or the.dll and RWM?(2) With 1.13c, RRM becomes obsolete.
How do I uninstall it?(3) Is there a modified.dll for 1.13c? If so, where is it? I did not find it here:(4) Will RWM from 1.12 work in 1.13c, or do I need a 'new' RWM? If so, how do I uninstall the old RWM, and how do I install the new RWM? Also, where do I find the 'new' RWM?(5) How are things different on Mac?I hope that this thread is not considered redundant.
Thanks for the answers to all good Samaritans out there!-Greebo. Re: The need for official 1.13c thread that explains everything1) If you download the patch and install it manually it shouldn't be a problem which extensions/mods you are running.Although if you are worried then you can reinstall and patch then redo your mods, but if you're doing the install manually I can't see how it would be a problem.
I myself updated off battle.net and didn't bother to take off the modified d2gfx.dll, I just made sure I was quick and haven't had a problem (not that I'd play on battle.net anyway)2) Just delete the runewords/redrunemod folder from your D2 directory and then download it again and reinstall it.3) The modified.dll still works for 1.13c so shouldn't be a problem.4) Runeword mod works fine in 1.13c you just need to install it as per 1.12a, same installation instructions etc.5) I don't believe there are any updates that have been to mac, per se. That said, I don't play on a mac so haven't taken much notice.Joosh:thumbup. Re: The need for official 1.13c thread that explains everything1. Yes, you can download and install.
You will probably have to reinstall a.dll (for 1.13) though but since I've never tried that I'm not 100% sure.2. Remove the folder from Diablo 2 directory and make sure that you're starting the game from the right directory (RWM) with your shortcut.3. I think there is one for 1.13a/b but I'm not sure if they work for 1.13c. Since there's so little change I don't see why it shouldn't though.4.
Yes, it works. But there was a fix of the runeword Principle so if you want that one correct you'll have to get the new RWM.5. I'm on PC so I can't answer that.EDIT: Damn you Joosh. 2 mins quicker than me.EDIT2: What? Nothing to see here! (1) I have 1.12 with RRM, RWM and modified.dll.
Can I download update from here:and install it right away?No. You need to replace the modified.dll with the original one. For the RRM and RWM, it is sufficient to temporarily remove the /Runewords folder from your Diablo II folder (not even sure if this is needed at all). Also, when you're going to patch, use Diablo II.exe, NOT your shortcut.(2) With 1.13c, RRM becomes obsolete. How do I uninstall it?I believe you just have to remove 'expansionstring.tbl' and 'patchstring.tbl' from your Diablo II/Runewords/data/local/lng/eng/ folder.(3) Is there a modified.dll for 1.13c? If so, where is it? I did not find it here:If there is one, you'll probably find it at the Frozen Keep.(4) Will RWM from 1.12 work in 1.13c, or do I need a 'new' RWM?
If so, how do I uninstall the old RWM, and how do I install the new RWM? Also, where do I find the 'new' RWM?The old one will work just fine. Just be sure to place back the /Runewords folder in your Diablo II folder.
Re: The need for official 1.13c thread that explains everythingThanks for the replies, but there seems to be some inconsistencies. For reference to have it in one place, I edited in the answers I got into my first post. So far it seems that:(1) According to some, I can install the downloaded update right onto modded version. According to others, I need to remove the mods.(2) The modified.dll does not work in 1.13c (but it did work in 1.13b).(3) There was a fix in runeword 'Pride', which requires reinstalling RWM.
I'm not clear whether one needs to download a newer version of RWM, or just reinstall one that can be found here. Thanks for the replies, but there seems to be some inconsistencies. For reference to have it in one place, I edited in the answers I got into my first post.
So far it seems that:(1) According to some, I can install the downloaded update right onto modded version. According to others, I need to remove the mods.(2) The modified.dll does not work in 1.13c (but it did work in 1.13b).(3) There was a fix in runeword 'Pride', which requires reinstalling RWM. I'm not clear whether one needs to download a newer version of RWM, or just reinstall one that can be found here. First: Same as you, I did wait for the final release.(1) no, you can't. At least not if you have a modded D2gfx.dll file. You need to replace that one with the original file or the patch installation will abort midthrough (I tested this on Win7).
Once you replace the modded file with the original file, installation is no problem. I used a Vanilla shortcut though, not the RRM/RWM shortcut. But I defnitely had RRM/RWM in my D2 folder.
Don't know if it would have worked if I had used the RRM/RWM shortcut.(2) no idea(3) DarkChaos posted an updated RWM somewhere in the 1.13 thread. Since RWM doesn't need to be installed (it's simple files placed in the 'data' subfolder of your D2 folder), you could simply copy the new Runes.txt file to your data folder (i.e. Diablo2dataglobalexcel ) and overwrite the old Runes.txt.NOTE: I don't know if said file has been accepted by the mods yet!To 'uninstall' RRM without having to 'install' RWM again, simply go to the data folder of your Diablo 2 folder and delete the folder called 'local'. Re: The need for official 1.13c thread that explains everything1.) Apart from the modified D2gfx.dll (you need the original unmodified one), in short, yes you can update to 1.13c even if you have RWM and RRM installed, as long as you run the game correctly, after installing the update, with both the -direct and -txt commands like this:'C:Example FolderDiablo IIDiablo II.exe' -direct -txtThe old RWM and RRM should work after you patch the game to 1.13c.
But I would say it's better to delete the old RRM, and use RWM only. That is because the old RRM would cause display error with the names of the new items. I believe the 5 new items, 4 'Essences' and the 'Token' that can be cubed from the essences, would be shown as 'An Evil Force' if you run the game with the old 1.12a RRM.
Re: The need for official 1.13c thread that explains everythingAs I said (with different phrasing) in my previous message, that is an issue only if the '-txt' command is left out of the shortcut or it's typed incorrectly.When the commands (-direct -txt) are in the shortcut as they should be, the.bin files get re-created each time D2 is run. At least that is my understanding, someone please correct me if I'm wrong (jjscud?).But also, as I said in the previous message, I'm rather paranoid with that, so that's why I just delete the whole RWM/RRM folder and re-install RWM.Edit: Owned by jjscud, also, thanks for confirming that (in advance: P). And seems like you have similar opinion about that matter: -direct -txt should re-create the.bin files, but just to be foolproof, safest is to delete the old files first.Edit2: @ Pyrohemia: Yeah I thought D2 is most likely case insensitive with that, but I wanted to be exact (what the filename originally is), and I was at work computer so I didn't have a fast way of checking that then.
Now at home I checked it, it's Runes.txt, though that info is trivial at best. Re: The need for official 1.13c thread that explains everythingDid some more digging, and read all the replies above. It seems that:(1) To install the patch manually downloaded from Blizzard servers, one needs to revert to the unmodded d2gfx.dll.However, removing the Runewords folder is a good idea, since- RRM became obsolete- RWM has new versions(2) There are 5 new items that ATMA cannot display yet (they deal with re-doing your character mid-game), but there is a temporary fix,.(3) There is no modified d2gfx.dll for 1.13c yet.
Both 1.13a and 1.13b had a new modified d2gfx.dll released for them, both different than each other and different than the d2gfx.dll for 1.12.(4) There is new RWM for 1.13, but only for PC. Thyiad seems to have put it here (the Runesfor1.13b file):(5) that installing the RWM for 1.13b once you install 1.13c will revert you to 1.13b.
That's on Mac.If that's correct I'll put this info into the first post. Re: The need for official 1.13c thread that explains everythingUpdating preparationIF YOU CONNECT TO THE REALM TO UPDATE ENSURE YOU USE AN UNMODDED VERSIONRemove RWM/RRM - by deleting Runewords and RedRuneMod directories (move your screenshots first!)Replace the multi instance modified dll with the originalUse a shortcut without -direct -txt.Mac users need to replace the original carbon.It may well be quickest to move your save directory out of D2 directory and reinstall.
Be aware that D2's uninstaller does not necessarily delete the directory and you may need to do that manually.Updating OptionsFrom Blizzard's website via logging onto the realms orManually by downloading the patchIf you get an error when updating via Bnet log in, try doing a reinstall.A manual update doesn't require you to uninstall the modified.dll. You should use a vanilla shortcut because otherwise you won't get the 1.13c runedrops.Reinstalling modsRWM and RRM will still work in 1.13c.
However RRM isn't really needed because the runes are now orange anyway.RWM has the same install as before but use the Runesfor1.13b.txt. (Thanks to DarkChaos)Mac RWM is.I do not have a multi instance.dll for 1.13c.MulingTwo alterations to ATMA are required or the new Essances will crash it. They can be found.and on. Information from Rhone: the Sourceforge GoMule copes with Essenences, but the one on Silo's site doesn't.
As I am not using 1.13 (of any kind) I am unable to test that.Item compatibilityThere is no change in regards item movement. Items may move forwards (1.12a 1.13beta1 1.13beta2 1.13c) but not backwards.
Re: The need for official 1.13c thread that explains everythingFor RWM, you don't have to actually remove the Runewords directory to upgrade-just temporarily changing the shortcut to run from the D2 directory instead of the Runewords directory (and taking out the -direct -txt) is enough.GoMule works fine with the essences-Silospen updated it soon after 1.13a was released. Pinnacle video transfer. It appears that Silospen's page that's linked to in Thyiad's post links to an older version of GoMule, though. The current version of GoMule can be found at its.
- Author: admin
- Category: Category
Diablo II Auto Teleport: Download or Mirror Download - Optimized teleport plugin that can be used together with maphack or separately to move in between waypoints. Looking for an older version? Download Teleport 1.2 or Teleport 1.2a - Auto Teleport 1.2a fixes chat bug for those who have it in newer versions.
What I'm trying to describe here is how to have two copies of Diablo 2 running on the same computer without the use of any third party programs. This means that this guide will not provide any information on hacked dll files, or loader programs of any sorts.To my knowledge, the only way to accomplish this is with the Window's XP feature called 'Fast User Switching'. Note that as far as I know, Fast User Switching is not available on computers who are part of a network domain, so if you're playing D2 at work or something, then you won't be able to do this (besides, you should be working anyway ).We'll get into Fast User Switching soon, but first I'd also like to mention that it's important you have two sets of valid CD-Keys if you wish to do this. When you log onto battle.net, it'll authenticate both the D2 Classic CD-Key and D2 Expansion CD-Key, even if you're playing Diablo II: Lords of Destruction. The only way to have two copies of Diablo 2 logged onto the same battle.net realm at the same time is if both copies have a unique D2 Classic CD-Key and D2 Expansion CD-Key (totaling 4 CD-Keys).
If you do not have the Diablo 2 expansion, then battle.net will only authenticate your Diablo 2 Classic CD-Key, of course.Fast User Switching First, verify that you have Fast User Switching enabled on your Windows XP machine.
The need for official 1.13c thread that explains everythingEDIT: Read Thyiad's post below (#18) for answers.Let me start by saying(1) I have not upgraded to 1.13a or 1.13b or 1.13c yet. I decided to wait for the final official release. Which happened yesterday, I believe.(2) I would like to upgrade to the final version, i.e. 1.13c(3) Because of (1), I have not followed any of the '1.13 and blah-blah' threads.I believe I'm not the only one who decided to wait for the final version before upgrading, so I think a general explanation thread with basic info about 1.13c is needed. There is no such info here yet:Basically I would be grateful if someone wrote a post like this one:about 1.13c.If it helps, I would like to know the following:(1) I have 1.12 with RRM, RWM and modified.dll. Can I download update from here:and install it right away?If not, do I have to uninstall everything, or just the.dll, or the.dll and RWM?(2) With 1.13c, RRM becomes obsolete.
How do I uninstall it?(3) Is there a modified.dll for 1.13c? If so, where is it? I did not find it here:(4) Will RWM from 1.12 work in 1.13c, or do I need a 'new' RWM? If so, how do I uninstall the old RWM, and how do I install the new RWM? Also, where do I find the 'new' RWM?(5) How are things different on Mac?I hope that this thread is not considered redundant.
Thanks for the answers to all good Samaritans out there!-Greebo. Re: The need for official 1.13c thread that explains everything1) If you download the patch and install it manually it shouldn't be a problem which extensions/mods you are running.Although if you are worried then you can reinstall and patch then redo your mods, but if you're doing the install manually I can't see how it would be a problem.
I myself updated off battle.net and didn't bother to take off the modified d2gfx.dll, I just made sure I was quick and haven't had a problem (not that I'd play on battle.net anyway)2) Just delete the runewords/redrunemod folder from your D2 directory and then download it again and reinstall it.3) The modified.dll still works for 1.13c so shouldn't be a problem.4) Runeword mod works fine in 1.13c you just need to install it as per 1.12a, same installation instructions etc.5) I don't believe there are any updates that have been to mac, per se. That said, I don't play on a mac so haven't taken much notice.Joosh:thumbup. Re: The need for official 1.13c thread that explains everything1. Yes, you can download and install.
You will probably have to reinstall a.dll (for 1.13) though but since I've never tried that I'm not 100% sure.2. Remove the folder from Diablo 2 directory and make sure that you're starting the game from the right directory (RWM) with your shortcut.3. I think there is one for 1.13a/b but I'm not sure if they work for 1.13c. Since there's so little change I don't see why it shouldn't though.4.
Yes, it works. But there was a fix of the runeword Principle so if you want that one correct you'll have to get the new RWM.5. I'm on PC so I can't answer that.EDIT: Damn you Joosh. 2 mins quicker than me.EDIT2: What? Nothing to see here! (1) I have 1.12 with RRM, RWM and modified.dll.
Can I download update from here:and install it right away?No. You need to replace the modified.dll with the original one. For the RRM and RWM, it is sufficient to temporarily remove the /Runewords folder from your Diablo II folder (not even sure if this is needed at all). Also, when you're going to patch, use Diablo II.exe, NOT your shortcut.(2) With 1.13c, RRM becomes obsolete. How do I uninstall it?I believe you just have to remove 'expansionstring.tbl' and 'patchstring.tbl' from your Diablo II/Runewords/data/local/lng/eng/ folder.(3) Is there a modified.dll for 1.13c? If so, where is it? I did not find it here:If there is one, you'll probably find it at the Frozen Keep.(4) Will RWM from 1.12 work in 1.13c, or do I need a 'new' RWM?
If so, how do I uninstall the old RWM, and how do I install the new RWM? Also, where do I find the 'new' RWM?The old one will work just fine. Just be sure to place back the /Runewords folder in your Diablo II folder.
Re: The need for official 1.13c thread that explains everythingThanks for the replies, but there seems to be some inconsistencies. For reference to have it in one place, I edited in the answers I got into my first post. So far it seems that:(1) According to some, I can install the downloaded update right onto modded version. According to others, I need to remove the mods.(2) The modified.dll does not work in 1.13c (but it did work in 1.13b).(3) There was a fix in runeword 'Pride', which requires reinstalling RWM.
I'm not clear whether one needs to download a newer version of RWM, or just reinstall one that can be found here. Thanks for the replies, but there seems to be some inconsistencies. For reference to have it in one place, I edited in the answers I got into my first post.
So far it seems that:(1) According to some, I can install the downloaded update right onto modded version. According to others, I need to remove the mods.(2) The modified.dll does not work in 1.13c (but it did work in 1.13b).(3) There was a fix in runeword 'Pride', which requires reinstalling RWM. I'm not clear whether one needs to download a newer version of RWM, or just reinstall one that can be found here. First: Same as you, I did wait for the final release.(1) no, you can't. At least not if you have a modded D2gfx.dll file. You need to replace that one with the original file or the patch installation will abort midthrough (I tested this on Win7).
Once you replace the modded file with the original file, installation is no problem. I used a Vanilla shortcut though, not the RRM/RWM shortcut. But I defnitely had RRM/RWM in my D2 folder.
Don't know if it would have worked if I had used the RRM/RWM shortcut.(2) no idea(3) DarkChaos posted an updated RWM somewhere in the 1.13 thread. Since RWM doesn't need to be installed (it's simple files placed in the 'data' subfolder of your D2 folder), you could simply copy the new Runes.txt file to your data folder (i.e. Diablo2dataglobalexcel ) and overwrite the old Runes.txt.NOTE: I don't know if said file has been accepted by the mods yet!To 'uninstall' RRM without having to 'install' RWM again, simply go to the data folder of your Diablo 2 folder and delete the folder called 'local'. Re: The need for official 1.13c thread that explains everything1.) Apart from the modified D2gfx.dll (you need the original unmodified one), in short, yes you can update to 1.13c even if you have RWM and RRM installed, as long as you run the game correctly, after installing the update, with both the -direct and -txt commands like this:'C:Example FolderDiablo IIDiablo II.exe' -direct -txtThe old RWM and RRM should work after you patch the game to 1.13c.
But I would say it's better to delete the old RRM, and use RWM only. That is because the old RRM would cause display error with the names of the new items. I believe the 5 new items, 4 'Essences' and the 'Token' that can be cubed from the essences, would be shown as 'An Evil Force' if you run the game with the old 1.12a RRM.
Re: The need for official 1.13c thread that explains everythingAs I said (with different phrasing) in my previous message, that is an issue only if the '-txt' command is left out of the shortcut or it's typed incorrectly.When the commands (-direct -txt) are in the shortcut as they should be, the.bin files get re-created each time D2 is run. At least that is my understanding, someone please correct me if I'm wrong (jjscud?).But also, as I said in the previous message, I'm rather paranoid with that, so that's why I just delete the whole RWM/RRM folder and re-install RWM.Edit: Owned by jjscud, also, thanks for confirming that (in advance: P). And seems like you have similar opinion about that matter: -direct -txt should re-create the.bin files, but just to be foolproof, safest is to delete the old files first.Edit2: @ Pyrohemia: Yeah I thought D2 is most likely case insensitive with that, but I wanted to be exact (what the filename originally is), and I was at work computer so I didn't have a fast way of checking that then.
Now at home I checked it, it's Runes.txt, though that info is trivial at best. Re: The need for official 1.13c thread that explains everythingDid some more digging, and read all the replies above. It seems that:(1) To install the patch manually downloaded from Blizzard servers, one needs to revert to the unmodded d2gfx.dll.However, removing the Runewords folder is a good idea, since- RRM became obsolete- RWM has new versions(2) There are 5 new items that ATMA cannot display yet (they deal with re-doing your character mid-game), but there is a temporary fix,.(3) There is no modified d2gfx.dll for 1.13c yet.
Both 1.13a and 1.13b had a new modified d2gfx.dll released for them, both different than each other and different than the d2gfx.dll for 1.12.(4) There is new RWM for 1.13, but only for PC. Thyiad seems to have put it here (the Runesfor1.13b file):(5) that installing the RWM for 1.13b once you install 1.13c will revert you to 1.13b.
That's on Mac.If that's correct I'll put this info into the first post. Re: The need for official 1.13c thread that explains everythingUpdating preparationIF YOU CONNECT TO THE REALM TO UPDATE ENSURE YOU USE AN UNMODDED VERSIONRemove RWM/RRM - by deleting Runewords and RedRuneMod directories (move your screenshots first!)Replace the multi instance modified dll with the originalUse a shortcut without -direct -txt.Mac users need to replace the original carbon.It may well be quickest to move your save directory out of D2 directory and reinstall.
Be aware that D2's uninstaller does not necessarily delete the directory and you may need to do that manually.Updating OptionsFrom Blizzard's website via logging onto the realms orManually by downloading the patchIf you get an error when updating via Bnet log in, try doing a reinstall.A manual update doesn't require you to uninstall the modified.dll. You should use a vanilla shortcut because otherwise you won't get the 1.13c runedrops.Reinstalling modsRWM and RRM will still work in 1.13c.
However RRM isn't really needed because the runes are now orange anyway.RWM has the same install as before but use the Runesfor1.13b.txt. (Thanks to DarkChaos)Mac RWM is.I do not have a multi instance.dll for 1.13c.MulingTwo alterations to ATMA are required or the new Essances will crash it. They can be found.and on. Information from Rhone: the Sourceforge GoMule copes with Essenences, but the one on Silo's site doesn't.
As I am not using 1.13 (of any kind) I am unable to test that.Item compatibilityThere is no change in regards item movement. Items may move forwards (1.12a 1.13beta1 1.13beta2 1.13c) but not backwards.
Re: The need for official 1.13c thread that explains everythingFor RWM, you don't have to actually remove the Runewords directory to upgrade-just temporarily changing the shortcut to run from the D2 directory instead of the Runewords directory (and taking out the -direct -txt) is enough.GoMule works fine with the essences-Silospen updated it soon after 1.13a was released. Pinnacle video transfer. It appears that Silospen's page that's linked to in Thyiad's post links to an older version of GoMule, though. The current version of GoMule can be found at its.