Помогите Advanced Ban выводит в MYSQL русскую причину в кракозябры.

Я ставил кодировку cp1251_general_ci, но не помогло всё равно вместо русской причины была причина ?????
На сервере если забанить, кикнуть, замутить игрока, то русская причина пишет. А вот на MYSQL нет.
Прошу помочь. Мне очень нужно чтобы в банлисте выводилась русская причина.

 

utf8 не?

 

Вроде кириллица не cp1251? Хорошо, сейчас попробую.

 

Не помогло

 

Вроде нужна кодировка Windows-1251

 

Ставил, тоже не помогало

 

А пробовал utf8_unicode_ci ?

 

Да

 

Другую версию плагина попробуй.

 

Сейчас попробую.

 

В MYSQL уже всё нормально, но на сайте всё ещё кракозябры.

 

# AdvancedBan v2 - Coded by Leoko
# For each setting there is a small description
# please read it carefully before changing anything
# For more information visit: https://www.spigotmc.org/resources/advancedban.8695/
# Do you want your own Plugin or Website, check out our Dev-Page: http://dev.skamps.eu

# If set to false all bans will be saved locally in the data.yml
UseMySQL: true

# Set to false if you want to have only short messages in the console
# On startup and on the shutdown.
DetailedEnableMessage: true
DetailedDisableMessage: true

# This will be the default reason to be displayed if none is given
DefaultReason: "Неизвестно"

# Change this if your server has a diffrent time that your users.
# eg.: ServerTime: 16:43 | Your Time: 13:43 | TimeDiff has to be set to -3
# You can check the server time with /systemPerfs
TimeDiff: 0

# This commands will be disabled for muted players
# A player woun't be able to bypass with eg "/minectaft:me"
MuteCommands:
- 'me'
- 'say'

# This players will not be able to get punished in any way
# this also works if the player is offline
ExemptPlayers:
- 'ForcePlayYT'

# The date-format which will be used for the %DATE% variable
DateFormat: "dd.MM.yyyy-HH:mm"

# If you use extern REST-APIs they will have to respond in JSON
# The given APIs will only be used for NAME -> UUID
# For UUID -> NAME will either the official MojangAPI or the InternFetcher be used!
# To check if you can use the intern fetcher do /systemPerfs and compare your uuid
# to the one you can see online on http://NamesMC.com
# if they are similar we recommend using the InternFetcher
UUID-Fetcher:
# If dynamic it set to true it will override the 'enabled' and 'intern' settings
# and automatically detect the best possible uuid fetcher settings for your server.
# Our recommendation: don't set dynamic to false if you don't have any problems.
Dynamic: true
Enabled: false
Intern: false
REST-API:
URL: "https://api.mojang.com/users/profiles/minecraft/%NAME%?at=%TIMESTAMP%"
Key: "id"
BackUp-API:
URL: "https://us.mc-api.net/v3/uuid/%NAME%"
Key: "uuid"

# These are the commands that will be performed on warns
# If you skip a number the command from before will be performed
# You can also use not-AdvancedBan-Commands like 'broadcast' or 'clear %PLAYER%
# Variables: %PLAYER%, %REASON%, %COUNT%
WarnActions:
3: "kick %PLAYER% &c&oВы получили 3 предупреждения!"
4: "tempban %PLAYER% 30м &c&oВы получили 4 предупреждения!"
5: "tempban %PLAYER% 5ч &c&oВы получили 5 предупреждений!"
6: "tempban %PLAYER% 7д &c&oВы получили 6 предупреждений!"
7: "tempban %PLAYER% 1месяц &c&oВы получили %COUNT%th предупреждений!"
10: "ban %PLAYER% &c&oВы получили 10 предупреждений!"

# Here you can create permission-nodes for max-punishment-duration.
# The permission "ab.tempban.dur.1" would allow the player to ban max. for 600sec = 10min
# The permission "ab.tempwarn.dur.2" would allow the player to warn max. for 3600sec = 1h
# You can only create up to 10 perms. The perms can be overridden with "ab.COMMAND.dur.max"
TempPerms:
1: 1296000
2: 3600
3: 43200

# This is useful for bungeecord servers or server with permission systems which do not support *-Perms
# So if you enable this you can use ab.all instead of ab.* or ab.ban.all instead of ab.ban.*
# This does not work with negative permissions! e.g. -ab.all would not block all commands for that user.
EnableAllPermissionNodes: false

# With this active will show more information in the console, such as errors, if
# the plugin works correctly is not recommended to activate it since it is
# designed to find bugs.
Debug: false

# This is the amount of days that we should keep plugin logs in the plugins/AdvancedBan/logs folder.
# By default is set to 10 days.
Log Purge Days: 10

# Removes the prefix of the plugin in every message.
Disable Prefix: false