0
Early on I would have called that paranoid but I've seen it several times now and I would just call it good sense.
Three things everyone should do.
- Make sure you are getting 1.13b drop odds. Thanks to the careless-ness of the devs, this isn't difficult. Orts, Rals, and Tals should be roughly 5 times more common, than Els and Elds. This should be very obvious very quick. I've only seen one test where it wasn't extremely clear within the first 5 runes and even then 2 more made it clear.
- If you have doubts, double check the shortcut. It should say "-direct -txt". I suspect an incorrect shortcut was responsible for all the issues I've seen and it definately was the one time I actually saw the shortcut text.
- If you still have doubts, remove all .bin files in the "DiabloII\runewordmod\data\global\excel" folder. (or sometimes just "DiabloII\data\global\excel" folder). This should leave you with just the runes.txt file in that folder. This will force D2 to recreate all those .bin files when you are running RWM.
Hi I have a little problem and I figured this be the place to post and ask for help..
I have multiple installs for different versions and its been working fine - I have lots of disk space so that's not really a problem. But after doing a session of some classic 1.06b I found something odd. When I was going back to the normal 1.13 version first the game loaded up as classic when using my RWM game.exe shortcut but when I used the loader.exe shortcut it loaded LOD. But for my chars to be possible to open I had to copy them to my 1.06b directory..
Well a lot of strange stuff happened and if you need more info I'll provide it, but to cut it short, the files seems to no longer be saved in the normal save folder since when I load them in GoMule they are as they were before I played classic and things got this messy. when doing a search of the computer for .d2s files I found files that had a last edit date from the last time I used the char I found files in '
"AppData\Local\VirtualStore\Program Files (x86)\Diablo\Diablo II 1.06b\save"
and in the "Roaming" catalogue
What shall I do? just load them from there and go at it in GoMule as usual or is there a way to get this back to normal?
Hmm ... so it appears a Ladder Reset / Patch is in the works. It's been so long that I wonder if I can still update ATMA for 1.13
--T
Tenshi,
First, thanks again (can never say it too many times) for ATMA, I'm sure like me, many people wouldn't have played D2 this long if it wasn't for your hard work, and thanks for updating it for 1.13.
If you do update it for 1.13, which I think won't be too hard to do, it would be nice to also update it for 1.13a and 1.13b (which are the two beta versions of 1.13 that were released on the test realm, in case you've been away so long that you weren't even aware of the beta patches).
The 1.13a and 1.13b text files, namely Runes.txt are different, so the drop calculator needs to use different text files for each version. If you need to get your hands on the 1.13a and 1.13b text files, let me know and I will be happy to PM you a link to them.
Runes.txt defines the runewords and whether they are enabled for single player. It is TreasureclassEX.txt that defines the drop chances such as the addition of essences and changed rune drop rates.
That's right, I meant TreasureClassEx. Runes.txt is just the definition of the runewords as you said.
Still none that can help me with my problem? Can't mule anything off of my characters and thats getting pretty annoying..
thanks in advance
BetaBlocker: what technique/switcher you use for your version swapping? I noticed you mentioned "loader.exe" - that might be a problem.
Bookmarks