Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published 5 months ago
Updated 2 months ago
All versions
1.0.1
Release
Dragon Care - 1.0.15 months ago 25
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
English Changelog (click to expand)
DragonCare — Hotfix 1.0.1
Sound System Stabilization & Crash Fix
Fixed
- Client Crash on Startup: Resolved a critical issue (
No ALCapabilities instance has been set) where raw OpenAL buffer initialization for the geiger track ran before Minecraft's sound engine finished loading asynchronously or if no audio devices were connected. - Resource Reload Crash (F3+T): Fixed a crash that occurred when reloading resource packs or changing audio output devices, which invalidated active OpenAL buffers and source IDs.
Changes
- Added an safety guard
isOpenALReady()usingAL.getCapabilities()to prevent early execution of raw OpenAL calls. - Subscribed to
SoundEngineLoadEventto automatically reset and recreate sound buffers safely whenever the game's audio engine is reloaded.
Русский список изменений (нажмите, чтобы раскрыть)
DragonCare — Хотфикс 1.0.1
Стабилизация звуковой системы и исправление крашей
Исправлено
- Краш клиента при запуске: Исправлена критическая ошибка (
No ALCapabilities instance has been set), возникавшая при попытке инициализации низкоуровневых OpenAL-буферов счетчика Гейгера до полной загрузки звукового движка игры или при отсутствии аудиоустройств. - Краш при перезагрузке ресурсов (F3+T): Устранено падение клиента при перезапуске ресурсов или смене аудиовыхода, которое приводило к инвалидации используемых OpenAL источников и буферов.
Изменения
- Добавлена безопасная проверка
isOpenALReady()черезAL.getCapabilities(), предотвращающая преждевременный вызов низкоуровневых функций OpenAL. - Интегрирована подписка на событие
SoundEngineLoadEventдля бесшовного сброса и безопасного пересоздания звуковых буферов при перезагрузке аудио-движка игры.
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:Hlm7REws:T7TDnSVM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Hlm7REws:T7TDnSVM"
}

