First and foremost, alongside these channels should come with restrictions to limit what the general Discord sees passively. The best way I can think to truncate our workload for this is to add it into your existing emote-reaction opt-in system if it can be done. Players can choose a town, then what feeds they want to "subscribe" to, ie which they can see, and then manage muting/hiding/show all show none etc from there.

It would definitely help limit how many messages disassociated members get about stuff they don't care about. It also makes each members' Discord seem tidier. Not sure how feasible all this is, just definitely something I want to try and incorporate right away if possible.

For each * are channel(s) planned, and need to be x2 for both towns. Anytime only one channel would suffice (somehow) will be listed but this is just a disclaimer if that becomes a reality, which I doubt.

Some channels listed, you already have in some manner or another, the redundant ones I list here are just for the things that I think should be included under the role opt-in system.

================
==PvP Channels==
================

Monthly/Weekly rotating channels:
* [?] for Silph Cups, including past ones (?), we will want to probably be able hide the channel and announcements and just turn them on for those "everything" cups they have shown to have occasionally. This can also be opt-in, so the channels only show for members who want to see em, and the bot is just spinning its wheels spitting into those channels even if no one has opt'd in to see them. At some point this becomes a little redundant, nearly all pokemon have become relevant in some manner or another in all Silph cups.... one would imagine. Which is where breakpoints come to play, these channels would also announce not only the pvp perfs for top contenders but any discovered Breakpoint spreads for the meta threats in each cup. This is probably going to be the hardest part of all this to create. Simply because adding info into the bot seems to be from discord commands only?

* 1 for Community Day, created the moment it is announced so players can prepare ahead of time and on the day of. It would be only Great/Ultra spreads. No assumed breakpoint spreads.

Permanent set channels:
* 2 for ALL Great/Ultra League PVP-100s.

* 2 for ALL Open GL/UL PVP-100s. Taken from PVPoke probably, top actual 30 or so. Not just their ranking but any gut feeling ones too.

* 1 for each branching evolution pokemon x forms combining GL and UL into one just to limit ridiculousness. For example, would be x7 feeds (for each town!) showing the GL and UL pvp perfs for each Eevee form currently in the game. This is required because, looking at the bot, we can't add "new pokemon" which would be "Eevee (Flareon Great)", "Eevee (Flareon Ultra)", etc etc you get the point. Something that tickles an OCD itch somewhere inside me but totally 100% not necessary. Particularly since most of the eevee's have no use in PVP. But also because there is an RNG factor in getting the eevee you want anyway after obtaining the correct spread. So not really sure if we even want to deal, but just throwin it out there. There will be multiple eevee's submitted for the other channels as necessary, this would just be to filter them out so if someone was say, specifically hoping for a jolteon, they would know right away if the eevee the bot found was the spread for a jolteon or not.

================
==PvE Channels==
================

Monthly/Weekly rotating channels:
* 1 for Current 5* Raid Counter 100 IVs. Lifting straight from whatever guides are available for countering the most recent raid bosses, a tracker channel for only 100 IV wild counters to the current 5* raid boss. Non CD stuff included. So its not gonna say to get a Tyranitar when its assuming you're gonna need Smack Down. A savy player is gonna chase down a perfect larvitar spawn anyway, and Elite TM what they need if that's the case but the goal of this would be simply all wild-caught perfs that are useful vs a current raid boss.

* 1 for Current EX Raid Counter 100 IVs. Same but perhaps less necessary. We zerg down EX raids and this would just be for optimizing speed or low raider # clears I guess?

* 1 for ALL 100 IV.