(I know that this topic is very closely related to the stickied ATMA etc. help thread, but I felt like it would be a good idea to concentrate this information into one thread for easier reference.)
Note that the information in this post only applies to D2 1.07 LoD and ATMA V. (I don't know how ATMA behaves with D2 1.07 classic.)
ATMA V (5.05 being the latest version) works with D2 1.07 LoD, with a few important exceptions regarding runewords and "Hit Freezes Target" property. Here's a list of all of the more or less known major issues - the issues can be divided into 3 main categories:
1. RUNEWORDS:
1.1) In short, it is safest to not let ATMA touch any characters that have runeword items. Also do not try to move runeword items into an ATMA stash file. ATMA is known to corrupt character and stash files when working with runeword items.
1.2) The only safe way to mule runewords in 1.07 is to do it in an MP game with another character (e.g. self-muling via multiple instances).
1.3) Especially do not move any runeword items with ATMA, because this will likely corrupt the character/stash file(s) involved, rendering the character/stash file(s) useless.
1.4) It is possible that ATMA will corrupt a character even just by looking at a runeword item's stats by hovering the cursor onto the item. There is at least one known case where this happened with something as basic as Ancient's Pledge.
1.5) Some runewords might result in a corrupted file with ATMA more easily than others, Bramble being one of those(?).
1.6) It MIGHT be possible to open and save a character file with a runeword item on it, as long as you do not touch the runeword item with ATMA, as in don't move the item, and preferably don't even move the mouse cursor on the item. However, do this at your own risk and remember to keep backups. (Could someone please confirm/correct/elaborate this point?)
2. HIT FREEZES TARGET: (gladly this issue is quite clear cut)
2.1) In short, absolutely do not let ATMA touch any character that has an item with "Hit Freezes Target" property at all (don't even open/save such character in ATMA). Also do not try to move such item into an ATMA stash from a character, as it can/will corrupt the stash and/or character file.
2.2) For example the unique items Iceblink Splint Mail, Axe of Fechmar Large Axe and Bing Sz Wang Dacian Falx have this property, so do NOT touch any characters that have these items with ATMA. Preferably don't even pick up these items, unless you put them onto a separate mule character via an MP game, which you won't touch with ATMA.
3. POOFING ITEMS:
3.1) After moving an item into a character's inventory or stash in ATMA, there is a (small) chance that the item will disappear once the character is loaded in D2. It does not seem to happen often, but keep an eye on items that you have muled onto a character's inventory or stash, when you load the character in D2 (to confirm that they don't disappear). And remember to keep backups. - Does anyone know what triggers this?
3.2) It seems like the disappearance of an item is connected to moving an item from a character's equipment slot (e.g. helmet or shield) into a character's inventory or stash (regardless if it's on the same character or moving from one character to another).
3.3) It seems that one way to avoid the disappearance of items is to move an item into a character's equipment slot (e.g. helmet, armor, amulet, etc.) if possible, instead of putting the item into the character's inventory or stash. And if you remove an item from a character's equipment slot, it's probably safer to put the item into an ATMA stash instead of the character's inventory or stash.
Those should be all the known major issues ATMA has with 1.07, or at least all I have found information on so far. Apart from those major issues, I believe ATMA V (5.05 to be exact) works just fine for muling in 1.07 - but remember to keep backups of your files just in case.
That brings me to the point of this thread: It would be good to have a more or less up-to-date list of all the major issues that ATMA has with 1.07, so please post any possible corrections or additions to those issues. I can edit the list accordingly to keep it up-to-date. It would also be nice to get confirmation on the issues from people who know about and/or have experience on those issues.
Please note that by major issues I mean something that can result in a corrupted file or altered properties for example. Mere display errors do not count, even though they are annoying (e.g. if ATMA just shows the stats of an item incorrectly).
Most of the info comes from this thread: 1.07 News, Info and Gossip - it's an excellent source of information, but the thread is long, thus the info is spread out and requires some detective work in some cases to find the correct info.|||Maybe a cross reference of Prefix numbers to in-game prefix names?|||Quote:
Maybe a cross reference of Prefix numbers to in-game prefix names?
Do you mean a list that for example has the prefix numbers and in-game prefix names in their respective columns? If yes, such list could be useful, especially with Clvl requirements, but I don't know if it'd be worth the trouble because I think that ATMA shows the stats of charms for example otherwise correctly, except for the prefix names and Clvl requirements.
Besides, that's only a display error in ATMA, so it's a bit out of the scope of this thread. I intended this thread as a reference for the major issues that ATMA V has with 1.07, and by major I mean anything that could corrupt or alter any items/characters/stashes, or cause ATMA to crash.|||I've never found one, but I assume that the 1.07 Bing Sz Wang unique Dacian Falx would also have the 'hit freezes target' mod and would cause the same issue as Iceblink or AoF.
I had always assumed that the runeword Ancient's Pledge would be OK, as it exists in all LoD patches, but it DID corrupt a character, and all I did was mouseover it in ATMA!
I know that Galtwish did play extensively with a Death runeword bow while using ATMA, so it IS possible...not sure if he ever lost a character that way, but you'd want to backup A LOT if you did it.
While the prefix thing in ATMA is just a display issue, I find it VERY annoying...but not on blues, I'm pretty good at matching up level reqs when I can SEE the prefixes. Its on rares and especially crafted items that it becomes annoying as hell...ATMA gets the rlvl on these right only by mistake, and is usually completely wrong. You have to mule items on and check their rlvls in-game, which gets to be a real drag.
What makes all this especially irritating is that Mattinm has done the coding to make GoMule compatible with 1.07 (1.09, 1.10a, and 1.10s, too), but Silospen has apparently dropped off the face of the earth...without his blessing, Mattinm's work is NOT FAM, and cannot be used by SPFers
WoRG|||Updated the opening post a bit. Added Bing Sz Wang into the list of items with Hit Freezes Target property. Thanks WoRG.
Quote:
What makes all this especially irritating is that Mattinm has done the coding to make GoMule compatible with 1.07 (1.09, 1.10a, and 1.10s, too), but Silospen has apparently dropped off the face of the earth...without his blessing, Mattinm's work is NOT FAM, and cannot be used by SPFers
WoRG
Really? That's interesting, and really a pity. I had also noticed that Silospen just seemed to suddenly disappear from the forum.
Do you know that did Mattinm get it to work also with all the 1.07 runewords and the Hit Freezes Target (HFT) items?
It would be excellent to have a working muling application for 1.07 which with you don't have to be afraid of runewords and HFT items like a plague. Not to mention that GoMule is in many ways so much more handy than ATMA (no offense to the old pioneer of muling programs). And how handy it would be to have control of all the D2 muling needs under one program...
SIIIIIIIIIIIILOOOOOOOOOOOOOOOOOOOO! VEEEEER AAAAAAAAR JUUUUUUUUUUUUUU????!?!?!?
Silo's needed. (Lame Command and Conquer reference.)
If silo doesn't appear, why couldn't someone else with the necessary skills (Mattinm?) do the changes to GoMule? Is it because GoMule is mostly silo's work so that he would have to check it in order for the changes to be considered trust-worthy on SPF? Perhaps a second person (other than silo) also with the necessary skills could confirm Mattinm's work on GoMule?|||As per Silo/Mattinm, I know they were having a conversation.
GoMule (Silo's) has been OK'd by the Admins. It's going to be a lot easier to get Mattinm's stuff OK'd if it's basically a continuation of Silo's work - and with his OK.
As always, we want to avoid any and every alteration done by any forum member being accepted as FAM and useable in our MP/trade pool. I'm sure most people who are able/want to code are playing by our rules but if it turns into a free-for-all, I guarantee someone won't be.|||Please excuse me for this shameless bump...
But so is that list comprehensive enough? And does it cover all the major issues that ATMA has with 1.07? I'd like to see a post from at least one or two more people with extensive 1.07 LoD + ATMA experience.
And if the list seems alright, wouldn't it be a good idea to have it under the 1.07 section of the SPF FAQ & rules sticky, and perhaps also in the ATMA/GoMule help sticky? Those issues are not covered in the 1.07 guides (or I must be blind), so it seems to me like a good idea to have a clear list of those major issues linked there for reference.|||Dunno if I should use ATMA Help Thread instead of this one but here it goes
I noticed that ATMA eats some items. Using ATMA V I moved my P Sapphire'd Valk from Helm Slot to sorc's stash, as soon as I load sorc in D2 the Valk doesn't show and disappears. This doesn't happen when moving the said helm to both Sorc or Merc's helm slot. Just to stash or inventory.
Dunno if this has happened with other items, I just panicked when Valk was gone. I wouldn't notice lower items being gone. Maybe it's the fact that's socketed...?|||@ nulio: That's interesting, because I noticed similar behavior with a socketed shield (post from the ATMA/GoMule help thread (no one had commented on it)):
Quote:
I bumped into a problem I had not seen or read about with ATMA and D2 1.07 LoD.
I tried to mule a Chromatic Kite Shield from a sorceress' primary weapon switch's right side (above boots) onto an amazon's inventory, but then after loading the amazon in D2 the shield had just vanished. It's not found anywhere on the character. I confirmed this with ATMA too; D2 had just made the shield poof. Gladly I keep frequent backups, so I was able to roll back the saves. I tested it multiple times, varying the spot where I muled the shield to. I also tried muling other items at the same time, and the other items were successfully transferred, only the shield poofed.
Finally I tried muling the shield into the amazon's weapon slot, then the shield did not disappear when loading in D2. Curiously enough, after that I was able to mule the shield back and forth without any trouble, so the problem was somehow fixed. I confirmed that that behavior was repeatable too, by rolling back the saves and testing again.
The shield in question is:
Prefix 1002 Kite Shield
Defense: 17
Chance to Block: 33%
Durability: 30 of 30
Required Strength: 47
Required Level: 18
Item Version: Expansion
Item Level: 64
Fingerprint: 0x7d18d81b
All Resistances +86
Socketed (3: 3 used)
The prefix is Chromatic, with no suffix. It got 3 sockets from Larzuk, and is socketed with 3 Perfect Diamonds.
The problem didn't seem to cause any corrupted files or any other problems, but I thought such more severe problems didn't occur with other things than runewords and "Hit Freezes Target" property, although this problem was different as it just made the shield poof in game, nothing else. Has anyone else seen similar behavior with ATMA and 1.07 LoD?
Assuming that you had backups so you didn't lose the Valk Wing for good, I'm glad to see that issue occurred somewhere else too, to confirm that it seems to be a bug in ATMA. It indeed might have something to do with the item being socketed, and in both cases the items were socketed with gem(s).
I think that normally this kind of issues would belong to the ATMA/GoMule help thread, but most of the discussion there is about the current version of D2, and 1.07 players are a minority, and well the point of this thread is to gather all such major issues that ATMA has with 1.07, so I hope it's alright to talk about those issues in this thread.
As I mentioned, 1.07 players are a minority. There aren't many people playing 1.07, and not many people with extensive experience on 1.07, so I think posts on this topic could easily go unseen by the "1.07 people" in the sticky help thread.
Besides, ATMA doesn't have such major issues (corrupted chars/stashes, lost items) with the latest versions of D2 as far as I know, except for the tokens and essences, so I feel like this topic deserves its own thread. I hope the moderator (Thyiad) and others agree on that.|||Quote:
Dunno if I should use ATMA Help Thread instead of this one but here it goes
I noticed that ATMA eats some items. Using ATMA V I moved my P Sapphire'd Valk from Helm Slot to sorc's stash, as soon as I load sorc in D2 the Valk doesn't show and disappears. This doesn't happen when moving the said helm to both Sorc or Merc's helm slot. Just to stash or inventory.
Dunno if this has happened with other items, I just panicked when Valk was gone. I wouldn't notice lower items being gone. Maybe it's the fact that's socketed...?
I have had this happen in 1.07 with a rare amulet, where I had to equip it on my assassin to actually transfer it. Like nulio, it has probably happened many more times than the few I have noticed it.
No comments:
Post a Comment