I just used the new wardrobe system for the first time and the results were devestating. I had equiped a pair of crafted ascended wupwup pauldrons and wanted to skin them with the council guard pauldrons. The visual appearence successfully changed and the superior rune of the traveler was maintained, however, the item stats were completely re-written by the exotic stats of the skin……so……I’m pretty sure this is not supposed to happen? Crafting an ascended item is no small task and I am pretty disappointed by this….some resolution to this bug would be greatly appreciated.
I don’t see how that could happen with transmutation charges. The only thing that changes is an item’s appearance. Did you check to make sure you didn’t somehow confuse the exotic set of pauldrons with the ascended set and wound up equipping the exotic set? Maybe posting a screenshot could help us see what happened.
No, I am sure because the item created still has the same superior rune that was on the ascended item. And I don’t see how a screenshot can help, it does not prove anything except that I have a pair of exotic pauldrons….Plus, the ascended pauldrons are nowhere to be found in my inventory, they are gone, destroyed by the transmutation. Really upset about this.
The current transmutation system doesn’t destroy anything, though. It only works by placing a skin on an item you currently have equipped. There’s no way to destroy the item you have equipped by transmuting alone. I just transmuted a boot skin onto my current boots to demonstrate. No runes transfer, and no item gets destroyed doing it that way. So, I’m not sure exactly what you did. :\
I’d suggest relogging and then searching your inventory for the ascended pauldrons. Then check your bank. If the item still doesn’t appear, then you should contact support directly to see if they could figure out what went wrong.
Yes, I completely understand how the system is SUPPOSED to work, hence why I have made this post in the “BUGS” section. Perhaps it has something to do with the fact that they were crafted long ago and had already been transmuted in the old system before the wardrobe was introduced? Whatever the case, my ascended item has been converted into an exotic item and this is unnaceptable.
I don’t think that (them being old items) would be the issue. I know I transmuted new skins onto items that had been previously transmuted in the old system, and I don’t recall something like this happening. Like I said, contact support directly. Not only could they look and see what happened, but they might even be able to refund you the lost ascended item.
Skins don’t have stats, so there’s nothing for them to overwrite. They also don’t have a rarity. You can have a common- (white-)rarity weapon using an antique (i.e. ascended) skin and an ascended-rarity weapon with a common skin. In both cases, the item will state the rarity, so a screenshot of the existing item would help.
Regardless, the best response you can get on the forums is “hmmn, that might be a bug if it happened the way you describe” — we would actually be able to help you resolve the issue. For that, you need to create a support ticket, as Rose suggested.
Be sure to provide them with a screenshot of the item, the estimated time you did the transmutation, and the name of the character you were on.
John Smith: “you should kill monsters, because killing monsters is awesome.”
I am pretty sure i know the i know the issue, When you transmute an item, the actual name of the item changes to match what it was transmuted to. So say you transmute a Volcanus skin over an ascended weapon, the weapon will now be labeled as Volcanus, however if you look under where the sigil/runes are located, it will say
Transmuted:
(Name of original item)
I am not sure if it causes the actual rarity color of the item to change or not, but the stats should still be that of ascended or whatever it was before.
non of the above. The ascended wupwup stats and rarity were completely overwritten. This is what the item was converted to:
The screenshot says the original item was Knight’s Heavy Plate Pauldrons. That seems to indicate that you transmuted an exotic skin onto an exotic piece of armor, not onto an ascended piece of armor. Also, the stats on that item are Knight’s stats; the CM armors don’t offer Knight’s stats. So, the stats on that item are what would be on a set of Knight’s Heavy Plate Pauldrons.
It’s just really strange that a rune would transfer on a transmutation, the stats would change to the same stats as an exotic set of wvw-bought pauldrons, AND that the transmuted item doesn’t show that the transmuted item was “Wupwup’s Pauldrons”. :\
The June 23rd update made it possible to change attribute combos on ascended weapons and armor through the mystic forge (such as changing berserker’s into clarrion’s). The OP’s glitch might have something to do with that.
What might have happened: the game mistakenly thought the OP was trying to change the attribute combo on their equipment instead of the skin. The system randomly selected ’Knight’s’ attributes and since the Wupwup armor doesn’t come in that attribute combo it was completely downgraded to exotic quality of a random piece that does come with ’Knight’s’ attributes.
Unless transmutations and the MF use the same backend system, the odds of that happening are below zero. The more likely situation is 1) the OP transmuted the wrong item, particularly considering the fact that the provided screenshot shows that the item was never originally a wupwup piece, nor an ascended piece in general. Transmutations no longer overwrite rarity or stats, thus this is not really possible in the first place. Or 2) the OP is trying to steal something he never had in the first place due to the fact he cant salvage the rune out of karma gear.
3) the OP is reporting a legitimate bug so that this glitch can be investigated and possibly avoided by other people.
Not likely when no one else has been able to reproduce said bug. “Bug” not reproduceable? Then it’s not a bug.
Just because a bug can’t be reproduce does not mean it is not a bug.
If it cant be reproduced, then that means even Support cannot reproduce it, which means the devs cant fix it. You cant “fix” something that essentially does not exist.
