Repository navigation
Per‐Event Configuration
WereF0X edited this page Oct 17, 2026
·
3 revisions
Now you can customize all available events that can be logged to Discord.
The mod comes with 3 configuration files to categorize events and make files less crowded with options, and they are located in the same location as the other files we've seen:
player-events.jsonserver-events.jsonchat-events.json
These are the options you will see in most of the per-event settings:
-
mode: The mode to log the message as. There are 3 options:-
NONE- Disable the event from being logged -
SIMPLE- Simple message in normal text -
STYLED- A nice embed containing more information
-
-
channelReference: The Channel Reference we have created in Step 2. -
username: Username of the Webhook. -
avatarUrl: URL of the Webhook avatar. Normally set ondefaultto use the default one we have set up in Step 3, changing this will override the avatar for this event to the newly provided link. -
embedColor: If theSTYLEDmode is used, you can customize the color of the embed that is sent.
Some events will have extra settings. The following list contains all of the events that have special settings and their extra configuration options:
-
advancementCompleted-
includeDescription: If the description of the Advancement should be included or not in the Webhook message. Affects bothSIMPLEandSTYLEDmodes.
-
-
consoleLog-
enabled: Enable or disable the console logging. This event has nomode. -
level: Minimum level to log. Options areALL,TRACE,DEBUG,INFO,WARN,ERROR,FATAL. WARNING: Setting the level to a low one (likeALLorDEBUG) WILL cause rate-limiting. At minimum, useINFO. -
sendNotificationOnFatal: If the logging level is set toFATAL(server crash), this option can be enabled to send a notification in the channel, for example pinging the tech team in charge of the server. -
fatalNotification: The notification text, described above. -
uploadLog: If enabled, when the logging is set toFATAL(server crash), the mod will automatically upload the latest.log file to the channel.
-
-
messageSent-
allowUserPings: Whether player messages logged from Minecraft into Discord should be able to ping other users. If enabled, typing the ping (with user ID) will actually ping the Discord member. If disabled, the ping will indicate the member, but they will not receive any label or sound cue. -
allowMassPings: Similar to the above option, but massively scaled, as it allows or prohibits@everyoneand@herepings. Use carefully.
-
Configuration files changes will be synced on next server startup.