
LogicCraft
LogicCraft adds “vanilla+” enhancements focused on immersion and quality of life: dynamic lighting with items, smarter sand/gravel physics, XP fusion, biome titles, oxygen bottles, cave tremors, ambient drips, quick campfire cooking, door synchronization,
Tags
Creators
Details
1.7
Compatibility
Changes
Important: Folia support is currently in a very early experimental stage. It is not yet 100% complete, and bugs, unexpected behavior, or compatibility issues may still occur. Please report any problems you encounter.
Carry On
- Fixed a serious item duplication exploit when carrying chests and other storage blocks.
- Container contents are now removed and restored atomically.
- Added safeguards to prevent scheduled restoration attempts from restoring the same inventory multiple times.
- Added safe rollback behavior if a carried block cannot be placed.
- Prevented carried mobs from taking attack damage when released with left-click.
- Improved mob releasing, positioning, velocity, and state restoration.
- Added support for empty and decorated Flower Pots.
- Removed Jukebox support because its special behavior caused positioning and visual issues.
- Improved cleanup when players disconnect, get kicked, or the plugin shuts down.
- Blocks, displays, players, and mobs are now processed within their corresponding Folia regions.
Ghost HUD
- Fixed HUD visibility and configuration handling.
- Improved crop and tool detection.
- Fixed action-bar cleanup when the module is disabled or a player disconnects.
Experimental Folia Support
- Added initial Folia compatibility.
- Replaced legacy Bukkit scheduler usage with Folia-compatible schedulers.
- Added thread-safe storage for shared module data.
- Added region ownership checks for dynamic lights, cave quakes, ambient effects, XP fusion, and Carry On.
- Paper compatibility is retained.
Folia support should currently be considered experimental and is not recommended for critical production servers without extensive testing.
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:DrCLi50H:TMR7lhP3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DrCLi50H:TMR7lhP3"
}
