Tags
Creators
Details
1.3.0
Compatibility
Required content
Changes
NOTE
This is the last Trident version that will be released for 1.21.11. Going forwards, all new Trident releases will be made exclusively for 26.1.2
✨ What’s New?
-
Chatroom Lock
- Shows buttons for switching between pinned Chatrooms above the chat input, acting as a "channel"
- You can pin/unpin a Chatroom by middle-clicking it inside the Social menu
-
Enhanced Compact Infinibag
- When enabled, item quantities greater than 99 are displayed in a shortened format if the "Compact Infinibag" option is enabled in the server settings.
-
Supplies Module
- Added support for stacked augments
-
Wayfinder Module
- Removed the FULL variant of the module in favor of the compact one
-
Questing Module
- With the addition of Total Quest Progress on MCC Island, you will now be able to see the actual remaining progress for your quests.
🐛 Bug Fixes and Misc.
- Updated to 26.1.2 by @Moralts (1.21.11 version available as well)
- Fixed the wrong link being attached to the missing API Token message
- Fixed killfeed messages not disappearing if the user had an assist
- Fixed a typo in a death message that caused it not to appear in the killfeed
- Fixed quest lock not working without the Questing module enabled
- Changed the appearance of chat switcher buttons
- Fixed a client crash when Discord IPC is not connected by @Moralts
- Fixed other Discord IPC issues
- Fixed a game crash when hovering over the "Overlay type" option in the config while on the main screen
- API Provider will no longer automatically switch to "Token" when Trident Web is unavailable
- Removed the "An error occurred while handling your current screen" message from chat
New Contributors
- @Moralts made their first contribution in https://github.com/pe3ep/Trident/pull/66
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:L6RCcsrd:f79vB3Wd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:L6RCcsrd:f79vB3Wd"
}

