0.0.1
Compatibility
Required content
Changes
With this mod you can change how many IVs comes with a specific value or allow you to change the probability to a specific pokemon spawns with a hidden ability or being shiny. Totally customized with a configurable file.
To find the species name, you will need to access the Cobblemon/AllTheMons github and look for the spawn_world_pool folder. Inside it are the spawn configuration files for the respective pokemon.
Look for the "pokemon" variable and copy the name that is assigned to this property.
Tip: For paradox pokemon with compound names, for example Iron Valiant, you need to leave the name with the space (iron valiant), otherwise it will not be recognized.
Path to pokemon spawn configuration:
Cobblemon 1.6.1:
common/src/main/resources/data/cobblemon/spawn_pool_world All The Mons 2.3 (for Cobblemon 1.6.1):
data/cobblemon/spawn_pool_world (for regular pokemon) data/legendary_spawns_atm/spawn_pool_world (for legendaries) data/paradox_spawns_atm/spawn_pool_world (for paradox) data/ultra_beast_spawns_atm/spawn_pool_world (for ultra beasts) To keep cobblemon's default configuration set ha_chance and shiny_chance to 0.
Example Configuration:
{ "paradox": { "iv_value": 31, "iv_quantity": 3, "shiny_chance": 0.20, "ha_chance": 0.25, "species_list": [ "iron valiant" ] }, "legendary": { "iv_value": 31, "iv_quantity": 5, "shiny_chance": 0.10, "ha_chance": 0.15, "species_list": [ "celebi" ] }, "ultrabeasts": { "iv_value": 31, "iv_quantity": 4, "shiny_chance": 0.15, "ha_chance": 0.20, "species_list": [ "xurkitree" ] }, "ditto": { "iv_value": 31, "iv_quantity": 2, "shiny_chance": 0.01, "ha_chance": 0.01, "species_list": [ "ditto" ] } } Requirements Cobblemon 1.6.1
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:P4wiRP9T:FwQY6lMj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:P4wiRP9T:FwQY6lMj"
}
