Tags
Creators
Details
Licensed GPL-3.0-only
Published last year
Updated 2 weeks ago
All versions
4.3.3
Release
KoolSMPCore 4.3.32 weeks ago 20
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
What's Changed
- update to 4.3.3 by @gamingto12 in https://github.com/KoolFreedom/KoolSMPCore/pull/4
If you don't want to read the Pull Request, here's a rundown of what changed:
- Moved to a new command system (Brigadier).
- Removed the AntiSpamService class as it just never worked.
- Anyone with the
kfc.adminpermission now gets notified when the text filter gets triggered. - Permanent bans can now be removed only from the console as the
bans.ymlfile no longer exists, so it is impossible to manually remove permbans. - Organized some packages a little bit
- Reworks freeze, adds a PlayerFreezeEvent.
- Removes the AutoUndoManager
- Adds durations and reasons to mutes
- The banlist now displays more information about the ban (name, duration, reason).
- Fixed a random bug with /kick that caused the plugin to throw errors to console
- Fixed an issue with the
/orbitcommand that would spam console whenever someone had any potion effect. - Made sure that the UpdateChecker actually replaces the old jar with the new jar, how I managed to mess that up is beyond me.
- Addresses a very old TODO that was in the DiscordSRVIntegration class.
- Adds more exploit patches to the ExploitListener, also creates a ExploitPunisher class along with exploit events that the punisher calls. This adds a new hardcoded group called the "Exploit Guard", this fires an AdminChatEvent when a exploit protection event gets triggered.
- Fixes build property issues
- Running
/koolsmpcorewith no arguments now displays a nicer looking message. - Adds better contributing rules.
As always, make sure you update your configuration file if any new config values were added. If there are any bugs or other issues with the plugin, please let us know in the appropriate channels.
Full Changelog: https://github.com/KoolFreedom/KoolSMPCore/compare/4.3.2...4.3.3
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:FeHUejBl:dplOEopE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:FeHUejBl:dplOEopE"
}

