1.20.1-5.0
Compatibility
Required content
Changes
Fixes:
-fixed darklizzardmon display name
-fixed mochimon couldn't evolve to tentomon
-fixed sunarizamon not spawning
-fixed evo conditions saying "joyfull"
-transition between attack animations made smoother and not look laggy
-fixed Yarmon being called Keemon
New Stuff:
-digimon evolutions and evolution conditions are now stored in jsons, they can be edited on data packs!
-digimon deal their level value as damage to non digimon entities
-digimon will randomly express mood
-ultimate digimon!!!
-digivice gui tamer commands
-attack command
-sit command
-stand up command
-fly command
-feeding command
-added digimon professions
-added storage profession
-added some sound effects
-non digimon mobs give xp now
-added Digimon Card
-added Blue Card
-added new training good m2 disk
Changes:
-champion evos require more specific data
-digivice gui can be opened without having to interact with digimon
-evolution conditions in the digivice gui show the name of the evo
-evo conditions name gets green if meeting evo requirements
-defeating higher level digimon counts as win too
-flying digimon tilt a bit to the front while flying
-move particles create in a spherical pattern rather than a disc pattern
-data/xp is directly gained by digimon defeating other digimon
-data/xp items are now admin items, thus can only be accessed in creative
-digimon can attack players to balance fights as now the attack command exists
-move items get consumed now
-digimon gain more stats through training
-high tier training goods rarely spawn in the wild
-changed damage function to allow for longer battles
-all high tier goods changed
Digimon:
-gabumon added
-drimogemon added
-garurumon added
-garurumon black added
-mamemon added
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:YEZBvWbe:xrzWBdQB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YEZBvWbe:xrzWBdQB"
}

