Positive compatibility

This page lists all plug-ins that have special changes to improve support for this plug-in and all plug-ins for which this plug-in has special changes to improve support. (At least, all plug-ins that I'm aware off and I didn't forget).

Action Bar API

This plug-in provides an action bar API that my plug-in will use if it is available. If you install it alongside my plug-in, the wand cooldown/charges and custom tool durability will be shown in the action bars of players.

Mythic Mobs

It is possible to equip custom items from this plug-in on mobs from Mythic Mobs. To do so, you need to configure a mythic mobs item in a configuration file for mythic mobs (for instance ExampleItems.yml). In such a file, you should define a custom item like this:

MythicMobsItemName:
  NBT:
    KnokkosCustomItems: { Name: item_name }

In the example above, item_name should be the Name that you gave the custom item in the Editor. Not the Display name. Then, you should configure a custom mob to equip this item in a mob file (for instance ExampleMobs.yml):

MobName:
  Type: ZOMBIE
  Equipment:
  - MythicMobsItemName HAND

Crazy Enchantments

The enchantments from the Crazy Enchantments plug-in can be used as the default enchantments of custom items. The crazy enchantments will be listed after the vanilla enchantments and have a "[CRAZY]" suffix after their name. Furthermore, this plug-in has nice support for the Hellforge enchantment on custom items. If a custom item would be repaired with the HellForged enchantment, its custom durability will be repaired instead of the vanilla durability. If crazy enchantments is not installed, nothing will happen, except a message in the console stating that crazy enchantments doesn't seem to be installed.

Skript

Custom items and custom blocks can be used in Skripts.

Conditions

