1.0
Compatibility
Required content
Changes
Epic Fight – Palladium Compatibility Patch
This mod enables compatibility between ThreeTag’s Palladium and Epic Fight, allowing both to run together without crashes or major conflicts.
It lets you use Palladium based mods such as FSANG18’s Heropack and AlienEvo while Epic Fight is installed.
However, these mods will not automatically use Epic Fight’s combat animations. To avoid animation bugs or visual glitches, you must press R (by default) to switch Epic Fight into Mining Mode before using these mods.
Notes
- Armors from Palladium-related mods are not compatible with Epic Fight models. Their textures must be manually converted to Epic Fight’s format.
- I do not plan to handle armor conversions at this time, but may consider it if enough people request it.
- This patch was created for personal use, so bugs are expected.
- Report any issues or requests on GitHub: https://github.com/Exizal/EpicFight-Palladium-Compatibility/issues.
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:Lj9kZ79B:jeZHQXMv"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Lj9kZ79B:jeZHQXMv"
}

