search

xyzz / acquisition

http://get.acquisition.today/
GNU General Public License v3.0
270 stars 98 forks source link

Multiple stacks of the same item #62

Open tstindt opened 9 years ago

tstindt commented 9 years ago

Example: Stashtab #1 has 2x10 chaos, I set a buyout for 20 fuses. Stashtab #2 has 1x10 chaos in it, which are now also offered for 20 fuses, but i want them to be sold for jewellers.

Changing either of them will change the prize on all stacks of chaos.

xyzz commented 9 years ago

Sadly there's no solution to it due to how GGG sends us item data -- there's simply no way to differentiate between these items. Unless we of course take tab into account, but then we'll have different problems -- prices disappearing due to tab rename / item moving. I'm not really sure what to do here. Do you know how Procurement solves this? Oh, and I think poe.trade will filter out the same items anyway, so only one of the same type will be displayed.

tstindt commented 9 years ago

No i don't know how Procurement does this, but (at least for me) this is quite important. I'd gladly take that solution and not be able to move items without loosing the price. I don't know how much work this would be, but maybe you could add this as an option uses can opt-in, or which is active for stackables only (if that is possible?).

It's about doing "reverse WTB's" like "wts 10c = 20fuse" AND "wts 10c=80jewllers" for example.

tstindt commented 9 years ago

Guess this also belongs here, same issue. Offering the unid unique map also sets a price for the white map. Maybe you could add some check for same rarity? unbenannt

silvermoona commented 9 years ago

I think this is a somewhat related issue. I'll try to explain by using an example. I have two tabs A and B. In TAB A (marked as ignore) I got a L20/Q20 Gem and in TAB B I got the same L20/Q20 Gem being corrupted though. If I mark the corrupted L20/Q20 with a buyout in TAB B, the non corrupted L20/Q20 gem get's the same buyout. I also don't know how Procurement handles this, but I would gladly take the solution for taking tabs into account and live with the drawbacks.

Nhatorama commented 9 years ago

"Do you know how Procurement solves this?"

As far as I know it doesn't. I've made a similar "Issue" thread on the Procurement's GitHub. https://github.com/Stickymaddness/Procurement/issues/140

widardd commented 9 years ago

Oh, and I wondered why no one is buying one of my 4 Q20 gems. Could we get a quick and dirty fix for this? Just allow us to price one item with the same name at the time and pop up a warning about the current limitation.