Need some "sell all" buttons

[DarknessEternal]

Sell all recipes.

Sell all enhancements.

Sell all salvage.

 

Simple code, direly needed.

[srmalloy]

There is already a 'sell stack' function for the people who don't want to click once per item in a stack of fifteen or so, but I fail to see how multiple button clicks are so incredibly onerous to require a completely new functionality.

[Oklahoman]

Personally, I'd love to see it. 3 button clicks and I am "cashed out"? Sounds wonderful.

[srmalloy]

1 hour ago, Oklahoman said:

3 button clicks and I am "cashed out"? Sounds wonderful.

And then we'll have people whining about how they clicked 'sell all' and it sold their orange salvage for 5000 inf, and insist on either having an option to to disable 'sell all' for salvage by class, or having separate buttons to sell each class of salvage, and want a button to put their orange salvage into the AH so it doesn't get accidentally sold on the cheap.

[tabbycat1]

I would like this function. Right now i use voice attack and macroed a button to drag my recipes to the ah 80 times.

[Oklahoman]

2 hours ago, srmalloy said:

And then we'll have people whining about how they clicked 'sell all' and it sold their orange salvage for 5000 inf, and insist on either having an option to to disable 'sell all' for salvage by class, or having separate buttons to sell each class of salvage, and want a button to put their orange salvage into the AH so it doesn't get accidentally sold on the cheap.

 

I guess I don't see a problem with improving the functionality later, if the feature proves useful. As it is, I know I've accidentally sold MANY orange salvages for 5,000 inf over the course of an ohnosecond, just hitting the sell button as fast as possible. If I'm thinking straight I tend to sell those on AH first, then go "cash out."

[srmalloy]

3 hours ago, tabbycat1 said:

I would like this function. Right now i use voice attack and macroed a button to drag my recipes to the ah 80 times.

@DarknessEternal's request is to enable dumping enhancements, recipes, and salvage to a vendor, not into the AH. That would be an entirely different change.

[Greycat]

16 hours ago, DarknessEternal said:

Simple code, direly needed.

I don't know about direly needed, and simple's kind of a minefield with the spaghetti code of the game. 🙂

 

That said, if accidental clicks are a worry, make them slash commands (/sellrecipe all, /sellrecipe common, /sellsalvage common all, etc.) that people can make their own macro buttons of if they wish.

[DarknessEternal]

18 minutes ago, Greycat said:

I don't know about direly needed, and simple's kind of a minefield with the spaghetti code of the game. 🙂

 

I could do it in under an hour.

[Vanden]

22 minutes ago, DarknessEternal said:

I could do it in under an hour.

 

I encourage you to volunteer your time and talents, then.

[DarknessEternal]

2 hours ago, Vanden said:

 

I encourage you to volunteer your time and talents, then.

I was declined, but let's try to stay on topic here.

Edited October 18, 2022 by DarknessEternal

[DarknessEternal]

8 hours ago, srmalloy said:

And then we'll have people whining about how they clicked 'sell all' and it sold their orange salvage for 5000 inf, and insist on either having an option to to disable 'sell all' for salvage by class, or having separate buttons to sell each class of salvage, and want a button to put their orange salvage into the AH so it doesn't get accidentally sold on the cheap.

So, for clarity, your position is "some people are stupid, so everything has to suck to appease them."?

[biostem]

Incorporate a warning like they have for selling salvage for recipes you own, and you should be good to go...

[srmalloy]

19 hours ago, DarknessEternal said:

So, for clarity, your position is "some people are stupid, so everything has to suck to appease them."?

No, my position is that prioritizing code changes based on complaints of "It's not convenient for me to have to do this; change it so these things are done for me" is poor code design practice. There are enough real problems with the code that should be fixed that "I don't want to have to click so many times" should be deeply buried in the pile.

[Sneakers]

On 10/18/2022 at 12:46 PM, srmalloy said:

No, my position is that prioritizing code changes based on complaints of "It's not convenient for me to have to do this; change it so these things are done for me" is poor code design practice. There are enough real problems with the code that should be fixed that "I don't want to have to click so many times" should be deeply buried in the pile.

 

But adding a button that sells the lot seems like it wouldn't be that difficult.

 

bottom line it's a good idea. But you don't agree with that. Because then you think people would be up in arms about accidently clicking it. So we need to do what's best for those idiots instead.

[srmalloy]

10 hours ago, Sneakers said:

But you don't agree with that. Because then you think people would be up in arms about accidently clicking it. So we need to do what's best for those idiots instead.

No, it's based on, in going on 40 years as a programmer, seeing exactly this chain of "Make this change to make this one little thing more convenient!" [change made] followed by a long string of "The change does something I don't want if I use it without thinking first; fix it!" as people want ever more specific alterations that affect fewer and fewer people until the first change becomes more complicated to use than things were before the change was made.

[lemming]

3 hours ago, srmalloy said:

No, it's based on, in going on 40 years as a programmer, seeing exactly this chain of "Make this change to make this one little thing more convenient!" [change made] followed by a long string of "The change does something I don't want if I use it without thinking first; fix it!" as people want ever more specific alterations that affect fewer and fewer people until the first change becomes more complicated to use than things were before the change was made.

Yep. It's a better example of feature creep.

 

I think a better designed selling system might be in order, but I do wonder how much of the code is shared between player trades, auction house, vendors, etc...

 

I think the ability to check off a bunch of items and then hit "Sell all clicked items" with a verification OK might be the way to go, but it's a lot more complicated to code currently.