
King of Fools Overhaul
King of Fools Overhaul is an early‑alpha Fabric mod that adds a growing set of classic‑tech progression features, starting with tin, raw tin, and their blocks. The long‑term goal is to slowly rebuild that classic Tekkit feel one update at a time. V0.00.06
0.00.04
Compatibility
Changes
Changelog
0.00.04 - 2026-03-03
Added
- Digger feature for tagged soft materials + tagged tools.
- Connected block harvesting (BFS) for secondary soft materials (coarse dirt, rooted dirt, gravel, soul soil, clay, mud, muddy mangrove roots).
- Tag system for Digger:
kofo:digger_blocksfor blocks,kofo:digger_toolsfor tools. - Digger excludes primary materials (dirt, grass block, sand) to prevent interference with normal gameplay, but includes gravel for its annoying falling behavior. Also excludes podzol, mycelium, red sand, and soul sand for now.
- Digger disables batch-breaking when crouching, allowing single-block harvesting for tool conservation.
- Template files for Digger block tags and tool tags in the modding kit.
- DIGGER.md integration guide in the modding kit.
Changed
- Miner now targets additional secondary stone types: diorite, andesite, granite, tuff, calcite, dripstone block, basalt, smooth basalt, and blackstone, making mining cleaner without interfering with normal terrain mining.
- Miner now disables batch-breaking when crouching/sneaking, allowing players to do single-block breaks when they need to conserve tools.
Fixed
- Miner now uses 6-connected neighbor spreading (face-adjacent only) instead of 26-connected (including diagonals), providing more natural vein spreading through deposits.
0.00.03 - 2026-03-03
Added
- Miner feature for tagged blocks + tagged tools.
- Connected block harvesting (BFS) for blocks of the same type (up to 256 blocks).
- Tag system for Miner:
kofo:miner_blocksfor blocks,kofo:miner_toolsfor tools. - Default support for all vanilla ores (coal, iron, copper, gold, diamond, emerald, lapis, redstone, nether gold, nether quartz, ancient debris).
- Miner respects all enchantments (Fortune, Silk Touch) and applies full durability costs.
- Template files for Miner block tags and tool tags in the modding kit.
- Feature-specific integration guides: FELLER.md, MINER.md, LEAVES.md for improved documentation organization.
Changed
- Modding kit README restructured as an index linking to per-feature guides.
- Documentation now organized by feature instead of single monolithic file.
0.00.02 - 2026-03-03
Added
- Automatic export of a KoFO modding kit folder to
Documents/King of Fools Overhaulwhen missing. - Exported
README.mdplus feature templates intemplates/for external integration work. - Template files for Feller block tags, Feller tool tags, and leaf compatibility requirements.
- Custom title screen branding: bottom-left version text now displays "King of Fools Overhaul" with the mod version.
Changed
- Startup documentation export now targets a dedicated folder structure instead of a single top-level markdown file.
- Export logic is non-destructive: existing user files are preserved and only missing files are created.
0.00.01 - 2026-03-03
Added
- Feller feature for tagged logs + tagged tools.
- Connected-log harvesting (BFS) with wood-group matching to avoid mixing unrelated tree types.
- Recursion guard to prevent re-trigger loops while the feller batch is breaking blocks.
- Global leaf behavior mixin: unsupported non-persistent leaves now decay deterministically using vanilla support state (
distance == 7), instead of waiting on random decay chance.
Changed
- Fabric Loader compatibility floor set to
>=0.15.0. - Tag folder layout aligned to modern format (
data/.../tags/blockanddata/.../tags/item). - Feller now handles block break + durability behavior without any custom decay logic in Feller itself.
Fixed
- Corrected malformed feller log tag JSON.
- Fixed recursion protection so all queued logs are guarded during batch break.
Feature Notes
Feller (what it does)
- Trigger: player breaks a block in
kofo:feller_logswith a tool inkofo:feller_tools. - Behavior: gathers connected valid logs (up to internal cap), breaks them in one batch, applies normal drops/events, and damages tool (unless creative).
- Scope control: wood-group normalization keeps feller from crossing into different tree families.
Leaf Decay Override (what it does)
- Not tied to Feller events.
- Applies through a
LeavesBlockmixin. - Uses vanilla-style support state (
persistent+distance) but removes the random wait for unsupported natural leaves.
Miner (what it does)
- Trigger: player breaks a block in
kofo:miner_blockswith a tool inkofo:miner_tools. - Behavior: gathers all connected blocks of the same type (up to 256 blocks), breaks them in one batch, applies normal drops/events, and damages tool for each block (unless creative).
- Scope control: only breaks blocks of the exact same type (e.g., coal ore only breaks connected coal ore).
- Sneaking: when crouching, Miner disables batch-breaking to allow single-block harvesting for tool conservation.
- Enchantments: respects Fortune, Silk Touch, and other enchantments on all blocks broken.
Digger (what it does)
- Trigger: player breaks a block in
kofo:digger_blockswith a tool inkofo:digger_tools. - Behavior: gathers all connected blocks of the same type (up to 256 blocks), breaks them in one batch, applies normal drops/events, and damages tool for each block (unless creative).
- Scope control: only breaks blocks of the exact same type (e.g., coarse dirt only breaks connected coarse dirt).
- Sneaking: when crouching, Digger disables batch-breaking to allow single-block harvesting for tool conservation.
- Excluded materials: dirt, grass block, sand, gravel, podzol, mycelium, red sand, and soul sand are intentionally excluded to prevent interference with normal gameplay and special behaviors.
- Enchantments: respects Efficiency, Silk Touch, and other enchantments on all blocks broken.
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:rMk3Zuvp:SyWe2zeg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rMk3Zuvp:SyWe2zeg"
}
