Links
Tags
Creators
Details
1.2.0
Compatibility
Changes
SPRA — Weekly Update | Can You Hear Me Now?
This update substantially improves Aeronautics propeller acoustics and lays the foundation for believable sound transmission through rooms, doors, windows, hulls, and exterior openings. I am prematurely releasing this in alpha state. I believe it is in a good but not great state. I appreciate everyone's help in identifying bugs. Almost all of them are address but this release probably comes with new ones. development must pause for a few days while I deal with a family issue*
Highlights
- Added a new multipath audio system with directional aperture, portal, and edge-diffraction sound arrivals.
- Added collision-shape-aware routing through open doors, trapdoors, gates, slabs, panes, and other partial blocks.
- Improved acoustic routing across moving and rotated Sable sublevels.
- Added interior connected-air transport for sound passing through doors and openings without requiring outdoor exposure.
- Improved propeller occlusion, large-emitter classification, route power allocation, and energy conservation.
- Improved route-search performance, fairness, caching, and diagnostic accuracy.
- Fixed non-strict occlusion ray behavior. (thank you Succubyte)
- Fixed underwater filtering being triggered by underwater sources instead of the listener. (thank you brauzer666)
- Excluded weather from acoustic and Doppler processing. (thank you Dinonator123)
- Updated and hardened optional Distant Horizons terrain-occlusion integration.
- Added an optional (on by default) amplified Aeronautics propeller resource pack. (thank you WhoTfTookAaxel)
- Fixed Simple Voice Chat integration (thank you V3RYM3GAFUN)
- Removed herobrine
Portal transition polish remains an active area of development. A recent presentation-continuity experiment was reverted after it performed worse in testing. Walking through portals may not be fabulous in every conceivable situation, but we will get there together! Config migration should work but if you find issues, the first thing to try is probably deleting your configs and letting them regenerate.
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:JHKPj7kB:bCFn9jyV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JHKPj7kB:bCFn9jyV"
}

