Links
Tags
Creators
Details
2.0.0-BETA.164
Compatibility
Changes
Build 164 update
This release includes all changes from build 147 to build 164.
Fixed a camera conflict where FPV logic could force the camera back to the player during Shahed control.
Restored Shahed camera behavior to the stable flow used in build 146.
Added long range Shahed ghost rendering when normal entity tracking is lost.
Made ghost visuals match the real Shahed model rotation color launcher state and movement.
Increased Shahed render distance cap to 2000.
Increased Shahed client tracking range to 2000.
Added ghost position sync every 2 ticks for players within 10000 blocks.
Disabled Shahed forced chunk loading to reduce server memory usage.
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:NLOHh3Kg:NhfeRgtl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NLOHh3Kg:NhfeRgtl"
}

