Commands:

/KT RELOAD
kidtool.reload
Reloads config from disk

/KT CLEAR
kidtool.clear
Clears your inventory

/KT SETSPAWN (player)
kidtool.setspawn.global
kidtool.setspawn.player
Sets the global spawnpoint or the spawn for a specific player (if a player name is passed). If neither is set, when they do /kt spawn it'll use the spawnpoint of the world they are in

/KT SPAWN
kidtool.spawn
Teleports to the player's particular spawn, the global spawn, or the world's spawn

/KT ITEM itemcode
kidtool.item.(itemcode)
Gives the player an item. Not like a Minecraft item, I mean a custom item defined in config.items

/KT GMTOGGLE
kidtool.gmtoggle
Toggles between survival and creative

/KT GMC
kidtool.gmc
Sets creative mode

/KT GMS
kidtool.gms
Sets survival mode

/KT WEATHERTOGGLE
kidtool.weathertoggle
Toggles between sun and storm

/KT SUN
kidtool.sun
Sets sunny weather

/KT STORM
kidtool.storm
Sets stormy weather

/KT TIMETOGGLE
kidtool.timetoggle
Toggles between day and night

/KT DAY
kidtool.day
Sets daytime

/KT NIGHT
kidtool.night
Sets nighttime

/KT MOB mobname|groupname
kidtool.mob.(name)
Spawns either a specific mob or a random from a spawngroup


Configuration:

Path: config.use-permissions
Values: true, false
Desc: Determines whether or not to check for permission nodes

Path: config.use-brief-time-display
Values: true, false
Desc: If true, cooldowns are HH:MM:SS else it's # minutes, # seconds, etc

Path: config.cooldowns.(code)
Values: Any subcommand of KT
Desc: Cooldown seconds to use command

Path: config.items
Desc: This is where you can put custom items to be used by the /kt item command. The keys are the item code that they will use. So config.items.sword would be obtained via /kt item sword for example.

Path: config.items.(itemcode).material
Desc: This material used to create the item

Path: config.items.(itemcode).name
Desc: The name that will be set on the item

Path: config.items.(itemcode).cooldown
Desc: Cooldown for using this item

Path: config.items.(itemcode).permission
Desc: Permission required to use item, assuming use-permissions is true

Path: config.items.(itemcode).activatesby
Values: LEFT_CLICK_AIR, LEFT_CLICK_BLOCK, RIGHT_CLICK_AIR, RIGHT_CLICK_BLOCK
Desc: This is a string list of actions that can activate the item. This is in List format, so each action should be on a new line preceeded by a dash inline with the key. Example:
Path: config.items.(itemcode).slot
Desc: This will force the item to this slot number. If an item is already in that slot, it will be moved. If the player inv is full and it cannot be moved, the old item in that slot will drop on the ground

Path: config.items.(itemcode).enchants
Desc: If the item should be enchanted, this holds the enchant list. Each key should be an enchantment namespaced key. See appendix A at the end of the docs for the key list. The value of the enchant key is the enchant level. Example:
Path: config.items.(itemcode).function
Values: spawn, playercommands, consolecommands, weather, time
Desc: This gives the item functionality.

Path: config.spawngroups
Desc: This is for grouping mobs for spawning. The /kt mob command can use either a direct EntityType name or it can use a spawn group. Put entity type names in string list format. Example:
There is a global "all" spawngroup that is made by combining all groups togther as well.

Notice: As of version 1.1 I've added the ability to spawn multiple items for an itemcode. To do so, create a subkey "0" for the first, then create subkeys for each other items. Uses the same config rules above. So for example if I wanted a dynamite kit I could do:
Technically it doesn't even have to be numbers after 0; the plugin just looks for "config.items.(itemcode).0" to determine if it should iterate subkeys of the itemcode. Just so long as you have 0 in there, it'll work. If using subkey items, don't put any config on the itemcode level as it'd be ignored. For example, this is an invalid config:
It'll give the TNT and F&S, but no torch as it only uses the subkey items since it sees the 0 key.