Tags
Creators
Details
1.5.0-mc1.20.6
Compatibility
Changes
1. Overview
- Added support for Minecraft
26.3. - New commands:
/kib rule <ruleName> [<value>]/kib blacklist <interactable|reactive> <add|remove> <material>/kib help
- New permissions:
kib.rulekib.blacklistkib.admin
- Changed config.yml to use snake_case keys instead of kebab-case.
- Updated the PacketEvents optional dependency to
2.14.0+spigot.
2. Commands and permissions
The config.yml file can now be edited in-game with the /kib rule and /kib blacklist commands.
You don't need to reload the plugin after executing commands; this is only necessary if you edit the config.yml file manually.
To see the current value of a rule, use /kib rule <ruleName>, and if you want to edit a rule, specify a proper value
at the end (based on the rule type). Here are some examples:
/kib rule max_blocks→ Displays the current value of themax_blocksrule/kib rule max_blocks 100→ Setsmax_blocksto100in config.yml/kib rule only_use_kib_in_creative_mode false→ Setsonly_use_kib_in_creative_modetofalsein config.yml
The
/kib rulecommand requires thekib.rulepermission.
To blacklist a reactive or interactable material, use /kib blacklist <interactable|reactive> <add|remove> <material>.
This is useful if you want to prevent certain blocks from being restored, or stop specific block interactions from
triggering restoration. Here are some examples:
/kib blacklist interactable add minecraft:oak_button→ AddsOAK_BUTTONto the interactable blacklist/kib blacklist reactive remove minecraft:oak_door→ RemovesOAK_DOORfrom the reactive blacklist (assuming it was previously added)
The
/kib blacklistcommand requires thekib.blacklistpermission.
If you need help with commands, you can use /kib help. It will show you all available commands, with a short
description and usage example.
Any
kib.*permission automatically grants access to the/kib helpcommand.
The /kib reload command and the kib.reload permission haven't changed and still work the same way.
You can use the kib.admin permission to easily grant access to all commands (this is equivalent to kib.*).
Pull request: https://github.com/Atrimilan/KeepIllegalBlocks/pull/5
Optional dependencies
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:i4WvDCnD:Odzjc6UG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:i4WvDCnD:Odzjc6UG"
}

