Tags
Creators
Details
Licensed CC-BY-NC-ND-4.0
Published last year
Updated 3 weeks ago
All versions
0.6.1
Beta
LumyMon 0.6.15 months ago 12.2K
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Required content
Changes
LumyMon 0.6.1
🗝️ Improvements & Fixes
- Structure Localization: The Secret Key and Turbine Key now correctly locate the corresponding Team Galactic structures (Eterna Building and Wind Plant)
- Map Icons: Fixed the Split Decision Temple icon not appearing on maps
🍰 New Feature: Data-Driven Poké Snack Blacklist
We’ve implemented an advanced filtering system for Pokémon spawned via Poké Snacks to ensure better balance within the COBBLEVERSE and its unique mechanics.
- Dynamic Blacklist: You can now block specific Pokémon from being spawned by Poké Snacks. By default, the "custom" blacklist is enabled, featuring all Pokémon that already have unique obtaining methods (altars, structures, or special mechanics) within COBBLEVERSE. This encourages players to engage with our custom adventure!
- Ready-to-use Modules: Four additional blacklist categories are included and can be easily toggled via the configuration file (
lumymon.json):legendary(All Legendaries)mythical(Mythical Pokémon)paradox(Paradox Pokémon)ultrabeast(Ultra Beasts)
- Total Customization: The system is entirely data-driven. You can create your own
.jsonfiles or modify the existing ones. Simply place a list of Pokémon in a datapack at:data/lumymon/poke_snack_blacklist/your_file.jsonand add the filename to theblacklistedPokeSnackSpawnslist in your config. - Master Switch: Don't want any restrictions? You can easily disable the entire system at once by setting
enablePokeSnackBlacklisttofalsein the config file
Optional dependencies
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:QAX8WiBc:SdTHrNvX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QAX8WiBc:SdTHrNvX"
}



