Links
Tags
Creators
Details
1.1.3
Compatibility
Changes
🎉 Custom Commands v1.1.3 - Critical Bugfixes
🐛 Bug Fixes: Folia Command Execution & Command Registration
Fixed two critical bugs that were preventing commands from working properly!
🔧 What Was Fixed
1. Folia Command Execution Error
- Error:
NoSuchMethodException: io.papermc.paper.threadedregions.scheduler.GlobalRegionScheduler.get(org.bukkit.plugin.Plugin) - Issue: Commands failed to execute on Folia 1.21.11 servers due to incorrect API method usage
- Fix: Updated to use the correct Folia API:
Bukkit.getServer().getGlobalRegionScheduler().run(Plugin, Consumer<ScheduledTask>) - Impact: This bug only affected Folia 1.21.11+ servers - Paper servers were not affected
2. Command Registration Failure
- Issue: Custom commands weren't registering at all - commands like
/discordor/websitedid nothing - Symptoms: No errors in console, but commands simply didn't work
- Fix:
- Fixed command registration logic to properly handle aliases
- Improved command cleanup before registration (prevents conflicts)
- Added better debug logging to track registration issues
- Impact: This bug affected all server types - Paper and Folia
✅ What This Means
- ✅ Commands now execute correctly on Folia servers
- ✅ Commands now properly register and work as expected
- ✅ Better error handling and debug logging for troubleshooting
- ✅ No changes needed to your configuration
- ✅ All existing features work as expected
📦 Installation
Simply update to v1.1.3 - your configs work exactly as before!
Full Changelog:
- Fixed
NoSuchMethodExceptionwhen executing commands on Folia 1.21.11+ servers - Updated Folia API usage to
Bukkit.getServer().getGlobalRegionScheduler().run(Plugin, Consumer<ScheduledTask>) - Fixed command registration failure - commands now properly register
- Improved alias handling - commands work correctly with aliases
- Added better debug logging for command registration
- Improved command cleanup before registration to prevent conflicts
- Enhanced error messages for better debugging
Need help? Join our Discord
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:XRwXgh5o:ouVCp6RL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XRwXgh5o:ouVCp6RL"
}