%block% is [a] kci block
%block% is [a] kci %string%
Checks whether %block% is a kci custom block named %string%
%block% (isn't|is not) [a] kci block
%block% (isn't|is not) [a] kci %string%
%itemstack% is [a] kci item
%itemstack% is [a] kci %string%
Checks whether %itemstack% is a kci custom item named %string%
%itemstack% (is not|isn't) [a] kci item
%itemstack% (is not|isn't) [a] kci %string%

Effects

give [a] kci %string% to %player%
Gives the custom item with name %string% to %player%
give %integer% kci %string% to %player%
give [a] kci %string% to %inventory%
give %integer% kci %string% to %inventory%
place kci %string% at %block%
Places the kci custom block named %string% at the location of %block%
put [a] kci %string% in %slot%
Puts the custom item named %string% in slot %slot%
put %integer% kci %string% in %slot%
%player% opens kci %string% at %string%
Lets %player% open the custom container named %string% at string host %string%
destroy kci %string% at %string%
Destroys the custom container named %strsing% at string host %string%
destroy kci %string% at %string% and drop its items at %location%
kci remove %integer% %string% from %inventory%
drop [a] kci %string% at %location%
drop %integer% kci %string% at %location%
%entity% launches kci %string%

Expressions

kci name of %block%
kci name of %itemstack%
count of kci %string% in %inventory%
Counts how many times the kci custom item named %string% occurs in %inventory%

Examples

on rightclick:
    if event-block is dirt:
        if event-item is a kci item:
            broadcast "You right-clicked dirt with a custom item named "
            broadcast kci name of event-item
    if event-block is stone:
        if event-item is kci "cube1":
            broadcast "You right-clicked a stone with a cube1 (this is a custom item I use for testing)."
    if event-block is a kci "custom_block":
        broadcast "You right-clicked a kci custom block named 'custom_block' (I literally called the block 'custom_block')"
        put 2 kci "cube2" in slot 5 of event-player
    if event-block is cobblestone:
        place kci "custom_block" at event-block
        broadcast "Right-clicking cobblestone replaces it with custom_block"

kci player eats:
    send "you ate %kci name of event-item%" to player
    drop kci "fooddd" at player's location
    player launches kci "test"

on leftclick:
    if event-block is kci block:
        broadcast "You left-clicked a custom block. Take this as a reward!"
        give kci "cube1" to event-player

on rightclick on a pig:
    if event-item is stick:
        event-player opens kci "per_location" at uuid of clicked entity
        broadcast count of kci "fast_wand" in event-player's inventory
        kci remove 2 "fast_wand" from event-player's inventory
    if event-item is cactus:
        destroy kci "per_location" at uuid of clicked entity
    if event-item is sand:
        destroy kci "per_location" at uuid of clicked entity and drop its items at event-location

on kci container recipe starts:
    broadcast duration of event-kcicontainerrecipe
    cancel event
    
on kci container recipe ends:
    broadcast "and so it ends"

See this page for more information about expressions and effects for kci containers, which you can use in e.g. on kci container recipe starts

Denizen

Custom items and custom blocks can be used in Denizen scripts. Unfortunately, the Denizen VS Code extensions doesn't recognize them, so you will get some warnings and errors, which you should ignore.

Commands

kci place [block_name:<string>] (at destination:<location>)
kci_container [player_name:<player>] opens [container_name:<string>] at [host_string:<string>]
kci_container destroy [container_name:<string>] at [host_string:<string>] (and drop items at [drop_location:<location>])
kci_give ([amount:<int>]) [item_name:<string>] to [player:<player>]
kci_give ([amount:<int>]) [item_name:<string>] to [inventory:<inventory>]
kci_remove [amount:<int>] [item_name:<string>] from [player:<player>]|[inventory:<inventory>]
kci_drop ([amount:<int>]) [item_name:<string>] at [location:<location>]
kci_launch [projectile_name:<string>] from [shooter:<entity>]

Examples

test_event_handler:
    type: world
    events:
        after player right clicks dirt:
            - if <context.item.is_kci_item>:
            - narrate "You right-clicked dirt with a custom item named <context.item.kci_item_name>."
        after player right clicks stone:
            - if <context.item.kci_item_name> == cube1:
            - narrate "You right-clicked a stone with a cube1 (this is a custom item I use for testing)."
        after player left clicks block:
            - if <context.location.is_kci_block>:
            - narrate "You left-clicked a custom block. Take this as a reward!"
            - give <kci_items[cube1]>
        after player right clicks block:
            - if <context.location.kci_block_name> == custom_block:
            - narrate "You right-clicked a kci custom block named 'custom_block' (I literally called the block 'custom_block')"
            - inventory set o:<kci_items[cube2*2]> slot:5
        after player right clicks cobblestone:
            - kci place custom_block at <context.location>
            - narrate "Right-clicking cobblestone replaces it with custom_block"
        after player right clicks pig with:stick:
            - kci_container <player> opens per_location at <context.entity.uuid>
        after player right clicks pig with:cactus:
            - kci_container destroy per_location at <context.entity.uuid>
            - narrate "#wands: <player.inventory.kci_count[fast_wand]>"
            - kci_remove 2 fast_wand from <player>
        after player right clicks pig with:sand:
            - kci_container destroy per_location at <context.entity.uuid> and drop items at <context.location>
        after kci player eats:
            - narrate "you just ate <context.food_stack.kci_item_name>"
            - kci_drop fooddd at <player.location>
            - kci_launch "test" from <player>
        on kci container recipe starts:
            - determine inputs.in:obsidian
            - narrate context.recipe_experience
        on kci container recipe ends:
            - narrate context.recipe_duration

See this page for more information about determinations and tags about kci containers, which you can use in e.g. on kci container recipe starts

Ultra Chest

This plug-in has small changes that allow users to use custom items from this plug-in in its configuration files. For information of how to use this, take a look at commoncore config info at the section 'Custom Item and Textures (experimental)'.

Mimic

Mimic is a plug-in that makes it easier to integrate custom item plug-ins with plug-ins that would like to use custom items (and some other integrations that are irrelevant for this plug-in). Custom items from this plug-in can be used by plug-ins that use Mimic. The identifiers of items from this plug-in will be like knokkoscustomitems:item_name where item_name is the name you used in the Editor.

ItemBridge

Just like Mimic, ItemBridge is a plug-in that makes it easier to integrate custom item plug-ins with plug-ins that would like to use custom items. (This plug-in integrates with both Mimic and ItemBridge for optimal reach.) The identifiers of items from this plug-in will be like KnokkosCustomItems:item_name where item_name is the name you used in the Editor.

Magic

The Magic plug-in adds mana and spells. If you use Magic alongside this plug-in, wands from this plug-in can consume mana from Magic and/or launch Magic spells rather than custom projectiles. If you also install ActionBarAPI, players can see their current mana while holding a custom wand that requires mana.

Note: Magic overrides the server resourcepack by default, which will hide the custom textures from this plug-in. You can turn this behavior off by putting default_resource_pack: "" in their config.yml.

SilkSpawners

The SilkSpawners plug-in allows players with the right permissions to mine mob spawners blocks when they are using the right pickaxe with the silk touch enchantment. In their config, you can configure the allowed pickaxes like this:

# Allowed set of tools which can mine a spawner. IDs are supported, too
allowedTools:
- STONE_PICKAXE
- knokkoscustomitems:silk_pickaxe

This would allow players to either mine mob spawners with a stone pickaxe, or with a custom pickaxe from this plug-in called silk_pickaxe (when it has the silk touch enchantment). Note:

Players with the silkspawners.nosilk.* permission can mine mob spawners with any pickaxe, with or without silk touch. When you are OP, you have this permission. So, when you want to test this feature, make sure to deop yourself first.
Players without the silkspawners.silkdrop.* permission can't mine any mob spawners at all, regardless of whether they have the right pickaxe and silk touch. So, when you want to test this feature, make sure that you give yourself this permission.

Conditions

Effects

Expressions

Examples

Tags

Commands

Examples