1.0.2
Compatibility
Changes
PixelControl v1.0.2
š Stability & Bug Fix Update
**This update focuses on improving plugin stability, fixing GUI interaction issues, improving Discord synchronization, and resolving startup problems reported in v1.0.1. **
⨠Fixed
- Fixed GUI buttons not responding when clicked.
- Fixed punishment menu interaction issues.
- Fixed history menu interaction issues.
- Fixed GUI event handling and listener registration.
- Fixed Discord Staff Chat synchronization problems.
- Fixed Discord ā Minecraft staff message delivery.
- Fixed JDA listener registration issues.
- Fixed multiple startup and initialization issues.
- Fixed bStats startup crash when metrics were enabled.
- Improved plugin loading reliability.
š§ Improvements
- Improved GUI performance and responsiveness.
- Improved Discord communication handling.
- Improved startup diagnostics and logging.
- Improved event registration system.
- Improved overall plugin stability.
- Improved error detection and debugging.
š”ļø Moderation Systems
- Reviewed punishment system functionality.
- Reviewed history tracking system.
- Reviewed staff communication systems.
- Improved synchronization between Minecraft and Discord.
- Improved punishment logging reliability.
ā” Performance
- Reduced unnecessary startup errors.
- Improved manager initialization order.
- Optimized listener registration.
- General code cleanup and optimization.
š Compatibility
- Paper 1.20.1 ā Latest Supported Paper Version
- Java 21
- SQLite
- JDA Discord Integration
- LuckPerms
- PlaceholderAPI
Thank you for using PixelControl ā¤ļø More updates and new moderation features are planned for future releases.
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:zH93Otl8:f4zPAfmb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zH93Otl8:f4zPAfmb"
}

