1.0.3
Compatibility
Changes
PixelControl v1.0.3 - Security & Investigation Update
This update introduces major improvements to PixelControl, focusing on moderation tools, server security, staff workflow, and overall stability.
⨠New Features
- Added a complete Suspension System with GUI support.
- Added Advanced Alt Detection to help identify linked accounts.
- Added Automatic IP-Based Ban System (using the existing
/banand/tempbancommands). - Added SOS Discord Role Ping support for faster staff response.
- Added Global Player Status System across all GUIs (Online, Offline, Muted, Banned, Suspended).
- Added Suspend to the Punish GUI alongside Ban, Mute, Kick, Warn, Report, Note, and History.
- Expanded punishment history with more detailed moderation information.
- Improved staff chat by displaying staff ranks in synced Discord messages.
- Updated all new systems to fully support the complete PixelControl rank hierarchy.
š Improvements
- Improved GUI consistency and player status detection.
- Improved punishment and investigation workflow.
- Improved Discord logging and embed formatting.
- Improved performance and database handling.
- Updated compatibility with the latest supported Paper version.
š Fixes
- Fixed multiple GUI-related issues.
- Fixed player status incorrectly showing "ACTIVE" in interfaces.
- Fixed various stability and performance issues.
- General code cleanup and optimization.
ā Known Issue
Discord slash commands may occasionally return "The application did not respond." in some situations. This is a known issue and is planned to be resolved in PixelControl v1.0.4.
Thank you for using PixelControl! More moderation features, security improvements, and Discord enhancements are coming in future updates.
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:7gepmk44"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zH93Otl8:7gepmk44"
}

