1.0.0
Compatibility
Changes
Key Features:
Phantom Taming & Classes:
Tame phantoms using Glistering Melon Slices.
Specialize your pet phantoms into 4 distinct classes using specific items: Wither Skeleton Skull, Chorus Fruit, Enchanted Golden Apple, and a Shield (upgradable with a Netherite Ingot).
Use a special Horn to store and carry tamed phantoms directly in your inventory.
End Corruption & Defense:
Ender Pilgrim: Corrupts the surrounding terrain into End Stone and spawns aggressive Endermites every 90 seconds. These Endermites inflict a dangerous "End Sickness" effect. Defeating the Pilgrim gives a chance to drop its mask.
Purification Flower: Cleanses corrupted End Stone back to normal terrain and repels nearby Endermites.
Bosses & Lore:
Herobrine's Altar: Summons a mysterious entity that silently observes your world.
Phantom Titan: A massive final boss battle located in The End.
Unique Boss Loot: Drops special Elytra with a 50% chance to negate incoming damage, and a Protective Horn that creates an aura blocking all projectiles.
World Generation & Mobs:
3 New Structures to discover and explore during your adventures.
Wild phantoms now have a chance to spawn with status effects (similar to spiders): Strength, Speed, or Invisibility.
Enchantments & Tool Buffs:
Midas Touch: A new enchantment that grants a chance to convert mob drops into gold.
Golden Tools: Buffed with a 25% chance to not lose durability and a 20% chance to yield double resources.
Netherite Tools: Granted a 10% chance to yield double resources.
Localization:
Fully translated into English and Russian.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| phantomtamer-1.1.0.jar | Unknown | 331.03 KiB |
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:CAnHaB7F:DKd4G5Jc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:CAnHaB7F:DKd4G5Jc"
}

