Releases: sciwhiz12/Concord
v1.4.0 for Minecraft 1.18.2
First (and probably last) release for Minecraft 1.18.2, alongside a good amount of changes and features.
Note for server administrators: The discord.channel_id
config setting was renamed to discord.chat_channel_id
, with the addition of the reports channel config setting. After saving the config while the server is running, you can reload Concord through /concord reload
.
Changelog
📨 A new /report
command is now provided, alongside the new config setting discord.report_channel_id
- Any user can run
/report
against another user with a reason, and a report will be sent to the configured report channel ID with details of both users and the report reason. - Any online server operators in-game will also see a feedback message in their chat (similar to what they would see for operator-ran commands), allowing quicker response to reports.
- When the config setting for the report channel ID is empty, the command is not registered. If the setting is configured during the runtime of the server, an operator must run
/reload
for the/report
command to appear and work. - Note that the command is registered if the config setting is non-empty, even if the provided channel ID is invalid or does not exist.
🗨️ Message replies are now supported and shown to players in-game.
- The inline chat message shows the name of the user the message is in reply to. Hovering over the username shows the regular user information, as well as the full message of the replied message.
🔗 Attachments and stickers are now supported and shown to players in-game.
- Stickers are shown in purple at the end of the message (before any attachements if present), and include the name of the sticker.
- Attachments are shown in cyan at the end of the message, and include inline the extension of the attachment. Hovering over the attachment indicator shows the full name of the file and the URL of the attachment.
- Clicking the attachment indicator opens the attachment's URL in your browser (subject to the usual URL warning screen shown by Minecraft).
- This is a less-noticeable feature, as it involves support across Concord versions between the server and client (for backwards compatibility).
- Gliding over the technical details, this means that connecting to a server with a newer Concord version will now properly handle differing translations: any (substantially) unchanged translations are lazily translated, while newer or modified translations are eagerly translated on the server before being sent to the client.
- Vanilla clients and Concord clients with matching versions work normally as expected.
😄 Added support for the /me
command
- The new
hooks.emote_command
config setting controls whether to hook into this command. This allows disabling the hook if another mod's hook for the same command causes a conflicts.
📢 Modified /say
command to use the command.say
message in all cases
- Previously, the message sent to the channel for
/say
by entities used the text fromchat.type.announcement
, disregarding the
configured message atcommand.say
(used by non-entities like the server). This change makes any invocation of/say
use thecommand.say
message.
Config changes
- 🚚 Moved
discord.channel_id
todiscord.chat_channel_id
- ➕ Added
discord.report_channel_id
- ➕ Added
notify.command.emote
- 🚚 Moved
say_command_hook
tohooks.say_command
- ➕ Added
hooks.emote_command
Full commit log: 1.18.1-v1.3.0...1.18.2-v1.4.0
Classifiers:
- none - Regular JAR, with all dependencies shaded and repackaged inside.
-sources
- Sources jar, for use when developing against the mod.-lite
- Lite jar, containing none of the dependencies. Usually no reason to use this.
v1.3.0 for Minecraft 1.18.1
First release for Minecraft 1.18.1. Notable new features;
- Added a new notification config setting
player.adv.respect_gamerule
which controls whether the advancement notification messages respect theannounceAdvancements
gamerule. When the config setting is enabled, then setting the gamerule in-game will controll all advancement messages; when disabled, only the config setting will be respected for controlling the advancement messages. - Added a new
messages.hide_crown
which controls when the crown icon for the server owner is visible in the user tooltip in-game. It can be set to always visible, never visible, or visible according to the Discord client logic for showing the owner crown: not visible if there are any hoisted roles with the Administrator permission (even if there are none with the role), otherwise visible. - Fixes a small annoyance where the message from
/concord status
is broadcast to all operators.
Full commit log: v1.2.0...1.18.1-v1.3.0
Classifiers:
- none - Regular JAR, with all dependencies shaded and repackaged inside.
-sources
- Sources jar, for use when developing against the mod.-lite
- Lite jar, containing none of the dependencies. Usually no reason to use this.
Release 1.2.0
- Update to Minecraft version, Forge, and dependencies
Minimum required Forge version is now 1.16.5-36.0.52. - Backend changes, such as a new versioning model and using ForgeGradle 4
- Fix inverted use of integrated server config setting
Previously, the config setting was interpreted in the opposite way as marked (having it totrue
would disable, and vice-versa). - Add hook into /say command
A new config setting (enabled by default) enables a hook into the/say
command, allowing server owners to communicate from their console. This works with anything that can use/say
(players, console, command blocks, entities via/execute
). - Add config settings for controlling mentions
A new config category for mentions is added, to allow control on whether mentions in messages from Minecraft to Discord cause pings. There are 4 options to control: a global mentions settings (controls the others), public mentions (@everyone
and@here
, disabled by default), user mentions, and role mentions.
User and role mentions work when manually using the mention syntax (<@00...0>
and<@&00...0>
) respectively. These mentions are still controlled by the permissions granted to the bot user (for example, messages cannot ping@everyone
even when enabled in the settings if the relevant permission is not granted to the bot). - Remove invite URL from logging
Note: previous versions of Concord would log an invite URL to the logfile when the discord integration is enabled. Please scour your logs to remove this invite URL.
Classifiers:
none - Regular JAR, with all dependencies shadowed/shaded in.
-sources
- Sources jar, for use when developing against the mod.
-lite
- Lite jar, containing none of the dependencies. Usually no reason to use this.
Release 1.1.1
Some fixes for broken behavior, and two internal refactors; no noteworthy changes.
- @sciwhiz12: Fix member statuses always showing as offline
- @sciwhiz12: Rework ModPresenceTracker map to use player UUIDs
- @sciwhiz12: Move MessageUtil to util package
- @sciwhiz12: Fix eager translations
Classifiers:
none - Regular JAR, with all dependencies shadowed/shaded in.
-sources
- Sources jar, for use when developing against the mod.
-lite
- Lite jar, containing none of the dependencies. Usually no reason to use this.
Release 1.1.0
An update to 1.16.5, and a minor yet breaking change: the config for Concord is now in the top-level config
folder instead of within the world. This change was in response to feedback, to prevent leaking of the bot token due to backups or world uploads.
Admins are advised to move their config (and rename to concord-common.toml
), and inspect any world backup for the config file.
Classifiers:
none - Regular JAR, with all dependencies shadowed/shaded in.
-sources
- Sources jar, for use when developing against the mod.
-lite
- Lite jar, containing none of the dependencies. Usually no reason to use this.