Interface | Description |
---|---|
IActionHandler |
This is the most crucial interface to implement in your bot
(in one or more registered handlers).
|
IChargeWhatHandler |
Called when the player may choose an item to charge after reading
a scroll of charging.
|
IDirectionHandler |
Called when a direction prompt is presented to the player.
|
IDoTeleportHandler |
Called when the player is prompted whether or not he wants to teleport.
|
IEnhanceWhatHandler |
Called when the Enhance skill menu appears with a choice of skill to enhance.
|
IGenocideHandler |
Called when the player can choose monsters to genocide.
|
IIdentifyWhatHandler |
Called when the player can choose items to identify.
|
ILevelTeleportHandler |
Called when the player can choose a level to teleport to.
|
IMakeWishHandler |
Called when the player can make a wish.
|
IOfferHandler |
Called when the player can choose the amount of gold to offer.
|
IPayDamageHandler |
Called when the player is asked to pay damage caused in the shop.
|
IReallyAttackHandler |
Called when you move towards a peaceful monster.
|
ISeducedHandler |
Called when a succubus or an incubus makes a request.
|
ISellItHandler |
Called when you drop an item in a shop and the shopkeeper is interested
in buying it.
|
IStopEatingHandler |
Called when the player is close to dying from overeating.
|
ITeleportWhereHandler |
Called when the player can teleport in a controlled way.
|
IVaultGuardHandler |
Called when a guard finds the player in a vault.
|
IWhichRingFingerHandler |
Called when you can choose which hand to put a ring on.
|
Prompt handlers are invoked on registered handlers in priority order until one of them returns a non-null value. This value is used as the response and no more handlers are invoked. The framework may handle some prompts automatically via actions before they reach bot handlers.
There are many more types of prompts that the framework always handles automatically via actions or default handlers. These are undocumented but available in the package bothack.internal.