All versions
1.1.2
Release
SlideProxy 1.1.2last month 17
Compatibility
Minecraft: Java Edition
1.21.4ā1.21.8
Platform
Velocity
Changes
What's New?
SlideProxy 1.1.2
š„ļø New Admin Panel System
- Added the new
/slideproxy panelcommand. - Added
/sp panelas a shorter alias. - The Admin Panel can now be opened directly from Velocity.
- Added the SlideProxy Bridge communication system between Velocity and Paper servers.
š SlideProxy Bridge
- Added the new SlideProxyBridge backend plugin.
- Added secure plugin messaging through the
slideproxy:mainchannel. - Velocity can now send GUI requests to backend servers.
- Added backend-to-proxy communication support.
š Backend OP Synchronization
- Added automatic backend OP status synchronization.
- OP status is synchronized when players join.
- Added continuous OP status checking while players are online.
- Supports detecting
/opand/deopchanges automatically. - SlideProxy can now use backend OP status for administrative access checks.
š§ Bridge Improvements
- Added
REQUEST_OP_STATUScommunication. - Added
OP_STATUSsynchronization messages. - Added
OPEN_GUIbridge actions. - Added support for future GUI systems such as:
- Admin Panel
- Chat Management
- Player Management
- Network Management
š ļø Improvements
- Improved communication between the Velocity proxy and Paper backend servers.
- Improved administrative command handling.
- Prepared the Bridge system for the upcoming large chest GUI panels.
- Added a stronger foundation for future SlideProxy management features.
š Coming Next
- Large Chest Admin GUI
- Player Management Panel
- Network Management Panel
- Chat Management Panel
- Server Management
- Textured Player Head Buttons
- Easier proxy administration
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:C0hLCijU:GrMCxxkd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:C0hLCijU:GrMCxxkd"
}

