Links
Tags
Creators
Details
Licensed CC-BY-NC-SA-4.0
Published 5 months ago
Updated last month
All versions
0.10.4
Release
0.10.4 NeoForgelast month 43
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.11
Platform
NeoForge
Supported environments
Client-side
Changes
Fixed
- Mod contents were missing from the release jars. Shared code (crosshair renderer, config) lived only on the compile classpath and was never packaged into the final jar, so previous builds shipped as near-empty archives and the mod had no effect in game. Both loader jars now bundle the shared module.
- Fabric client failed to launch. The mod resolved an outdated Mixin runtime (
sponge-mixin 0.16.5) that is incompatible with Fabric Loader 0.19.3, causing aNoClassDefFoundErroronorg.spongepowered.asm.service.IAdviceProviderduring startup. The Mixin version now matches what the loader expects. - Fabric entrypoint pointed to a non-existent class, which prevented the mod from initializing.
- The crosshair never rendered on NeoForge. The Mixin configuration was not registered in the mod metadata, so the renderer was never applied.
- Potential dedicated server crash. A client-only Mixin target was declared in the common Mixin list. It is now correctly scoped to the client.
- Exceptions during crosshair rendering were silently discarded, hiding real errors. Failures now surface normally.
- Reported mod version was inconsistent. The jar filename and the in-game version did not match. The version is now defined in one place and injected into both loaders' metadata.
- Corrected the NeoForge startup log, which incorrectly reported the mod as running on Fabric.
Added
- Configuration file at
configvnnhattruongneeecrosshairaddons.jsonwith three optionsenabled- master switch; when disabled the vanilla crosshair is usedcrosshairSize- rendered crosshair size in pixels (4-64)highlightOnReach- toggle the red crosshair shown when a player is within attack range
- In-game settings screen built with Cloth Config, accessible through Mod Menu on Fabric and through the Config button in the mod list on NeoForge. Changes are saved to disk immediately.
- Invalid or corrupted config files now fall back to defaults instead of crashing.
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:6srV1idy:kVroGULY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6srV1idy:kVroGULY"
}

