Tags
Creators
Details
All versions
v3.3.0
Release
AllTheMons x Mega Showdown [v3.3.0]8 months ago 54.6K
Compatibility
Minecraft: Java Edition
1.21.1
Platforms
Data Pack
Resource Pack
Changes
Changelog v3.3.0
Compatible with Mega Showdown v1.6.9+
Removed all "Fanon" content and moved them over to Lost Lore
- ATM x MSD is meant to fill your pokedex and provide a Pokémon experience similar to Mega Showdown - Based on the games and official canon. Which is why I decided to move everything that isn't quite accurate to the mainline games to my side addon in v2.0 (which will release shortly after this)
- Lost Lore will introduce all these Pokémon and Items in a mod format - meaning you will have all of them in creative, visible in JEI/REI/EMI, they will be translatable and won't break with every second update xD
- Removed Primal Dialga, Meta Groudon, Spiky-Eared Pichu, Mega Galarian Slowbro, Shadow Lugia, Shadow Mega Mewtwo Y/X, Riolu/Lucario/Incineroar Costumes, all custom items linked to any of these mons such as Ancient Light Ball, Red/Green Scarf, Costume Boxes, Corrupted Wish, Binding Armor, Shadow Energy, Shadow Mewtwonite X/Y, Time Gear, as well as cosmetics like Pledge Fragment & Water Shuriken
- The Armored/Shadow Mewtwo models will stay in this addon because I am not allowed to port them over and the new Lost Lore model isn't ready yet. They will be unobtainable without Lost Lore tho!
New Mons & Remodels!
- Wo-Chien has been added (fully animated and rideable)
- Updated the Xerneas model & animations
- Updated the Celebi model & animations
Miscellaneous & backend changes:
- Removed a few leftover files from old versions
- Fixed Ho-Oh's floral biome spawn location
- Fixed Zarude not having any drops
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:odZZdRCE:JkoWi39g"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:odZZdRCE:JkoWi39g"
}

