> For the complete documentation index, see [llms.txt](https://paw-studio.gitbook.io/paw-studio-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://paw-studio.gitbook.io/paw-studio-docs/litefish/fishing-spot.md).

# Fishing Spot

## Fishing Spot

Fishing Spots allow the creation of **temporary hotspots** in the world. These hotspots provide **modifiers** within a defined area and can affect gameplay mechanics such as drop tables or other player modifiers.

<div align="left"><figure><img src="/files/ZxExJydXF30bw28ng5eh" alt="" width="563"><figcaption></figcaption></figure></div>

All configurations are located in:

```
plugins/LiteFish/spots
```

Active hotspots are saved across world reloads. All data about currently active hotspots is stored in:

```
plugins/LiteFish/data/spots
```

***

### Functionality

Fishing Spots can:

* Modify a **drop table** in the specified category.
* Apply **modifiers** to players within the hotspot area.

### Example Configuration

```json
{
  "category_id": "skull_drop_table",
  "modificator_id": "skull_modificator",
  "storage": 100,
  "time": 10,
  "item": {
    "material": "NETHER_STAR",
    "display_name": "§x§C§7§F§D§F§F Nether Bait"
  },
  "animation": {
    "id": "spot_animation"
  },
  "display_text": [
    "<#484EFF>☠ <#69D1FF>§lFishing Spot §r<#484EFF>☠",
    " ",
    "<gray>Catch left: <white>%storage%",
    "<gray>Bite time: <white>%time%",
    " "
  ]
}
```

***

#### Configuration Fields

| Field            | Description                                                                                                           |
| ---------------- | --------------------------------------------------------------------------------------------------------------------- |
| `category_id`    | The ID of the drop table category that will be applied when a player fishes in this hotspot.                          |
| `modificator_id` | The ID of the modifier that will be applied within the hotspot.                                                       |
| `storage`        | The number of uses for this hotspot.                                                                                  |
| `time`           | Lifespan of the hotspot in seconds.                                                                                   |
| `item`           | The item representing the hotspot. Throwing this item into water will spawn the hotspot, and the item will disappear. |
| `animation`      | Animation applied to the hotspot. Available Actions: `WORK`, `START`.                                                 |
| `display_text`   | Text displayed above the hotspot. Supports placeholders: `%storage%`, `%time%`.                                       |

***

#### Additional Notes

* You can **limit the number of active hotspots per player** to prevent spamming. For example, in `config.json`:

```json
"max_spot_amount": 3
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://paw-studio.gitbook.io/paw-studio-docs/litefish/fishing-spot.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.