> For the complete documentation index, see [llms.txt](https://docs.cheddah-development.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cheddah-development.net/plugin-documentaion/better-baltop/playerpoints-integration.md).

# PlayerPoints Integration

PlayerPoints adds an optional second leaderboard to BetterBaltop.

### Enable the integration

1. Stop the server.
2. Install PlayerPoints `3.3.5` or a compatible 3.x release.
3. Start the server.
4. Look for the BetterBaltop message confirming that the PlayerPoints hook was enabled.
5. Run `/bbt refresh points` if you want an immediate refresh.
6. Open `/baltop`.

When the hook succeeds, a switch button appears in slot 50 of the menu. Players can use it to move between the economy and points leaderboards. Switching always returns to page 1.

If PlayerPoints is missing or cannot be hooked, BetterBaltop continues normally with Vault only. The switch button is hidden rather than showing an unavailable feature.

### How points are displayed

* Entries remain player heads.
* Points use readable thousands separators.
* PlayerPoints' configured singular or plural currency name is included when available.
* The `maximum-entries` and `show-zero-balances` settings apply.
* Accounts with names beginning with `*` are hidden because they are non-player accounts and do not belong in a player-head leaderboard.

### Performance and failures

BetterBaltop asks PlayerPoints for its sorted rankings asynchronously, so database-backed work does not block Paper's main server thread.

Vault and PlayerPoints have separate caches. If a PlayerPoints refresh fails, the last successful points list remains available and the economy leaderboard is unaffected.


---

# 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://docs.cheddah-development.net/plugin-documentaion/better-baltop/playerpoints-integration.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.