Tags
Creators
Details
1.1.3
Compatibility
Required content
Changes
Create Harmonics 1.1.3
Features
-
Neoforge port
-
Live streams are now directly supported
-
Record Players muffle audio when exposed to a liquid, depending on its viscosity, this works both for static players and for dynamic ones (both on contraptions and Valkyrien Skies ships)
-
Added a loot table for end cities for Ethereal Base Records @Robin
-
Enhanced how the record press base works
-
Direct http urls are supported (so custom links and CDNs work)
-
Now mechanical arms will dance less often
-
Display links now offer the following modes for displaying song names: full title, scroll and wrap mode.
-
Display links can now show the record player state, including if it is looping or not.
-
Added a Reverberator effect, which can be activated by placing some specific blocks around a record player, and modulated with other blocks (see in ponder)
-
Added tooltips for ethereal records showing which effects they have
-
Now audio effects (like the stone moving, villager etc) are affected by other effects down the chain, including external ones (liquid muffling and reverberator)
-
Released the official translator tool for the mod Create Harmonics – Translation Helper
Translations
- Russian translation by @J0phie
- German translation by @PowerMilian
Bug fixes
-
Fixed some performance issues and completely reworked the audio player, with a brand new synchronization logic
-
Adjusted buttons placement conditions for the library management gui
-
Now the pitch shift effect is more precise
-
The sliding stone effect now properly loops
-
Big performance enhancements with record players on contraptions and effect chains
-
Finally fixed AO for the Andesite Jukebox
-
Fixed duplicate ethereal record display on the creative mod tab
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:uWn64pD9:ezHTCu0C"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uWn64pD9:ezHTCu0C"
}

