distrukter4
Пользователь
- Сообщения
- 63
- Плагин
- CMI
- Ядро сервера
- Spigot
- Paper
- Версия сервера
- 1.19
- Память сервера ОЗУ
- 8Gb
Всем привет.
Прошу помощи по плагину CMI.
Когда пишу в чат не зависимо в какой(локальный | глобальный), всегда сообщения отправляются в локальный чат. В глобальный я пишу перед сообщением ставлю "!" знак.
Да, я находил 2 темы на форуме, но мне это не помогает..
Код ниже, пожалуйста помогите.
Прошу помощи по плагину CMI.
Когда пишу в чат не зависимо в какой(локальный | глобальный), всегда сообщения отправляются в локальный чат. В глобальный я пишу перед сообщением ставлю "!" знак.
Да, я находил 2 темы на форуме, но мне это не помогает..
Код ниже, пожалуйста помогите.
JavaScript:
Chat:
# Will try to modify chat to display it in defined format
ModifyChatFormat: true
# When set to true, regular and private messages (excludes clean messages) will have additional information when hovering over it (PlaceHolderAPI supported) and can be clicked for quick reply option
# To change default hover over messages seen on sent message, go to your locale file to Chat section
ClickHoverMessages: true
DiscordSRV:
# Enables support for DiscordSRV plugin
Enabled: false
# Defines name of global chat channel in discordsrv
GlobalChannel: global
# Indicator which can be used as {discord} in chat format to indicate that message came from discord and not ingame
Label: '&2[&7D&2]'
UnlinkedLabel: '&4[&cD&4]'
# Enables support for DynMap web chat
DynMapChat: true
# When set to false, each time you will use /r you will reply to person you previously sent message directly or to person who sent you message if there is none you have conversion before
# When this set to true, players with /r will reply to person who last sent private message. This can result in confusion when using /r while getting private messages from multiple players
ReplyToLastMessenger: true
# If ReplyToLastMessenger is set to false, then timeOut will be taken into consideration to who you should reply
# If you had conversation in last 120 seconds (default) then even receiving message from 3rd person, you will still reply to original player
# If you had conversation in longer then 120 seconds period, then you will reply to latest person who send you a message
LastMessengerTimeOut: 120
# When set to true players will need to have cmi.command.msg.[groupname].send where [groupName] is receivers main permission group
PrivateMessagesGroups: false
# When set to false, web pge links in a chat will not get shortened to default [LINK] format
TranslateLink: true
# Defines regex when replacing url in chat with short word
# Examples:
# (https?:\/\/(?:www\.|(?!www))[a-zA-Z0-9][a-zA-Z0-9-]+[a-zA-Z0-9]\.[^\s]{2,}|www\.[a-zA-Z0-9][a-zA-Z0-9-]+[a-zA-Z0-9]\.[^\s]{2,}|https?:\/\/(?:www\.|(?!www))[a-zA-Z0-9]\.[^\s]{2,}|www\.[a-zA-Z0-9]\.[^\s]{2,})
# ((http|https|ftp|ftps)\:\/\/)?[a-zA-Z0-9\-]+\.[a-zA-Z]{2,3}(\/\S*)?
# ((http|https|ftp|ftps)\:\/\/)?[a-zA-Z0-9\-]+\.[a-zA-Z]{2,3}(\/\S*)?([^\s]+)
LinkRegex: ((http|https|ftp|ftps)\:\/\/)?[a-zA-Z0-9\-]+\.[a-zA-Z]{2,3}(\/\S*)?([^\s|^\)]+)
# When set to true, particular variables in chat will be translated into items player are holding. List of variables belove
HoverItems: true
# Defines regex when replacing item line in chat with players item in hand information. Only works when CMI hover over chat format is enabled
ItemRegex:
- (\%item\%)
- (\[item\])
- (\%i\%)
# Attention! This will require you to have CMI Bungee plugin which can be found at zrips.net
# Or direct download https://www.zrips.net/cmi/
# Do you want to enable private messaging over bungeecord
BungeeMessages: false
# Do you want to enable public messaging over bungeecord
# Player needs to have cmi.bungee.publicmessages.[servername] permission node to be able to send messages to target server
BungeePublicMessages: false
# Do you want to enable staff messaging over bungeecord
BungeeStaffMessages: false
# Used for simple chat messages. Optional variables: {displayName} {world} {prefix} {suffix} {group} {shout} {message}. Supporting PlaceHolderAPI variables like %player_server%
# ATTENTION! Dont use gradient colors for {message} variable, if you want to apply gradient for it, utilize GeneralMessageFormat section
GeneralFormat: '{prefix}&f{displayName}&7: &r{message}'
# Will define message format itself, this allows to have gradients in messages
# It NEEDS to contain {message} otherwise we will ignore this setup
# For 1.16+ servers you can use color gradients like '{#b3a28f>}{message}{#d7b8e6<}'
# You can have more than 2 colors in gradient. To define it repeat {message} variable. For example '{#b3a28f>}{message}{#5c6999<>}{message}{#d7b8e6<}'
GeneralMessageFormat: '{message}'
# Defines range of regular messages to travel
# Set to -1 to disable range restriction
GeneralRange: 100
# Defines range of shout messages to travel
# Shout messages should start with ! and player should have cmi.chat.shout permission
# GeneralRange should be enabled
# set to 0 to shout across all worlds, -1 to disable
ShoutRange: 0
# Defines cost for each shout message
ShoutCost: 0
# Prefix used to indicate that message should be sent to public chat instead of current players chat room
# Set it to empty field if you want this feature to be disabled
ChatRoomShout: '!'
# Time in seconds you want to keep chat rooms alive before removing them
# This only applies to empty rooms after last user leaves it
ChatRoomLife: 3600
# Defines suggested commands when you click on public, private and similar messages. [playerName], [playerDisplayName] and [playerNickName] can be used to include players name
ClickSuggestions:
pubmsg: '/msg [playerNickName] '
privmsg: '/msg [playerNickName] '
staffmsg: '/msg [playerNickName] '
helpop: '/msg [playerNickName] '
chatroom: '/msg [playerNickName] '
discord: '/msg [playerNickName] '
# Use numeric increments to separate groups from each other. If player has more than one, then line with higher number will be used
# Add as many lines as you need too
# cmi.chatgroup.[id] permnission node to use
# Permission example: cmi.chatgroup.2
# ATTENTION! Dont use gradient colors for {message} variable, if you want to apply gradient for it, utilize GroupMessageFormat section
GroupFormat:
'1': '{prefix}&f{displayName}&3: &f{message}'
'2': '{prefix}&9{displayName}&3: &f{message}'
'3': '{prefix}&e{displayName}&3: &f{message}'
'4': '{prefix}&a{displayName}&3: &f{message}'
# Use numeric increments to separate groups from each other. If player has more than one, then line with higher number will be used
# Add as many lines as you need too
# cmi.chatmessagegroup.[id] permnission node to use
# Permission example: cmi.chatmessagegroup.2
GroupMessageFormat:
'1': '{message}'
'2': '{message}'
'3': '{message}'
Colors:
# If set to true then all public messages will be filtered from color codes and will allow to colorize them with appropriate permission node
# cmi.colors.publicmessage.[colorName]
# Colors: black(&0), darkblue(&1), darkgreen(&2), darkaqua(&3), darkred(&4), darkpurple(&5), gold(&6), gray(&7), darkgray(&8), blue(&9), green(&a), aqua(&b), red(&c), lightpurple(&d), yellow(&e), white(&f), magic(&k), bold(&l), strikethrough(&m), underline(&n), italic(&o), reset(&r)
PublicMessage: true
PrivateMessage: true
# If set to true then /me messages will be filtered from color codes and will allow to colorize them with appropriate permission node
# cmi.colors.me.[colorName]
me: true
# If set to true, then color codes will get removed from text instead of leaving them if player dont have appropriate permission node for that color
CleanUp:
publicmessage: true
privatemessage: true
me: true
signs: false
books: true
# List of strings to ignore when checking chat for color codes player cant use.
# This will bypass players colorcode restrictions and will allow usage of particular chat formats
# Applies only for public and private messages
WhiteList:
- '&c❤&7'
# If set to true then nickName will be filtered from color codes when player changes it
# cmi.colors.nickname.[colorName]
NickName: true