All versions
1.0.1+1.21.1
Release
Haunted Encounters v.1 NeoForge8 months ago 320
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Unavailable version
Changes
- Ghosts will now spawn in the Overworld, the Nether, and the End, with similar spawn mechanics as the hostile mobs they are based on. There are 7 types of Ghosts available:
- Forlorn Ghost: Zombie alternative, chases players to hit and deal damage.
- Spectral Ghost: Skeleton alternative, chases players to shoot Shadow Balls at them and deal damage.
- Flickering Ghost: Enderman alternative, neutral until attacked, upon which it turns hostile and very aggressive. Drops Ender Pearls.
- Volatile Ghost: Creeper alternative, chases players to explode when it gets near them. Drops Gunpowder.
- Wailing Ghost: Ghast alternative, shoots Fireballs at players from afar. Drops Ghast Tears.
- Pyrous Ghost: Blaze alternative, shoots a barrage of Small Fireballs at players from afar. Drops Blaze Rods.
- Galeful Ghost: Breeze alternative, shoots Wind Charges at players from afar. Drops Breeze Rods.
- Ghosts will hide from the sun during daytime.
- Ghosts can pass through walls when chasing a player.
- Ghosts are repelled when in the vicinity of a placed Cleanse Tag.
- Ghosts may attempt to run away when they their HP reaches a certain low threshold. They may also attempt to teleport nearby when engaging in combat with the player.
- When running away, Ghosts may attempt to possess a nearby Villager and turning it into a Zombie Villager.
- A new item Silph Scope can be crafted using Amethyst Shards, Iron Ingots, a Ghost Gem, and a Cleanse Tag. Using it on a Ghost will reveal the Ghost's true form: a random Ghost-Type Pokemon, which in turn can have a chance to possess the Restless Mark.
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:SHOk9B0j:39ZzSeKk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SHOk9B0j:39ZzSeKk"
}![Haunted Encounters v.1 [Fabric/NeoForge 1.21.1]](https://cdn.modrinth.com/data/SHOk9B0j/d496215024eb0cf39f68f8f6c41a874844e8d6bc.png)

