Tags
Creators
Details
Licensed MIT
Published 8 months ago
Updated 1 hour ago
All versions
1.2.0
Release
SpatialAudioSystem 1.2.01 hour ago 5
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
English
Major Changes
- Manta 2.94.0 (Manta 7.1) is bundled (jar-in-jar) — required range
[2.94.0,3). The CEF runtime that plays in-game videos (Chromium Embedded Framework 122) is now bundled in the jar and extracted to<game folder>/mcss-chrome-nativethe first time a video plays. Nothing is downloaded, and the jar contains no executable (.exe): CEF's child processes are started by the Java that runs the game (java.exe/javaw.exe), which loads the bundled DLLs — in Task Manager they appear as Java processes. The jar is now about 140 MB. Videos that need DRM (Widevine), and pop-up windows opened from links inside a video, do not open. Update TSU to 1.2.0 at the same time (it embeds the same Manta). - Chinese UI — zh_cn, with zh_hk / zh_tw converted from it.
Changed
- F1 hints read as natural Japanese, and what nine of them said was corrected against the code; English and Chinese say what the code does too.
- UI labels, playlist counts and tooltips are drawn with Manta's raster font. Scrollbar thumbs can be grabbed and dragged.
Added
- Wiki — a Videos page with the SAS guide (English, Japanese and Chinese).
Fixed
- The recording device's screen shows a picked or cleared file at once.
/clone ... movemoves a playback or recording device's contents instead of doubling them.- A memory device's medium keeps its length with its sound (on clear, and on a rewrite that cannot be timed).
- A late listener who has played a sound before hears it without a transfer.
- In the schedule popup, releasing a running quick-craft goes through.
Internal
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:4rsUhTWv:55FTOaWc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4rsUhTWv:55FTOaWc"
}

