1.3-SNAPSHOT
Compatibility
Changes
Bombaclat big changes
Added a pokemon filter to avoid selling wrong pokemon
This filter can be configured to not sell pokemon with certain aspects, like server skins etc. You should probably use this so players don't fuck up (this is common). It also has the filter options:
- ShiniesBPs which doesn't allow you to sell shinies or pokemon over 4x31.
- HighBst which doesn't allow you to sell pokemon over 500.
- UltraBeast
- Legendary
- Mythical
- Skins
- NoFilter (These are self explanatory, right?)
Added a sell all option which puts everything on the pc page into the sale cart. This works with the filter so it doesn't sell your good shit.
Oh, yeah I also added the option to name the GUI differently since that was requested. I'm not going to add the option to customize the GUI though since there's so many pokemon you're super limited nonetheless.
Lowkey might be other things but I forgot
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:MCWoGlXJ:xXSYrC8G"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MCWoGlXJ:xXSYrC8G"
}

