Commands

Commands

Use with /kismet <command>. <> denotes required, [] denotes optional. All commands listed here require at least permission level 2 (command block usage, by default all server operators have it).

Player bound commands

Commands listed here can only be run in-game by a player (no FakePlayer, no command block, no server console). The player must additionally have enough permissions to run the /kismet command.

Command	Description
reset	Resets the target database (required after recipe and/or mod changes)
block	Adds the currently help item to the target filter
pardon	Removes the currently help item from the target filter
force	Adds the currently help item as a forced target
unforce	Removes the currently help item from the forced target list

Other commands

All commands listed bellow can be run from any source that has permission to run the /kismet command.

Command	Description
block <item>	Adds item into the target filter
pardon <item>	Removes item from the target filter
force <item>	Adds item as a forced target
unforce <item>	Removes item from the forced target list
refresh	Forces the target library to recompile. This happens automatically when mod configs are changed
dump <list>	Dumps into chat the contents of list (blacklist, database, library, override, savedata)
serverOnlyReset	Resets the target database without subtype unfolding, avoiding network load but leading to a more limited target database
stats	Shows a listing of the number of registered targets and their categories
help	Shows a list of the possible commands and a link to this page!

• item can be written out on the string format allowed in the configs (mod[:item[:meta[:nbt]]]) or using the same format as in /give (without the user argument).
• list corresponds to run-time target lists, not ones present in the user config (such as Forced Targets or the Generated Target Filter).
  • blacklist corresponds to item origins that have been nulled (removed) on run-time, either by override config or API usage (the prior takes priority over the former);
  • database is the final compilation of all the other run-time lists and the end-product of /kismet reset|serverOnlyReset;
  • library is the subset of database from where Kismet fetches possible targets. This subset is created by filtering database with the user mod configurations (or server configurations if under a dedicated server environment);
  • override corresponds to item origins that have been forced (added) on run-time, either by override config or API usage (the prior takes priority over the former);
  • savedata is the local copy of database which is saved to disk after a reset, and henceforth loaded on further sessions. Should be effectively database sans the run-time overrides (see blacklist and override).