Yes pleeeeaaaaase. Mass remove (check boxes please !), and hover names (like when you go to a pets page, you can see the name when hovering an item). I am going to be switching beanbags out of Booty's tc and into Luga's. This is going to be Hell.
pls 10000% support TCs are kind of a pain as they are rn
Yes please.
My TCs are ever growing
Hi. I have a million duplicates in a pet treasure. (read 50+) and being able to sort by either name or Item ID would be massively helpful when trying to remove duplicates. Please? Pretty please?
[Center][Url=https://www.youtube.com/user/ShutupandLetsPlay4]Shut up & Lets Play! Youtube Channel[/url][/center]
RE: Mass removing items There will need to be a limit. Some pets have 1000+ items in their treasure, and attempting to remove them all at once would likely result in a 504 error and items vanishing from your account. Unfortunately this is just a limitation we have to live with.
I am thinking a mass remove page with checkboxes and pagination. TBH the main page could also use some pagination, though at least click-to-move makes organizing giant TCs less laggy. We just can't think of a way to paginate it and still let you organize it easily across the pages that it would have.
There would be a limit as to how many you could remove at once, and it would tell you when you check too many items, similar to the TC Mass Add page. I'm thinking, for those who want to remove all the items, it could have a button like "Check first 50" so you don't need to manually check all the checkboxes.
What do you think of these ideas?
RE: Auto sorting options Again the main concern here is large TCs, where sorting them all at once would... potentially be a huge server strain, if we're looking at thousands of items. The only compromise I can come up with here, is to allow auto-sorting on TCs that are below a certain size only. However I feel that might defeat the purpose (usually people want auto-sorting to help them manage super big TCs, not smaller ones) and it also seems kinda unfair to only let some TCs have this option. So this may be a suggestion we have to drop, unless you can brainstorm a better compromise?
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights
I know nothing about code and my computer expertise is pretty much limited to the power switch. But, fwiw, I personally have no trouble with limits on sort options. Maybe limit the ability to sort by page but allow us to highlight & move multiple items forward or backward a page? If there were direction arrows at the top of each page and we could R-click or something to highlight all the items we want to move to a page < or >. Even with limitations, it would still be better than what we have now.
It would be great if the limit was 50 or 100 items at a time, it's fine if that doesn't happen but I agree with the limit idea overall.
[tot=PiplupMagby34]
I'm afraid that people with larger TCs would be upset, that it would be a feature specifically not available to them. That honestly does seem unfair, like it would be punishing them for using the TC feature. I wouldn't want anyone to feel that way, hence my hesitation.
At the moment I don't think we are going to implement pagination as a general thing, only on the Mass Remove page since it doesn't matter as much there and it could reap the benefits. As long as the pet profile shows all the items at once, I think the organize page needs to as well.
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights
The limit would probably start off at about 25, because it's best to start small! But we may then increase it based on what we observe with the usage. This page probably won't be used super often, so we may be able to increase it a lot over time :)
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights
Stupid question: how many users/pets have tcs with a thousand items or more?
Another stupid question: If things were paginated, why would the feature not be available to users with lager pet tcs? Doesn't pagination solve the lag issue with large tcs? (Is my ignorance showing?)
For your first question: more than you'd think, and either way, those users matter to us even if they're not the majority.
Pagination would only solve the issue of displaying the items - as it would only display a certain number at a time. However, sorting needs to involve all the items no matter how they are displayed. If I ask you to sort 3000 numbers, you have to look at all 3000 of them to sort them correctly, you can't really sort like 500 at a time while ignoring the rest. Does that make sense?
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights
Thanks for the explanation. :) It does make sense. I had actually assumed that it was only sorting by page and not all of the items instead of the way you describe.
Personally I'm against pagnation for sorting tcs. for removal that would be fine. just my opinion tho :) (because flight rising does that and it annoys the crap out of me when i have to go through multiple pages to move a dragon.) I assumed any kind of mass remove would have a limit, it only makes sense :)
Hmm.. brainstorming ways to sort? What about check-boxes next to the rows that are already there, once checked it selects the whole row? Or maybe put selectable check boxes by all of them and have it (like the battle front page?) where once checked it moves the items into another box which you can then mass remove from and have that box have a limit of like 40 or something. (Just throwing that number out there) gives people a chance to preview what they're removing and if the box could stay on multiple pages it could be used for a pagnation type of page.
i'm illiterate when it comes to this stuff, but re: sorting (by id, rarity, etc)... how is it different from sorting the vault or user shops? shops might be limited now, but vaults aren't.
This is true, but sorting the vaults is an expensive operation. We want to be wary about adding expensive operations like that to more parts of the site.
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights
I don't have any ideas for a way to auto sort feasible with large TCs, but I just wanted to say how much I appreciate staff taking those of us with massive TCs into account. It would definitely be very upsetting to be cut out of certain features for loving TCs too much.
As for pagination/limits/etc on a mass removal feature, that sounds fine. Anything would be better than what we have now. As long as TC organization doesn't get paginated (which would make it very hard/impossible to do certain types of large TCs) having it for removals wouldn't be that big a deal.