Links
Tags
Creators
Details
1.2.1
Compatibility
Changes
๐ ShadowCrestModeration โ v1.2.1 (Integrated Release)
This release includes all changes since v1.1.0.
v1.1.1 was an internal development version and was not released separately.
โจ New Features
๐ซ Fully Reworked Ticket System
Complete GUI-based ticket workflow
Step-by-step ticket creation (category โ target โ additional info)
Ticket cooldown and max-open-ticket limits
Staff ticket overview with pagination
Ticket detail GUI with:
Claim / Unclaim
Teleport to ticket creator
Close ticket via GUI with predefined reasons
Ticket status system (OPEN, CLAIMED, CLOSED)
Automatic staff notifications
๐ฌ Private Ticket Chat
Private chat between ticket creator and supporter
/t <message> to reply to the active ticket
Toggle mode for ticket chat
Automatic chat disable when ticket is closed
Safe session handling and validation
โก Ticket Actions GUI
Perform moderation actions directly from a ticket
Warn
Kick
Tempban (1h / 1d)
Permanent ban
Default reason: Ticket
Clean separation between:
Ticket detail GUI
Ticket actions GUI
Fully language-driven (de_DE / en_US)
๐งโ๐คโ๐ง Internal Team Chat
Internal staff-only chat
/teamchat โ toggle mode
/teamchat <message> โ one-time message
Permission-based access
Custom chat format via language files
Independent from ticket chat
๐ Improvements
GUI-first design (fallback chat commands removed)
Robust GUI detection using PersistentDataContainer
Cleaner code structure for ticket & chat systems
Unified black GUI borders for all ticket-related GUIs
Modular GUI and listener architecture
Fully localized messages (German & English)
๐ Bug Fixes
Fixed GUI click detection issues
Fixed ticket chat sessions not closing properly
Fixed NPEs with offline or unknown players
Fixed missing language keys
Fixed duplicate listeners
Fixed ticket claiming edge cases
Improved permission checks for staff actions
๐ Notes
Version 1.1.1 was used internally during development and is fully included in this release.
No migration steps required from v1.1.0.
Configuration and language files are backwards compatible.
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:hFgnjAsI:2bJ5GHdo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hFgnjAsI:2bJ5GHdo"
}

