Mass Evolve

So to start with, I'll just put up front that I did find this thread that already shot down the concept of mass-evolving in fields. There's too many complications, and I get that. Edit; This rejection also exists, but I felt that mine was distinctly different in that it focuses on species, not type. Furthermore, Niet did not give any criticism in that thread beyond "learn your types", so it wasn't a total takedown of the idea, in my view. If I'm wrong I'm sure they'll let me know! Summary: Compile same-species evolutions in the Farm page for quick mass-evolutions to make it easier on high tier badge Wishforge users. Pros: Beneficial to all people who use the Wishforge to get above the Titanium badge, neat/clean design that reduces load time & scroll length for extensive Farm lists, plenty of flexibility for how many Pokemon can be in batches or what qualifies as a batch, no leaving the Farm page, structure of evolution still remains the same. Cons: Eeveelutions, shiny/albino/melanistic pokemon that are RTE and therefore are batched and accidentally evolved with everything else since you do not have the ability to see a visual indicator of a shiny/albino/melanistic Pokemon the way you do now. Edit to add a con; Poor Sally. Potential Solutions to Cons: Longwinded version below, if that's not clear enough. A note: I personally believe that all UI changes should be toggleable. There should always be a way for a user to choose whether or not to use a feature. This includes my suggestion. Batch evolving may not be for absolutely every single person on this site, but a great deal of people would benefit and use the feature, so making it an option is the ideal situation. I really hope this makes the concept of mass-evo more approachable for Staff. I read the full thread on why fields were rejected, but I really think this is a winning idea. I look forward to feedback!

Something similar has already been rejected. Though that one is about type and not species, it's still similar.

@Zen I saw that! I should probably include that in my opener. But I felt that the focus of that post being "type" and not species is an important distinction to make. Anything involving type gets messy fast. Species is way more streamlined, and Niet's only criticism on that thread was just basically "learn your types", so I didn't feel it was an actual takedown of the concept, more of the fact that the reasoning behind it wasn't sufficient.

Well, it's still similar, so others might've brought it up as well since you didn't mention it. :p Though honestly, if you're only using one species then I don't see how their will be much of an issue. I mean, I have a bunch of Zorua that are waiting to evolve and they've taken over my ready to evolve section. xD Not only that, special Pokemon show the corresponding star in the evolve section. I just checked this to be sure, and two of my shinies have the gold star next to their names in the list. So if someone evolves them by accident that's kinda their own fault for not paying attention.

@Zen Oh no, I agree with you! I've always believed that accidentally evolving anything is the user's own fault, ahha. I was trying to say that potential opposition to the concept of batch-evolving is that like, since it will be lumped together in a group, you won't be able to see the little star indicator for shiny pokemon anymore, if this is put through. You won't be able to individually see every single pokemon you are evolving, so you'll probably end up evolving shiny/albino/melan pokemon if they aren't holding Everstones. That's why I said "The issue of accidentally evolving special pokemon is solved by...well, giving any pokemon you don't want to evolve an Everstone. I think that's really the only way to get around it, and I wouldn't qualify that as an actual con."

Main issue I see if the possiblity of Sally choking upon being told to evolve 100+ Pokemon at once. Telling a system 100 times to perform an action is different than telling it to perform an action 100 times.

@Mystera I'll be honest, it was hard not to include that in cons because I have zero concept of what is and isn't difficult for Sally, and I wasn't sure if it came off as a it's hard to do type line. I'm still hoping though. Maybe there's a workaround somewhere in the distant future. was something Niet said independently, so I'm kinda riding on that hope haha. Late edit; but I just thought of another point. Helping Sally out, you could keep the batches small. Even batches of 50 would be better than individually evolving 640 Pokemon. That's like, 12 batches and then some leftover individual evos.

i support this. badges can be such a headache, especially on mobile 🙄 the hard part should be getting the pokemon rte, not physically scrolling and clicking evolve hundreds of times

I totally agree with you tape on this whole ideal that when you go to upgrade a badge, it should be easy to do, and not as boring and tedious as having to click over and over again.

As much as it sounds great to be able to mass evolve for badges.... I don't support. For the same reason I didn't support mass release either, which was shot down for I think the same reason. What if a account got hijacked and the person felt like being funny and decided to mass evolve the pokes? It's easy enough to evolve pokes via the farm page, I don't see the need for making it any easier. Sorry.