
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.6
Compatibility
Changes
LogicCraft v1.6 — CarryOn Ownership & Mob Transfer Fix
This update focuses on stopping “CarryOn theft” and fixing mob pickup rules, while keeping village/structure mobs and blocks movable as usual.
✅ Changes / Improvements
🔒 Ownership Protection (Anti-Theft)
- Player-placed carryable blocks (chests, barrels, furnaces, shulkers, etc.) now store an owner.
- By default, only the owner can move their carryable blocks.
- Owners can grant access to other players using:
/lc add <player>— allow this player to move your CarryOn-owned items/lc remove <player>— remove access/lc trusted— list your trusted players
- Village/structure blocks and mobs (no owner) remain movable by anyone, so normal gameplay is unchanged.
🐾 Mob Pickup Rules (Fixed)
carry_on.mobs.allowed_entitiesis now actually enforced (previously it could be ignored, allowing unintended mobs).- Still respects:
disallow_hostiledisallow_bossesdisallow_leasheddisallow_with_passengers
🧠 Owner Detection for Mobs
- Tameable mobs (Wolf, Cat, etc.) use their vanilla owner.
- Bred animals are tagged to the breeder as owner to prevent stealing.
- If a mob has no owner (villages / natural mobs), it behaves like before: anyone can move it.
⌨️ Command Auto-Tab Complete
- Added tab completion support for:
/lc add/lc remove/lc trusted
- Player names autocomplete for
add/removeto make management quick.
🌍 Persistence
- Ownership + trusted lists are saved to:
plugins/LogicCraft/carry_on_ownership.yml
- Data persists after restarts/reloads.
🛡️ Admin Bypass Permission
- Admins can bypass ownership restrictions with:
logiccraft.carry_on.bypass
🗣️ Language Support
- New lang keys were added for ownership/trust messages (EN + ES supported).
Thanks for using LogicCraft! 💙
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:RzogWd7D"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DrCLi50H:RzogWd7D"
}
