> For the complete documentation index, see [llms.txt](https://prism3.gitbook.io/logger/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prism3.gitbook.io/logger/extra/faq.md).

# FAQ

## What Minecraft versions does Logger support?

Logger v1.8.5 supports **Minecraft 1.8.8 all the way through 26.3+** (Paper, Purpur, Folia, Spigot, BungeeCord, Velocity).

## What Java version do I need?

Logger requires **Java 17 or higher** on the server machine (**Java 21 is recommended**). Even if your server runs Minecraft 1.8.8, running the server JVM on Java 17 will ensure complete compatibility with Logger's universal jar and modern database drivers.

## How does player logging work?

Every player activity (chat, commands, block breaks, chest opens, etc.) is logged by default. To exempt specific players or staff ranks from being logged, assign them the permission `logger.exempt`.

## How can I exempt staff from Discord alerts only?

In v1.8.5, assign the permission **`logger.exempt.discord`**. The player will still be logged to your database/files, but their actions will not spam your Discord channels!

## How do I set up the Discord Bot?

Download and place `LoggerDiscordAddon-1.8.5.jar` into your `plugins/` folder and configure your bot token in `plugins/Logger/discord.yml`. See our [**Discord Guide**](/logger/getting-started/discord-integration/discord.md) for full instructions.

## What database engines are supported?

Logger natively supports **MySQL**, **MariaDB**, **PostgreSQL**, and **SQLite** with lag-free HikariCP connection pooling and automatic schema updates.

## I need help or found a bug!

Join our [**Discord Server**](https://discord.gg/MfR5mcpVfX), run `/logger dump` on your server to create a sanitized configuration paste, and open a ticket!

## Why do I get "Host is not allowed to connect to this MariaDB/MySQL server" (Error 1130)?

The IP shown in the error is **the Web Panel's outgoing IP address**. MySQL/MariaDB rejects remote connections if your database user is restricted to `localhost`. Run this SQL command on your database server to grant remote access:

```sql
GRANT ALL PRIVILEGES ON logger.* TO 'your_user'@'WEB_PANEL_IP' IDENTIFIED BY 'your_password';
FLUSH PRIVILEGES;
```

*(Or use `'your_user'@'%'` to allow remote connections from any host).*