scylla
Recruit
Shar of Dragonblood Clan
Posts: 19
|
Post by scylla on Dec 21, 2008 17:12:56 GMT -6
I've been sending a couple of Talismans to the gang vault when i noticed the following:
- Combining an assigned talisman from the Vault with a talisman from your inventory leads to the talisman being sellable again.
- Combining two assigned talismans leads to the item still being marked as coming from the Vault (which it should), but causes another problem.
- The talismans created during the top two scenarios cannot be recalled to the Vault, as they are 'in use'. Given that the second talisman is still gold and cannot be sold, it's kind of stuck right now until i slap it on an item.
I have not tried re-donating the first item yet.
|
|
scylla
Recruit
Shar of Dragonblood Clan
Posts: 19
|
Post by scylla on Dec 21, 2008 17:27:31 GMT -6
O...kay...
I redonated the first item (Diseased Talisman of the Blight) and it showed up in my Vault. Unfortunately, the Diseased talisman i withdrew to create it is still listed as being assigned to me, so essentially it's in my Clan Vault twice now.
What's more disturbing is the second bug i found.
Combined a Tarnishing talisman from my Vault with a talisman of Soldiers from my inventory. Since the box appeared again, i uncached it, and sold the item. That worked, as it disappeared from my inventory.
HOWEVER, when i was in the Vault it still said the Tarnishing talisman i sold was assigned to me. Recalling it worked, and so did reassigning it to myself. I could potentially combo a badass talisman and keep slapping it on random trash, recall both talismans and repeat the process until my purse explodes.
Figured you'd want to get that fixed ^^;
|
|
|
Post by alSeen on Dec 21, 2008 17:34:43 GMT -6
thanks for telling me that. i may use it.lol just joking
|
|
|
Post by alSeen on Dec 21, 2008 17:36:50 GMT -6
just tried it. didnt work. maybe its just the talis u used or u have more than one in your vault
|
|
scylla
Recruit
Shar of Dragonblood Clan
Posts: 19
|
Post by scylla on Dec 21, 2008 17:37:30 GMT -6
Update
Taking the assigned item to enhance a non-assigned item works correctly, but the other way around (using a non-assigned talisman on an assigned talisman) seems to be what's causing the error.
Also, it seems that (gold) items achieved in this manner can't be recalled either, maybe something to do with being set as Cached, so the game thinks it's still in use?
Update 2
It seems to work for items, just tried it with a cudgel i had previously donated. Still getting the "You cannot withdraw an item that is in use!" message trying to recall or discard it though, so i'm stuck with three items i can't recall now :/
|
|
scylla
Recruit
Shar of Dragonblood Clan
Posts: 19
|
Post by scylla on Dec 21, 2008 17:58:04 GMT -6
Right, narrowing this down to where i first noticed it.
Items used: - Blacksmith talisman - Talisman of Ogier (from Vault)
- Recall talisman of Ogier, check - Use Blacksmith talisman (non-assigned talisman!) on Talisman of Ogier, check - Uncache newly created Blacksmith talisman of Ogier, check - Sell Blacksmith talisman of Ogier, check - Go to Vault, return Talisman of Ogier, check
Worked for me again...
Edit
And for some reason, i managed to return all the gear that got stuck, including the two talismans i duped and couldn't return. Go me.
|
|
|
Post by Tim on Dec 21, 2008 20:05:08 GMT -6
Interesting. I'll have to play around with the vault more. Thanks for the detailed error report! Go Team!
|
|
|
Post by Tim on Dec 31, 2008 11:22:16 GMT -6
Ok. I think I finally solved this one. The issue was the way I was identifying which items needed to be removed from the vault. If it had talisman in the name, it assumed it was the talisman you used marking it as found and therefore ignoring any other matches for that talisman (in case you had withdrawn 2 talismen of the same name), so the real one never got removed. This is also where it copied the clan name over to the item, and since the one that was found mistakenly was not really a clan item, it ended up erasing it.
A big thanks to scylla for the very detailed bug reporting. Made fixing this one a lot easier than it could have been. Go Team!
|
|