1.2.0
Compatibility
Changes
PsychoTerror 1.2.0 — Deep Psychological Audio & Ghosts
This update replaces the previous build with a fully stable and improved version of the plugin.
Several issues from the earlier release have been fixed, and the psychological horror mechanics
have been redesigned to be more intense, more atmospheric, and much less repetitive.
🔧 Fixes & Stability
- Fixed particle compatibility issues (SMOKE is now fully supported).
- Fixed ghost events not triggering consistently for some players.
- Corrected sound events that previously felt “soft” or non-threatening.
- Improved internal timers to avoid repetitive or predictable scares.
- General performance cleanup (lighter tasks, cleaner logic, faster event handling).
🔊 Reworked Sound System
- Removed melodic or friendly sounds from earlier builds.
- Added cave ambience, nether mood, and low Warden heartbeat for deeper tension.
- Added directional “swoop” audio for side-ghost appearances.
- Blackout events now mix thunder + heartbeat + horror ambience.
👻 Ghost & Blackout Improvements
- Side ghosts are now darker, faster, and more unpredictable.
- Blackout events include a front-facing ghost apparition unique to high insanity.
- Ghosts now use aggressive smoke particles without lag or visual bugs.
🧠 Psychological Horror Enhancements
- Scares are now rare but more powerful, following realistic tension pacing.
- Violence affects only the violent player: peaceful players remain unaffected.
- Insanity thresholds adjusted to create a smoother descent into madness.
This version focuses on deep psychological tension rather than repetitive effects.
Players who kill mobs will experience unique personal horror, while those who remain peaceful
will see nothing unusual.
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:TicgNrm0:9WRTBe8R"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:TicgNrm0:9WRTBe8R"
}

