Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 9 months ago
Updated yesterday
All versions
1.3.22+26.2
Release
IG: Ore Amplifier 1.3.22+26.2yesterday 12
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client-side
Server-side
Required content
Any compatible version
Any compatible version
Changes
Added
- 5-Pillar Testing & Runtime Verification Harness ([BL-OA-003]): Implemented comprehensive testing suite satisfying studio verification standards:
- Pillar 1 (
OreAmplifierStressFuzzTest): 20,000 deterministic chaos property fuzzing iterations verifyinggetAmplifiedCountbounds, non-negative saturation, and static blacklist heuristics. - Pillar 2 (
OreAmplifierConcurrencyLoadTest): 50 virtual worker threads executing 20,000 operations verifying deadlock-free concurrency, lock-free config safety, and zeroConcurrentModificationException. - Pillar 3 (
OreAmplifierCommandTest): Headless Brigadier AST hierarchy assertions, Gamemaster level 2 permission gating, static GameRule handles, and conventional tag keys. - Pillar 4 (
OreAmplifierGameTest): Headless state simulation validatingBuiltInRegistries.BLOCKore identification, Monte Carlo stochastic multiplier convergence, and sparse delta config pruning. - Pillar 5 (
OreAmplifierSidednessContractTest): Sidedness isolation asserting 0 client package references in common code/bytecode and verifying single-line GPLv3 license headers across all source files.
- Pillar 1 (
Fixed
- Saturated Arithmetic Guard: Enforced integer saturation in
OreLogic.getAmplifiedCount, preventing 32-bit signed integer wrap-around on extreme count/multiplier inputs adhering to the Freedom Over Anti-Crash policy. - Config Concurrency Thread-Safety: Converted
OreAmplifierConfig.perOreMultipliersto thread-safeConcurrentHashMapwith synchronized mutation/pruning guards.
Links & Resources:
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:dKnhF0GD:DoZdv5yu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dKnhF0GD:DoZdv5yu"
}

