I inserted Tal and Eth runes (in that order) in Field Plate (2 socket) and I don’t have Stealth armor (only TalEth). What did I do wrong or is that a bug?
Is your armor magic? (ie: Mechanic’s Field Plate) or rare instead of white/grey?
3 Likes
Aye, it was Mechanic Field Plate (blue)… thx, didn’t know it has to be white/grey
Same thing happened to me. I put Tal and Eth into a 2-socketed ScaleMail and it did not create the runeword.
BTW, the magic word “Mechanic” is just what the item says after adding the runes. It was not magic before putting them in.
If you put runes in a grey item that don’t make a RW then the name stays grey text but changes to "gemmed " .
Name becomes gold like a unique after successful RW creation.
It never would add “mechanics” to the name, so if it has that it was already a blue text magic item. It may have had no suffix and therefore no other magic affixed making it look like it was not magical, but would still have blue text and be magic and therefore unsuitable for RW creation.
If you’re able to post a pic or might help but it really sounds like you used an incorrect base.
You think it is coincidence that three people attempted to create a “Stealth” armor and ended up with a “Mechanic” magical armor with no magical properties, and you think it is our fault?
Not trying to be insulting or condescending, but most runeword issues do end up being a mistake by the user. Note that the thread starter did come back and say he didn’t realize that it had to be a grey item, so he admitted that in his case he made a mistake. This is how must of the runeword threads I’ve seen end up.
I made stealth in a 2 socket splint mail with no issues so it’s definitely possible.
There’s a chance you got some Resurrected specific bug that just has a very low chance to somehow change an item to magic instead of making the correct runeword, but I do think that’s very unlikely, sorry and no offense meant.
It’s also really common to make small mistakes that end up with failed runewords. Failed runewords also just go to a gemmed item name, mechanics can only occur on a magic item.
1 Like
happened to me… no mechanics affix… just gemmed… it was a white grey breast plate… … tal in top … eth on bottom… no stealth
Edit : I did not know you needed exact # of sockets… my bad. (had 3 instead of 2)
1 Like
Yes, it needs to be exact # of sockets. Sorry to hear you wasted runes! Note though that it became “gemmed” and not “mechanics”. It sounds like what Kwaske is saying is that he had a grey armor with 2 sockets, then inserted Tal + Eth, then it became a “blue name” “Mechanics” armor.
I saw this 2 socket shield at Ashera the other night:
https://imgur.com/4nhwFf1
Note that it has a blue name, “Mechanics” and 2 OS. If I inserted runes, the RW would fail, and it would still be named “Mechanics”. It would be easy to see this, see that it has no “magic mods” and assume it’s a good RW base, but it’s a magic item with the prefix mechanics that gave it sockets, so it is not eligible for RW. I’m not saying there’s no chance of a bug, but it just seems like this is the most likely option for failed RW that show “Mechanics”.
Can some of you with the issue post a screenshot of how the item looks?
1 Like
Please post screenshots before I facepalm a second time.
Same here, grey item, 2 sockets, put them in correct order.
imgur dot com/OSwQoqM
Because i can’t put link in my post 
Sorry but that’s not a gray item, it’s a blue, magical item. Mechanic’s affix provides sockets but runewords will never work in those.
I see. I have to be more careful next time.
Hi all,
In my case all is correct, Grey armor, 2 sockets, I put it in the correct order but not chance to get the benefits of the runeword.
In fact, I bought the armor in actIV normal level with my sorc and then I shared with my paladin, so honestly i don´t know where is the fault here
it either was not a body armor, it was not gray before you put the runes in, or you didn’t put them in in the order of tal eth