Resource Solomods Megathread

[Nootathotep]

yeah sorry, I understand now, I had trouble parsing the acronyms and stuff at first

 

[guruu]

I'm a fan of the concept. I don't know how organising solomods really works, but instinctively the large amount of new stuff does make it feel a bit intimidating to me. For this and the mega man mod I feel it would be a bit more approachable if it had been played a bit more and a meta started to develop. Perhaps a randbats version would be a fun starting place. Or perhaps we just need more solomod enjoyers regardless of the tier itself, who knows.

Click to collapse...

Yeah, a mod with 100+ new Pokemon, each with its own new signature move, can be overwhelming.

To make the mod more digestible, I built each Robot Master's base stats around an existing Pokémon. I also limited each one to a single competitive ability and 12 moves (excluding its signature move, Endure, Protect, Substitute, Rest, and Sleep Talk).

I currently have MM1-4 coded and will stop there until the mod is playable. 31 new additions shouldn't be too difficult to pick up and play with.

 

[Nootathotep]

Yeah, a mod with 100+ new Pokemon, each with its own new signature move, can be overwhelming.

To make the mod more digestible, I built each Robot Master's base stats around an existing Pokémon. I also limited each one to a single competitive ability and 12 moves (excluding its signature move, Endure, Protect, Substitute, Rest, and Sleep Talk).

I currently have MM1-4 coded and will stop there until the mod is playable. 31 new additions shouldn't be too difficult to pick up and play with.

Click to collapse...

I don't think the stat distribution is bad but looking from the outside the stat basis does not seem like a reliable way to get a sense of the tier imo. For example, if I were playing AAA and I saw Slurpuff with Poison Heal, or Godly Gift and Slurpuff with Groudon's ATK, I would have an intuitive understanding of what I'm up against, but Slurpuff but with four increased stats, a normal typing, new abilities, no sticky web or belly drum at that point the Slurpuff comparison can't be relied on for much. I still think doing it this way is valid because it makes the pokemon feel plausible and natural stat-wise and provides some design intent, maybe it's good for memorisation down the line when you have a bit more experience, but if I'm looking into the tier for the first time there's a lot to memorise and consider

Definitely keeping the roster at 31 to start with sounds like a good idea. 31 characters and 31 new moves seems quite manageable, I guess the format needs a home but when it has one perhaps the other robot masters could be added gradually to give opinions on each master room to develop. 100 is a lot for a single tier, maybe if all 100 are available there will be clear ou vs uu vs potentially uber distinctions, if you want to let them be that way.

