From Kolmafia
Jump to navigation Jump to search

A mood is a set of triggers that are executed after any BeforeBattleScript and before an adventure.



  • Trigger On: The trigger to check the mood for an action.
  • Check For: The condition required to take an action.
  • Command: The CLI command to execute.
  • add entry - Add an entry to the mood with the current settings.
  • auto-fill
    • minimal set - Adds all current active effects on the player. Users will find this function extremely useful.
    • maximal set - Adds the castable buffs available to the player. This only includes buffs available from skills.
  • Active mood - A drop-list of moods with the current active mood. The scroll box lists all triggers for the active mood.
  • new list - Create a new mood. Entering the name of an existing mood will set it as active.
  • delete list - Deletes the current active mood selected.
  • copy list - Copy the current triggers of the active mood into a new mood. This will replace the mood if it exists.
  • execute - Execute the current mood.


There are three types of triggers in the drop-down list. A trigger is checked upon the completion of an adventure or prompt from the user.

  • When an effect is lost - An effect is no longer active on the character.
  • When an effect is gained - An effect is active on the character.
  • Unconditional trigger - Trigger command is executed every time.


If the trigger is for an effect, the field is a drop-down list of all the effects in the game. The interface will fuzzy match to what the user types in. In addition, the interface will match common abbreviations such as "sss" matching to "Shortie Shaman Shurprise" and "Stevedave's Shanty of Superiority". The filtering is quite robust. For example, the interface will accept "2020" as matching to 20/20 Vision.

Unconditional triggers will always execute the command and does not allow the user to add a condition.


The command is a CLI command. The command will be executed if the condition for the trigger is true. Unconditional triggers are primarily for advanced users as it requires familiarity with the CLI and scripting. Typical usage is to use an if statement to check for the condition and then execute a command. See CLI scripting for control structures available for scripting.

Using the CLI

Moods are can be managed through the CLI using "mood" and "trigger" commands.

mood* list | listall | clear | autofill | execute | repeat [numTimes] | moodName [numTimes] - mood management.
trigger* list | clear | autofill | [type,] effect [, action] - edit current mood
  • mood - List all triggers for current mood. Equivalent to trigger list.
  • mood list - List all saved moods including active mood.
  • mood clear - Remove all triggers from the current mood. Ignores composable moods.
  • mood autofill - List current moods available.
  • mood execute [numTimes] - Execute current mood. If [numTimes] isn't given, executes the mood by looking at the triggers for each command. If [numTimes] is given, unconditionally executes every command [numTimes] times.
  • mood repeat [numTimes] - Works exactly like execute.
  • mood <mood> [numTimes] - If [numTimes] isn't given, sets <mood> as your current mood. If [numTimes] is given, unconditionally executes the given mood [numTimes] times, then goes back to the original mood. If mood doesn't exist, does nothing.

See the page for information.

Composable moods

Composable moods can be used to combine a set of moods together. Composable moods are handled through the CLI as the interface doesn't have equivalent functionality.

<mood> extends <mood>[, mood] 

A composable mood is treated just like a normal mood but multiple moods. In addition, triggers can be added and removed from the mood itself. If you want to clear all the moods the composable mood is referencing without removing triggers specific to the mood, you can extend the "apathetic" mood.

mood default extends apathetic

Anonymous composable moods can be created by using a list of existing moods. Anonymous moods are temporary and will disappear when the mood is changed or the session ends. This is useful when you don't want to create a new mood every time.

mood combat, item, sea


A common example is a player making a farming mood. Instead of creating a mood for effects that increase item and meat in a single list, the player creates a "item" and "meat" mood. The player then defines a "farm" mood consisting of the item and meat moods.

mood farm extends item, meat