My experience with the quick search filter for Rayquaza counters
The other day I wrote about a search filter I made for helping my community to make teams of rayquaza counters (here https://www.reddit.com/r/TheSilphRoad/comments/b1dblc/quick_search_code_for_rayquaza_counters/). I'm going to explain my experience putting that filter in practice.
My community is pretty small, and our main problem is not having enough people for raiding. Also, most players are low-middle profile. So before raiding, the more veterans have to spend a lot of time helping the other players making teams, if we want the raid to success. The problem is that, in addition to the time spent, we don't really know what pokémon the other players have. So I could recommend a counter but the other player only has one. An then say another one, and the other player only has low level ones, and so on.
This time, instead, we have used the quick search filter I put in the other thread. I wrote @1ice,@1rock,@1dragon&@2ice,@2rock,@2dragon,@2fairy,@3ice,@3rock,@3dragon,@3fairy in our messaging group for raids. Before beginning the raiding session, I explained the other players how to copy and paste that code in the search box, and how to use that code for quick-making the raiding team. I discovered that, even after sharing several guides, some people was making some big mistakes like using Mamoswine with bulldoze, because Mamoswine was the recommended counter in all the guides. But with that code all that mistakes were overridden. We started the raids with every player having two full teams. No bulldoze mamoswine. No aggron. We defeated rayquaza eight times without problem. We were even able to make a trio. So I can say the "quick search strategy" has been a big success.
And that's all. I wanted to share it in case it's helpful to other raiding groups.
TL;DR: We have used in my community a quick search filter for helping players to make teams of rayquaza counters, and it has been a complete success.
EDIT: I confused bulldoze with earthquake.
Posted Mar 18, 2019, 5:13 PM UTC · edited
Nice work. This is what should be coming up as the "Recommended" team, Niantic please take note.
Personally, I don't like the idea of the game recommending an optimal team, because in that case players do not even have to bother about learning type effectiveness.
As opposed to the current situation where many players still don't bother to learn type effectiveness and stick with their recommended Aggrons?
This still won't be "optimal", it'll be close enough. Making it hard to find good choices doesn't mean people will work harder to make good choices, they'll just make bad choices.
Even if this works, it's not like it teaches you what to power up, or it doesn't teach you that aggron is worse than metagross when steel types are ideal even if you have matching CPs.
I think the opposite might be true. It could help teach players type effectiveness to see the game pick a team and then see "supereffective" while they're playing.
They will need to know what to evolve, power up and tm, though
What Niantic suggest is not wrong. It's just that in the case of the time race with a raid boss, we want optimal damage, not optimal all around.
I feel like we need multiple options for auto-select teams, a defensive option, an offensive option, and a balanced option.