Tags
Creators
Details
2.4.0b-forge-1.18.2
Compatibility
Changes
Paradigm 2.4.0b
This beta is a major update focused on the new Discord integration, richer chat, safer live configuration changes, and reliability across storage, permissions, moderation, and all supported loaders.
New
- Added a first beta version of Discord integration module:
- Two-way chat between Minecraft and Discord, with configurable formatting, Discord role colors in Minecraft, replies, attachments, embeds, stickers, message edits, and deletion notices.
- Optional webhook mode gives relayed players their own name and skin head instead of using one shared bot identity.
- Notifications for server starts and stops, restarts, joins and leaves, deaths, advancements, and moderation actions.
- Separate channels can be configured for chat, notifications, server events, deaths, advancements, command logs, and console output.
- A live Discord console can show colorized server logs and optionally accept server commands. The
/consoleslash command includes autocomplete based on commands currently available on the Minecraft server. - Executed commands can be logged to Discord, with configurable filters and automatic protection for commands containing passwords or private messages.
- Configurable bot presence can show the current online player count.
- ANSI colors can be used for clearer Discord chat, notifications, and console messages.
- Webhook messages can optionally be relayed into Minecraft, while Paradigm always ignores its own webhook to prevent loops.
- Added configurable hover cards for player names in chat. They can show the player's group, world, ping, or any other supported placeholder.
- Added configurable click actions for player names, including suggesting commands such as
/msg <player>. - Added permission-based player-name hover variants for staff and other groups.
- Added
{player_world},{player_dimension}, and{player_ping}placeholders. - Added a Player Name section to the dashboard Chat Editor, including hover lines, click actions, placeholder selection, validation, and a live preview.
- Added
/groupchat cancelreq <group>so players can withdraw pending group join requests. - Added network-aware dashboard management for MySQL-backed Paradigm networks. Servers sharing the same network can be viewed and configured from one dashboard, with separate network and server scopes, inheritance, status tracking, and safer revision-based synchronization.
Changes
- Command and module toggles now update the live command tree. Disabling a command such as
/flyno longer requires a restart, and Paradigm only releases command names it actually owns so vanilla and other mods remain untouched. - Custom commands reload more predictably and no longer take command names already used by another provider. Simultaneous dashboard edits are also serialized to prevent one update from overwriting another.
- Chat rendering is now shared across all supported Fabric, Forge, and NeoForge versions for more consistent behavior.
- Configuration and player-data files are saved more safely. Damaged JSON files are preserved before Paradigm creates a replacement.
- Telemetry, update checks, dashboard operations, and database-backed command suggestions now keep slow work away from the Minecraft tick thread.
- Home and warp autocomplete uses a short-lived background cache instead of querying remote storage whenever a player presses TAB.
- Teleport warmups now resolve the player again and re-check access before completing homes,
/back, spawn, warps, RTP, and teleport requests. - Stale mention data and group join requests are cleaned up when players leave or groups are removed.
- Discord delivery, presence updates, console handling, reloads, and shutdowns are more resilient.
Fixes
- Fixed
/sudoexecuting commands with console authority instead of the selected player's real permissions. - Fixed legacy
playerdata.jsonbeing imported again after a successful migration and potentially replacing newer player data. - Fixed player chat disappearing from the Minecraft console when custom chat formatting was enabled.
- Fixed muted messages reaching Discord even though they were blocked in Minecraft, and fixed mute bypasses through routed chat channels.
- Fixed player-supplied formatting tags being interpreted in public chat, private messages, SocialSpy, group chat, and mention notifications.
- Fixed mention cooldowns being bypassed by some permission holders.
- Fixed permission checks occasionally reading partially updated data while permissions were being changed.
- Fixed permission resets and group deletion leaving hidden assignments behind that could return after a restart or after recreating a group.
- Fixed SQL storage rejecting multiple assignments of the same group when their context or expiry differed.
- Fixed interrupted MySQL and MariaDB schema upgrades becoming stuck on the next server start.
- Fixed punishment cache refreshes briefly exposing empty or outdated ban, mute, jail, or IP-ban data.
- Fixed several jail, unjail, unmute, and punishment-history consistency problems, including safer rollback when saving or teleporting fails.
- Fixed several moderation and punishment-history commands doing storage work directly on the server thread.
- Fixed dashboard moderation actions accessing live Minecraft player state from a dashboard worker thread.
- Fixed dashboard login tokens being redeemable twice during simultaneous requests and strengthened request-size, origin, localhost, and rate-limit handling.
- Fixed Discord worker reloads potentially losing queued messages or starting a second worker before the previous one stopped.
- Fixed telemetry network requests potentially freezing the Minecraft thread for several seconds.
- Fixed shutdown races that could run storage work after its resources had already closed.
- Fixed one malformed audit-log line making the remaining valid history unreadable.
- Fixed JSON repair occasionally leaving a character from a removed block comment behind.
- Fixed unloaded holograms bypassing their normal cleanup path.
- Internal event-listener failures are now reported instead of being silently ignored.
Compatibility
- Existing configuration files remain supported. New settings are added with safe defaults when their configuration is loaded.
- The Discord module is disabled until it is configured, and optional notification types remain off by default where appropriate.
- Discord server and restart messages fall back to the general notification channel unless a dedicated server channel is configured.
- If Discord webhook permissions are unavailable, chat automatically falls back to the normal bot identity without taking over unrelated webhooks.
- Existing chat formatting remains unchanged when player-name hover and click actions are disabled.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:s4i32SJd:O9X0tkAn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:s4i32SJd:O9X0tkAn"
}

