-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathconfig.yml
More file actions
88 lines (68 loc) · 3.37 KB
/
config.yml
File metadata and controls
88 lines (68 loc) · 3.37 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
##############################################################################
# Chat Filter / Matching #
##############################################################################
sanitize-chat: false
sanitize-signs: false
sanitize-commands: false
# Option to disable filtering on the first X arguments of a command (eg "/f ")
sanitize-commands-start-argument: 2
# A command to run whenever a player uses a bad word (eg "/mute %name% 5m")
badword-result-command: ''
# If more then 55% of a long chat message is uppercase, make it lowercase
anti-caps: true
# If a substitution isn't specified in blocked-words.txt, this will get used
# Set to empty to disable, or to a single character to auto-match word length
default-badword-replacement: '*'
# Warning: This option can cause harmless words to be blocked if their reverse
# spelling matches a blocked word
check-badwords-backwards: false
##############################################################################
# Spam Limiter #
##############################################################################
anti-spam: false
spam-result-command: "kick %name% §cReceived TMC/TMS from client\\n§fEither lag or spam... :P"
max-chats-per-second: 4
max-chats-per-10s: 15
max-chats-per-minute: 35
##############################################################################
# Item Sharing #
##############################################################################
# Enable [item-replacement] feature
item-hover-display: true
# To embed item hover-displays in chat, players can put {prefix}{sub}{suffix}
# in their message and ChatManager will substitute it for a display component.
# "sub" can be repeated 2+ times to escape the subtitution.
# Default format is [i] as seen below
item-share-prefix: '['
item-share-suffix: ']'
item-share-mainhand: 'i'
item-share-offhand: 'o'
# Note: Items in hotbar can be shared with 1-9
# The limit in bytes of item-display components sent to client per message
message-json-limit: 15000
##############################################################################
# General Features #
##############################################################################
# Automatically update the plugin (might be unreliable)
update-plugin: true
# Should we use the player's DisplayName in their chats?
use-player-displaynames: true
# Should we use the player's current Team settings in their chats?
use-player-teams: true
# Should we use the main (or per-player) scoreboard for Team lookups?
use-main-scoreboard: true
plugin-message-prefix: "&3<&aC&3>&f "
log-chat-to-console: true
# For the /color command, trigger /nick (for Essentials compatibility)
set-nickname-when-setting-color: false
# Should name colors also be applied to the (TAB) player list?
use-colors-in-player-list: true
# Should we use the "team color" feature of teams to color overhead names?
# Note: This will be incompatible with LITERALLY ANYTHING ELSE that uses teams
use-teams-for-name-colors: false
# It is recommended to disable these if you have a plugin or server that
# already provides sign/chat color permissions. Eg: EssentialsChat or Purpur
chat-colors: true
chat-formats: true
sign-colors: true
sign-formats: true