Links
Tags
Creators
Details
Licensed MIT
Published 7 months ago
Updated 7 months ago
All versions
1.1.2
Release
Simple Smith 1.1.27 months ago 26
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Simple Smith v1.1.2 - Configuration & Compatibility Update
This update introduces a robust scaling system for finer balance control and refactors the internal logic to allow for optional compatibility with external mods.
⚙️ Enhanced Configuration
- Failed Quality Customization: The "Failed" quality is no longer hardcoded. You can now define the exact penalty range using the
failedMinandfailedMaxconfig values. - Global Scale Settings: New scaling factors have been added to the config, allowing you to independently tune how quality affects different stats without changing the base multipliers.
- Applied Stats: Attack Damage, Armor, Armor Toughness, Mining Speed, and Gem Potency.
- Logic: The bonus is calculated as: Bonus = (Quality Multiplier - 1.0) * Global Scale
- Expanded Multiplier Limits: The maximum allowable quality multiplier has been increased from 10.0 to 100.0 to support high-power gameplay configurations.
🔌 Optional Apotheosis Integration
- Decoupled Dependency: Simple Smith no longer requires Apotheosis to run. The mod will now operate perfectly as a standalone experience.
- Dynamic Feature Activation: If Apotheosis is detected, the following features are automatically enabled:
- Socket Bonuses: Specific qualities (Legendary/Excellent) provide additional item sockets.
- Gem Potency Scaling: Gem attributes are dynamically amplified based on the item's quality and the
gemEffectScaleconfig.
- Tooltip Synchronization: Tooltips now accurately reflect the final amplified values, ensuring players see the exact bonuses they are receiving.
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:s3q2NAYa:lxUSlRn0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:s3q2NAYa:lxUSlRn0"
}