> For the complete documentation index, see [llms.txt](https://daddy-studios.gitbook.io/daddy-studios-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-marketplace/configuration/featured.md).

# Featured Listings

A paid, time-limited highlight that pins a listing or auction to the top of the list with its own card colour.

```lua
Config.Featured = {
    enabled = true,
    durations = {
        { hours = 6,  price = 500  },
        { hours = 12, price = 900  },
        { hours = 24, price = 1500 },
        { hours = 48, price = 2500 },
    },
    paymentMethod = 'bank',
    maxFeaturedPerPlayer   = 2,
    maxFeaturedPerLocation = 10,
    allowAuctions = true,
    allowRenewal  = true,
    bgColor      = '#221113',
    bgHoverColor = '#2C1518',
}
```

| Option                     | Meaning                                                      |
| -------------------------- | ------------------------------------------------------------ |
| `durations`                | The packages players can buy. Add, remove or reprice freely. |
| `paymentMethod`            | `'cash'` or `'bank'`                                         |
| `maxFeaturedPerPlayer`     | How many featured entries one player may hold at once        |
| `maxFeaturedPerLocation`   | Cap per market, so the top of the list stays useful          |
| `allowAuctions`            | Whether auctions can be featured too                         |
| `allowRenewal`             | Extend a highlight that is still running                     |
| `bgColor` / `bgHoverColor` | Card background of featured entries in the UI                |

The fee is charged immediately and is not refunded if the listing is sold, cancelled or expires early. It is reported to `Config.OnFeeCollected` with `feeType = 'featured'` — see [Fees & Taxes](/daddy-studios-docs/scripts/daddy-marketplace/configuration/fees.md).

{% hint style="info" %}
`maxFeaturedPerLocation` is what keeps this feature worth paying for. Without a cap, everyone features everything and the highlight means nothing.
{% endhint %}

Set `enabled = false` to remove featuring from the UI entirely. Entries that are already featured simply run out and stop being highlighted.

## Pricing it

The price should be meaningful next to a typical sale on your server. If an average trade is $2,000, a $1,500 highlight for 24 hours is only worth buying for a genuinely valuable item — which is exactly the behaviour you want. If featuring costs less than a few percent of a normal sale, everything ends up featured.

## Next steps

* [Fees & Taxes](/daddy-studios-docs/scripts/daddy-marketplace/configuration/fees.md)
* [Security](/daddy-studios-docs/scripts/daddy-marketplace/configuration/security.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-marketplace/configuration/featured.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.