# Homunculus Item Drops

Logs item drops when a **player's homunculus** lands the killing blow on a monster.

**Action:** `hom_item_drop`

## Why Use It

* **Monitor AFK homunculus farming** separately from direct player kills
* **Track Alchemist/Geneticist hunting patterns**
* **Distinguish automated farming** from active gameplay

## Configuration

```
ragnasync_hom_item_drop_log_enabled: true
ragnasync_hom_item_drop_log_channel_id: "YOUR_CHANNEL_ID"
ragnasync_hom_item_drop_log_min_rate: 500
ragnasync_hom_item_drop_log_types: "all"
```

| Setting      | Description                                                                                                                        | Default |
| ------------ | ---------------------------------------------------------------------------------------------------------------------------------- | ------- |
| `enabled`    | Enable/disable logging                                                                                                             | `false` |
| `channel_id` | Discord channel for drop logs                                                                                                      | -       |
| `min_rate`   | Minimum drop rate to log (500 = 5%)                                                                                                | `500`   |
| `types`      | Item categories — `all`, `healing`, `usable`, `etc`, `armor`, `weapon`, `card`, `petegg`, `petarmor`, `ammo`, `shadowgear`, `cash` | `all`   |

Tokens are comma-separated and case-insensitive. See [Item Drop Types](/getting-started/channels-conf.md#item-drop-types) for the full list with descriptions.

{% hint style="warning" %}
This filter is **item categories**, not mob classes. `"mvp,miniboss"` won't work — those aren't item types and every token will be rejected (watch for `[Warning]: Unknown item type '...'` at map-server startup).
{% endhint %}

For data fields and more details, see [Mob Item Drops](/logging/mob-item-drop-log.md).

## Custom Messages

Want to customize how these messages look? Head to the **Message Routes** page on your dashboard, set the format to **Custom Message**, and compose your own template using `{{placeholder}}` syntax.

**Example template:**

```
:paw_prints: {{player_name}}'s homunculus got {{item_name}} from {{mob_name}}! ({{rate}})
```

**Available placeholders for this event:**

| Placeholder        | Example                                        |
| ------------------ | ---------------------------------------------- |
| `{{player_name}}`  | Marky                                          |
| `{{mob_name}}`     | Poring                                         |
| `{{mob_id}}`       | 1002                                           |
| `{{item_name}}`    | Apple                                          |
| `{{item_id}}`      | 512                                            |
| `{{rate}}`         | 50.00%                                         |
| `{{rate_raw}}`     | 5000                                           |
| `{{src_template}}` | :gem: \[Card Drop] Marky obtained Poring Card! |

{% hint style="info" %}
`{{src_template}}` contains the pre-formatted message from your game server's `[template: ...]` field. If your server doesn't send one, it resolves to empty. See [Message Templates](/builder/message-templates.md) for details.
{% endhint %}

See [Message Routing](/builder/message-routing.md) for more about formats, conditions, and multi-channel routing.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ragnasync.com/logging/hom-item-drop-log.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.