Links
Tags
Creators
Details
mc1.8.9-1.1.0-ornithe
Compatibility
Required content
Changes
1.1.0 Ornithe
Note
This version has no functional differences from 1.0.1 (Legacy Fabric). It only adds support for the OrnitheMC Loader. Players still using the Legacy Fabric loader with this mod version 1.0.1 do not need to port and update.
Changelog
- Added .gitattributes with line-ending rules and binary markers for Java/Gradle/mod assets.
- CI workflow now builds on Java 21 with Gradle setup action; dropped Java 17 matrix, wrapper validation, and artifact upload.
- Build system upgraded to Fabric Loom 1.11 with Ploceus; version string now includes MC version, dependencies switch to Ornithe feather mappings/OSL loader, and Gradle props updated (parallel build, loader/feather/OSL versions, mod v1.1.0); wrapper bumped to Gradle 9.2.1 with launcher script adjustments (gradlew, gradlew.bat).
- Maven repos retargeted to Ornithe releases/snapshots in settings.gradle.
- Client code ported to Ornithe APIs: keybinding registration now uses KeyBindingEvents/MinecraftClientEvents, barrier block/particle mixins updated to new method names/packages and behavior logging tweaked, and block model mixin renamed to BlockModelsMixin with updated injection target.
- Resource configs streamlined: fabric.mod.json drops dependency/suggests blocks and lvb.mixins.json now references BlockModelsMixin.
What's Changed
- Ornithe Port by @DaveyL2013 in https://github.com/metaconscious/legacy-visible-barrier/pull/1
New Contributors
- @DaveyL2013 made their first contribution in https://github.com/metaconscious/legacy-visible-barrier/pull/1
Full Changelog: https://github.com/metaconscious/legacy-visible-barrier/compare/v1.0.1...v1.1.0
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:FSLuAotK:GLbZfG3F"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:FSLuAotK:GLbZfG3F"
}

