1.3-SNAPSHOT
Compatibility
Changes
This version adds a few commands, which should under no circumstance be given to anyone not 100% trusted.
The commands are /mmtell <player> "message", which sends an unsanitized minimessage to the player.
/createdupe <player> <slot>, which creates a duplicate pokemon, with the same uuid as the original, this is for testing purposes, like when using the finddupe command.
Lastly, and possibly most importantly, this version also adds a trade event hook, which checks if the players have any duplicate pokemon based on uuids, to address duplication glitches tied to held items. To solve the issue, the pokemon is simply removed from one of the player's party/pc. The mod also makes sure to log the pokemon properties in case you need to see what was deleted as well.
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:zJhFyT9U:ZS4XPu9C"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zJhFyT9U:ZS4XPu9C"
}