(On another note 15 of the first 31 are normal types. Rock, ground, fairy, bug and flying are absent entirely while grass, poison and dragon have one each. There's more variety in the later list but normals are still very common; some offensive typings seem much more useful than others. I know it's very difficult to distribute types evenly while sticking close to canon, especially in small numbers, but I think it's worth looking into pruning the number of normals)

 

[Toxic Ariados]

I don't think the stat distribution is bad but looking from the outside the stat basis does not seem like a reliable way to get a sense of the tier imo. For example, if I were playing AAA and I saw Slurpuff with Poison Heal, or Godly Gift and Slurpuff with Groudon's ATK, I would have an intuitive understanding of what I'm up against, but Slurpuff but with four increased stats, a normal typing, new abilities, no sticky web or belly drum at that point the Slurpuff comparison can't be relied on for much. I still think doing it this way is valid because it makes the pokemon feel plausible and natural stat-wise and provides some design intent, maybe it's good for memorisation down the line when you have a bit more experience, but if I'm looking into the tier for the first time there's a lot to memorise and consider

Definitely keeping the roster at 31 to start with sounds like a good idea. 31 characters and 31 new moves seems quite manageable, I guess the format needs a home but when it has one perhaps the other robot masters could be added gradually to give opinions on each master room to develop. 100 is a lot for a single tier, maybe if all 100 are available there will be clear ou vs uu vs potentially uber distinctions, if you want to let them be that way.

(On another note 15 of the first 31 are normal types. Rock, ground, fairy, bug and flying are absent entirely while grass, poison and dragon have one each. There's more variety in the later list but normals are still very common; some offensive typings seem much more useful than others. I know it's very difficult to distribute types evenly while sticking close to canon, especially in small numbers, but I think it's worth looking into pruning the number of normals)

Click to collapse...

Yeah, a mod with 100+ new Pokemon, each with its own new signature move, can be overwhelming.

To make the mod more digestible, I built each Robot Master's base stats around an existing Pokémon. I also limited each one to a single competitive ability and 12 moves (excluding its signature move, Endure, Protect, Substitute, Rest, and Sleep Talk).

I currently have MM1-4 coded and will stop there until the mod is playable. 31 new additions shouldn't be too difficult to pick up and play with.

Click to collapse...

Seeing as this discussion is interesting, I think I'll give my two cents on this.

Yeah, I definitely agree with the fact that basing your Pokemon's stats off of an existing Pokemon is not a reliable way to understand how the custom Pokemon functions. After looking through the Mega Man pokedex I don't quite understand the "base Pokemon" comparison. Taking Ice Man for example (who uses Iron Bundle as a basis), can this really be considered similar to Bundle if it has Fur Coat over Quark Drive, lost the Water typing, and has recovery in Slack Off? These two Pokemon play entirely differently, to the point where the only real comparison you could make here is that they both share the Ice type. I also disagree with the notion of basing a custom Pokemon's stats off of a pre-existing one. To me it just feels like regional variants with extra steps, and I do think it limits one's creativity by a good margin. While I do think it's useful to use one successful Pokemon's competitive role as a basis to design your own, I think that limiting yourself to only slightly deviating from that Pokemon's stat spread (unless you are specifically trying to design a regional variant) inhibits how creative you can get when designing your Pokemon's competitive role.

Though, what I don't get is why it was necessary to limit each Pokemon to like a dozen moves and one good ability (for the most part). I think a direction like that will limit the amount of creativity that players will have in the teambuilder. Each Pokemon might just end up feeling like a one-trick pony, running the same 4-5 moves and ability. I think that giving some Pokemon a good amount of versatility is healthy for the meta, that way players can come up with clever techs to deal with meta threats or help patch up some of their team's weaknesses. With such limited movepools and ability choices, it seems like there won't be much room for experimentation, and each Pokemon will be stuck running the same sets whether they like it or not.

I also disagree that a mod with 100+ new Pokemon is overwhelming, perhaps I'm biased because my own mod has over 150 custom Pokemon, but I don't think its that hard for even amateur players to grasp. As long as any signature moves are somewhat intuitive to use, players should be able to pick up on them relatively quickly (were things like Vessel of Ruin and Revival Blessing that hard to understand during the beginning of Generation 9?). If a player wants to know what any move does they can always /dt it in the middle of the battle. I also think that formats with smaller dexs are at risk of becoming too stale after a while. A dex with 20 Pokemon will inevitably leave less room for teambuilder creativity than a dex with 100 Pokemon. While the bigger dex will inevitably have some centralization in the form of top tiers (I think some form of centralization is good for any meta!), there is a lot more room to play with off-meta picks. In a smaller dex, sometimes it'll feel like you can only run the same few Pokemon in a team due to how little options you have.

 

[guruu]

(On another note 15 of the first 31 are normal types. Rock, ground, fairy, bug and flying are absent entirely while grass, poison and dragon have one each. There's more variety in the later list but normals are still very common; some offensive typings seem much more useful than others. I know it's very difficult to distribute types evenly while sticking close to canon, especially in small numbers, but I think it's worth looking into pruning the number of normals)

Click to collapse...

Yeah, I was worried about this. That's why the current code is set up to include standard Gen 9 Pokemon as well. On my next update, I'll ban standard Pokemon and I'll add two more MM games by Robot Masters who will help balance the meta, instead of going in game order.

Yeah, I definitely agree with the fact that basing your Pokemon's stats off of an existing Pokemon is not a reliable way to understand how the custom Pokemon functions. After looking through the Mega Man pokedex I don't quite understand the "base Pokemon" comparison. Taking Ice Man for example (who uses Iron Bundle as a basis), can this really be considered similar to Bundle if it has Fur Coat over Quark Drive, lost the Water typing, and has recovery in Slack Off? These two Pokemon play entirely differently, to the point where the only real comparison you could make here is that they both share the Ice type. I also disagree with the notion of basing a custom Pokemon's stats off of a pre-existing one. To me it just feels like regional variants with extra steps, and I do think it limits one's creativity by a good margin. While I do think it's useful to use one successful Pokemon's competitive role as a basis to design your own, I think that limiting yourself to only slightly deviating from that Pokemon's stat spread (unless you are specifically trying to design a regional variant) inhibits how creative you can get when designing your Pokemon's competitive role.

Click to collapse...

The base Pokemon is only here as a visual reference to each Robot Master's base stats. Ice Man is not "Iron Bundle with a few changes." They are two completely different Pokemon with similar stats - one is an offensive attacker/utility, the other is a defensive utility/attacker. If it makes it less complicated, I can remove the base Pokemon altogether and maybe just highlight each Robot Master's notable stats. The goal is to create helpful ways to learn/remember each Robot Master's stats.

Though, what I don't get is why it was necessary to limit each Pokemon to like a dozen moves and one good ability (for the most part). I think a direction like that will limit the amount of creativity that players will have in the teambuilder. Each Pokemon might just end up feeling like a one-trick pony, running the same 4-5 moves and ability. I think that giving some Pokemon a good amount of versatility is healthy for the meta, that way players can come up with clever techs to deal with meta threats or help patch up some of their team's weaknesses. With such limited movepools and ability choices, it seems like there won't be much room for experimentation, and each Pokemon will be stuck running the same sets whether they like it or not.

Click to collapse...

We disagree here. Most OU threats basically use 6-10 moves and 1 ability to build 2-4 different sets. I applied that same logic here. Fire Man can function as a Scarf/Specs Attacker or a mixed Wall-Breaker, and Wood Man can be a Belly Drum Sweeper, a Bulky Swords Dance Tank, or an Hazard setting Wall.

But even with that said, I am definitely open to adding a few more moves and a third ability to each Robot Master. I'd like the communities input as well, so I'll probably set up a small council and/or a quick pet-mod in the future.

(Also, I should clarify that each Robot Master technically has 17 moves. I didn't list Endure, Protect, Rest, Sleep Talk, Substitute in their Dex movepools, but they are coded in their learnsets.)

I also disagree that a mod with 100+ new Pokemon is overwhelming, perhaps I'm biased because my own mod has over 150 custom Pokemon, but I don't think its that hard for even amateur players to grasp. As long as any signature moves are somewhat intuitive to use, players should be able to pick up on them relatively quickly (were things like Vessel of Ruin and Revival Blessing that hard to understand during the beginning of Generation 9?). If a player wants to know what any move does they can always /dt it in the middle of the battle. I also think that formats with smaller dexs are at risk of becoming too stale after a while. A dex with 20 Pokemon will inevitably leave less room for teambuilder creativity than a dex with 100 Pokemon. While the bigger dex will inevitably have some centralization in the form of top tiers (I think some form of centralization is good for any meta!), there is a lot more room to play with off-meta picks. In a smaller dex, sometimes it'll feel like you can only run the same few Pokemon in a team due to how little options you have.

Click to collapse...

With you recommending that I expand, and Nootathotep recommending the opposite, I think a happy middle ground for now is a "Robot Master Only" meta with 30-50 different options to choose from. That feels like a comfortable starting point, and we can always expand from there.

 

[Aevilok]

[Gen 7] Infinite Fusion Dex OU

​

Name of Mod: Infinite Fusion Dex OU
Mascot:

Link to Changes: play.pokeathlon.com
Summary of the Mod: Pokemon can be fused! Each fusion has:
- The movepool and abilitypool of both components,
- One type from each component (primary type from the Head pokemon, secondary type from the Body pokemon)
- A weighted average of the components' stats (the Head pokemon gives 66% of its HP, SpA, and SpD, and 33% of its Atk, Def, Spe, and vice versa for the Body pokemon).
Competitive Overview: Metagame Staples Resource, JimothyCool Video
Meta Note: This solomod has already been active for almost 3 years with a dedicated community, thousands of games played, and has proper UI support for the fusion mechanic since it's hosted outside showdown.

Viability Rankings

format: top column = head, bottom column = body, sorted in pokedex order

S

none

A+

Nidoking

:gengar:	:moltres:	:zapdos:	:regice:	:togekiss:	:hydreigon:
:nidoking:	:nidoking:	:nidoking:	:nidoking:	:nidoking:	:nidoking:

Gliscor

:gliscor:	:snorlax:	:suicune:	:rhyperior:
:golisopod:	:gliscor:	:gliscor:	:gliscor:

Meloetta-Pirouette

:ursaring:	:entei:	:crawdaunt:	:tangrowth:	:genesect:	:hydreigon:	:tyrantrum:	:necrozma:
:meloetta-pirouette:	:meloetta-pirouette:	:meloetta-pirouette:	:meloetta-pirouette:	:meloetta-pirouette:	:meloetta-pirouette:	:meloetta-pirouette:	:meloetta-pirouette:

A

Clefable

:clefable:	:clefable:	:clefable:	:clefable:	:clefable:	:clefable:	:snorlax:
:electrode:	:mew:	:suicune:	:dusclops:	:registeel:	:doublade:	:clefable:

Slowking

:slowking:	:slowking:	:slowking:	:slowking:	:slowking:	:slowking:	:slowking:	:meloetta:
:donphan:	:steelix:	:celebi:	:carbink:	:diancie:	:dhelmise:	:toxapex:	:slowking:

Entei

:entei:	:entei:	:dragonite:	:jirachi:	:magnezone:
:tangrowth:	:meloetta-pirouette:	:entei:	:entei:	:entei:

Genesect

:genesect:	:genesect:	:tangrowth:	:necrozma:
:garchomp:	:meloetta-pirouette:	:genesect:	:genesect:

Tangrowth

:tangrowth:	:tangrowth:	:tangrowth:	:snorlax:	:entei:	:jirachi:
:garchomp:	:meloetta-pirouette:	:genesect:	:tangrowth:	:tangrowth:	:tangrowth:

Cheninphox

A-

Slowbro

:slowbro:	:slowbro:	:slowbro:	:slowbro:	:slowbro:	:slowbro:	:meloetta:
:donphan:	:steelix:	:doublade:	:carbink:	:diancie:	:toxapex:	:slowbro:

Snorlax

:snorlax:	:snorlax:	:snorlax:	:snorlax:
:clefable:	:xatu:	:gliscor:	:tangrowth:

Dragonite

:dragonite:	:dragonite:	:ursaring:	:sylveon:
:ursaring:	:entei:	:dragonite:	:dragonite:

Ursaring

:ursaring:	:ursaring:	:ursaring:	:dragonite:
:dragonite:	:garchomp:	:meloetta-pirouette:	:ursaring:

Porygon-Z

:porygon-z:	:porygon-z:	:porygon-z:
:gardevoir:	:mismagius:	:whimsicott:

Doublade

:slowbro:	:clefable:	:jirachi:	:hydreigon:
:doublade:	:doublade:	:doublade:	:doublade:

Jirachi

:jirachi:	:jirachi:	:jirachi:	:jirachi:	:jirachi:	:jirachi:
:entei:	:salamence:	:tangrowth:	:hawlucha:	:doublade:	:toxapex:

Toxapex

:toxapex:	:vaporeon:	:slowking:	:suicune:	:jirachi:	:togekiss:	:drifblim:	:kyurem:
:tyranitar:	:toxapex:	:toxapex:	:toxapex:	:toxapex:	:toxapex:	:toxapex:	:toxapex:

Crawdaunt

:crawdaunt:	:crawdaunt:	:metagross:
:garchomp:	:meloetta-pirouette:	:crawdaunt:

B+

Alakazam

:alakazam:

:electrode:

Gengar

:gengar:	:gengar:	:gengar:	:gengar:	:hydreigon:
:nidoking:	:jolteon:	:whimsicott:	:greninja:	:gengar:

Moltres

:moltres:	:registeel:
:nidoking:	:moltres:

Xatu

:xatu:	:rhydon:	:snorlax:	:suicune:	:registeel:	:kyurem:
:diancie:	:xatu:	:xatu:	:xatu:	:xatu:	:xatu:

Garchomp

:crawdaunt:	:tangrowth:	:ferrothorn:
:garchomp:	:garchomp:	:garchomp:

Aegislash

:clefable:	:umbreon:
:aegislash:	:aegislash:

Drifblim

:drifblim:	:drifblim:	:drifblim:
:krookodile:	:diancie:	:toxapex:

Cofagrigus

:umbreon:	:togekiss:	:hydreigon:	:kyurem:
:cofagrigus:	:cofagrigus:	:cofagrigus:	:cofagrigus:

Registeel

:registeel:	:registeel:	:registeel:	:registeel:	:clefable:
:moltres:	:xatu:	:celebi:	:hydreigon:	:registeel:

Greninja

:greninja:	:greninja:	:gengar:	:hydreigon:	:kyurem:	:necrozma:
:meloetta-pirouette:	:necrozma:	:greninja:	:greninja:	:greninja:	:greninja:

Diancie

:slowbro:	:slowking:	:latias:	:drifblim:	:kyurem:
:diancie:	:diancie:	:diancie:	:diancie:	:diancie:

B

Espeon

:espeon:	:espeon:	:porygon2:	:togekiss:	:kyurem:
:latias:	:latios:	:espeon:	:espeon:	:espeon:

Mismagius

:jirachi:	:porygon-z:
:mismagius:	:mismagius:

Porygon2

:porygon2:	:porygon2:	:clefable:	:sylveon:
:espeon:	:carbink:	:porygon2:	:porygon2:

Suicune

:suicune:	:suicune:	:suicune:	:clefable:
:xatu:	:gliscor:	:toxapex:	:suicune:

Celebi

:clefable:	:slowking:	:registeel:
:celebi:	:celebi:	:celebi:

Dusclops

:clefable:	:jirachi:	:hydreigon:
:dusclops:	:dusclops:	:dusclops:

Togekiss

:togekiss:	:togekiss:	:togekiss:
:nidoking:	:electrode:	:toxapex:

Sylveon

:sylveon:	:porygon2:
:dragonite:	:sylveon:

Latias

:latias:	:latias:	:espeon:
:probopass:	:diancie:	:latias:

Latios

:latios:	:latios:	:espeon:
:probopass:	:genesect:	:latios:

Chandelure

:chandelure:	:chandelure:	:chandelure:
:electrode:	:nidoking:	:greninja:

Hydreigon

:hydreigon:	:hydreigon:	:hydreigon:	:hydreigon:	:hydreigon:	:hydreigon:	:hydreigon:	:registeel:
:nidoking:	:dragonite:	:dusclops:	:yanmega:	:cofagrigus:	:meloetta-pirouette:	:doublade:	:hydreigon:

Kyurem

:kyurem:	:kyurem:	:kyurem:	:kyurem:	:kyurem:	:kyurem:
:xatu:	:espeon:	:suicune:	:carbink:	:diancie:	:toxapex:

Meloetta

:meloetta:	:meloetta:	:meloetta:
:clefable:	:slowbro:	:slowking:

Carbink

:slowbro:	:slowking:	:kyurem:
:carbink:	:carbink:	:carbink:

B-

Sandslash

:sandslash:	:sandslash:
:haxorus:	:meloetta-pirouette:

Vaporeon

:vaporeon:	:vaporeon:
:tangrowth:	:toxapex:

Mew

:mew:	:clefable:
:hawlucha:	:mew:

Donphan

:slowbro:	:slowking:
:donphan:	:donphan:

Smeargle

:smeargle:	:smeargle:
:sableye:	:hawlucha:

Probopass

:clefable:	:latias:	:latios:
:probopass:	:probopass:	:probopass:

Magnezone

:magnezone:	:magnezone:
:entei:	:volcarona:

Breloom

:snorlax:	:mamoswine:
:breloom:	:breloom:

Ferrothorn

:ferrothorn:	:ferrothorn:	:jirachi:
:tangrowth:	:garchomp:	:ferrothorn:

Necrozma

:necrozma:	:necrozma:	:necrozma:	:necrozma:	:necrozma:	:greninja:
:garchomp:	:porygon-z:	:meloetta-pirouette:	:genesect:	:greninja:	:necrozma:

Golisopod

:crawdaunt:	:yanmega:	:gliscor:
:golisopod:	:golisopod:	:golisopod:

C

:blastoise:
:Tentacruel:
:jolteon:
:zapdos:
:Lanturn:
:Quagsire:
:Umbreon:
:Steelix:
:Skarmory:
:Raikou:
:Tyranitar:
:Metagross:
:Flygon:
:salamence:
:krookodile:
:volcarona:
:dhelmise:
:cresselia:
:torkoal:
:linoone:
:dragalge:
:gastrodon:

D

:electrode:
:weezing:
Zapmolcuno
:typhlosion:
:ampharos:
:ferrothorn:
:weavile:
:zoroark:
:roserade:
:whimsicott:
:galvantula:
:pyukumuku:
:slurpuff:
:sableye:
:bruxish:
:swellow:
:swoobat:

Sample Teams

Priority Spam HO by anaconja

Triple Choice BO by anaconja

The Brave Lion by Aevilok

CrawZam Voltturn by Renownedsun

Enetta Genking Balance by Boshigoat

 

[presi]

Name of Mod: Perfect Vision

Link to Changes: Perfect Vision Master doc

Summary of the Mod: A format where people can submit "visions" of what their "perfect" metagame would look like to the tier leader, with each entry of a vision lasting two months. The goal is to completely make a Vision perfect over time with each revision.

Competitive Overview: Each vision is meant to be approachable with a small meta size. Each Vision besides A tests out interesting themes such as Weather/Terrain wars or spins on already existing concepts like NFE, Z-Moves and Captains for a tailor-made experience.

Current format: The current format is I1! a national dex restricted metagame. Meaning teams have the option of choosing one of the 9 captains to be on the team. Captains are meant to be above average pokémon that provide multiple unique traits to enable specific strategies & gameplans. With the benefit being how you best use these inherent traits and enable your captain!

ALL Resources for current & past formats can be found in the master doc which contain things such as sample teams, speed tiers, role compendiums & more!

Current Meta Resource Link
Discord link