Tags
Creators
Details
Licensed ARR
Published last month
Updated 2 days ago
All versions
1.2.1
Release
Kernel Panic 1.2.12 days ago 17
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Unavailable version
Changes
1.2.1
It had trouble finding somewhere to stand.
Changed
- In-game config screen, now with tabs: Visuals, Audio, and Spikes.
- Spike settings (frequency, build and strike length, spike type weights, no-entity fade, false alarms) can now be changed in-game no file editing. Available to anyone hosting the world: singleplayer, LAN, E4MC, Essential. No operator status needed.
- On servers, operators can use
/horrormod configto list settings,/horrormod config <setting>to view one, and/horrormod config <setting> <value>to change it. Regular players can't. - Changes apply from the next spike onward, not to one already in progress.
Fixed
- The Fragment could fail to spawn entirely in tunnels, caves, and enclosed spaces, leaving a full spike with nothing in it. It now searches a spread of nearby positions instead of giving up on the first blocked one.
- The Fragment no longer spawns in mid-air over ravines and chasms.
- If there's truly no room for the Fragment nearby, the spike no longer plays at all,
and
/horrormod spiketells you why instead of silently doing nothing. - A spike no longer cuts out early if the Fragment's chunk unloads (for example, sprinting away mid-build).
- Fixed a rare crash in the error-text overlay during the strike phase.
Notes
- Safe update from 1.2.0. No gameplay changes, existing worlds unaffected.
- Requires Forge 1.20.1 and GeckoLib 4.8.3.
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:RIt3uzdg:4OgzEM54"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RIt3uzdg:4OgzEM54"
}

