Tags
Creators
Details
Licensed ARR
Published 5 months ago
Updated 2 weeks ago
All versions
0.1.1
Release
OmiCraft 0.1.1 - for 26.1+2 weeks ago 24
Compatibility
Minecraft: Java Edition
26.1.x
Platforms
Paper
Purpur
Spigot
Changes
Changelog
All notable changes to OmniCraft are documented here.
[Unreleased]
Added
- Added
/oc autocraft-plan <category:recipe> [amount]to preview recursive AutoCraft steps without consuming resources or creating a queue. - Added deterministic validation for invalid AutoCraft targets, sources, outputs, and ingredient amounts.
- Added regression coverage for output-capacity reservation, AutoCraft planning, and player lock cleanup.
Changed
- Category permissions now use the configured category node when present; blank or absent category permissions fall back to
omnicraft.use. - Craft transactions and AutoCraft nodes revalidate base, category, and AutoCraft permissions before committing work.
- Player GUI filters, favorites, delete mode, click throttles, and active craft state are cleared when a player leaves.
- Paper 26 metadata now declares the AutoCraft permission and AuraSkills soft dependency consistently with the legacy module.
- Removed the unused
anti-dupe.lock-timeout-msconfiguration option.
Fixed
- Output-capacity checks no longer reserve critical, byproduct, or quality stacks when their configured chance is zero.
- Category and recipe file operations now stay inside the configured data directories.
- Recipe archive imports reject unsafe archive paths and zip entries.
- Stale GUI interactions are rejected after permission changes.
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:rnYvADwE:usAmPCHp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rnYvADwE:usAmPCHp"
}

