1.0.0
Compatibility
Changes
π CreeperPractice v1.0
Official Stable Release
The first official stable release of CreeperPractice is here.
This update introduces a cleaner lobby experience, improved queue handling, a redesigned settings system, and major quality-of-life improvements focused on smooth gameplay and performance.
Built for competitive PvP servers that want a modern, polished, and lightweight practice experience.
β¨ New Features & Improvements
π Custom Lobby Hotbar
A fully redesigned lobby experience with dedicated hotbar utilities:
- βοΈ Sword β Queue Menu
- π Book β Kit Editor
- βοΈ Comparator β Settings Menu
The lobby system is now cleaner, faster, and more intuitive for players.
π₯οΈ Redesigned Settings Menu
The settings system has been upgraded to a centered 54-slot double chest GUI for a cleaner and more professional interface.
Benefits:
- Better visibility
- Cleaner layout
- Easier navigation
- Improved user experience
π₯ Smart Queue Logic
Queue handling has been fully improved.
Fixed issues involving:
- Message spam
- Inventory glitches
- Queue desync problems
Leaving queues is now handled with a clean and responsive 1-click system.
π Kit Editor Integration
Fully integrated hotbar support for the kit editor.
Players can now instantly access:
/kit editor- Kit management tools
- Inventory editing features
directly from the lobby hotbar.
β‘ Performance Improvements
Internal systems and event handling have been optimized to ensure:
- Smooth player experience
- Faster GUI interaction
- Better queue responsiveness
- Stable performance under load
Special focus was placed on reducing lag during:
- Player joins
- Item switching
- GUI interactions
π CreeperPractice v1.0
The beginning of a modern PvP practice experience.
More features, systems, and competitive improvements are planned for future updates.
βοΈ CreeperPractice
Competitive PvP perfected by MASTER NAMAN π
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:bFZ5GpwQ:gTgikDBF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bFZ5GpwQ:gTgikDBF"
}

