Site Forum

I thought there was a warning of somekind that informed you that a card in this trade is also in another trade offer you have.  I had two offers going where I select the cards I need and I add one card and let them select the others they want.  They both added many of the same cards.  I didn't get any indication they had selected the same cards until I went to pull the second trade and now I to scramble to fix it.  This isn't the first time I have run into this because I typically have several offers pending at the same time.   

There has to be a way of preventing selecting or warning when a card is in another pending transaction.

I agree with you.  Since that feature was brought in, I did not find it worked properly so I found myself still having to check the cards in each offer, both what I was being offered and what was being asked for.

Just another reason for me to feel good about limiting myself to one trade going at a time. I'm amazed at the members who can have many trades going at once. Of course I'm still working 65 hours a week so that creates some of the limitations I have.

I have been running into this issue also. Especially on the receiving end of cards. It doesnt let me know that cards are already on the way to me and only removes from my want list when I mark package received. Got a lot of duplicates lately.

When you initiate an offer that warning function works fine. The problem is when you receive an offer or counter it doesn't show anymore. 

I have a counter i submitted and received an offer from someone else that included the same card, but there was no warning. I didn't realize it until I countered that second offer that the warning popped up. 

So is that something we could bring up to the Admin to see if he can fix or is that something that goes on the new feature request.  Technically the feature exists it could just be updated? 

I'm sending an email to Admin because I feel like you that the feature exists. 

---Done---

Per Admin this issue is fixed. 

Thats awesome!

Not only did he fix it, but he added the Transaction # to the warning!