Tags
Creators
Details
Licensed MIT
Published 2 years ago
Updated 2 years ago
All versions
bukkit-1.1
Release
Jawake v1.12 years ago 104
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
1.20.6
1.19.4
1.18.2
Platforms
Bukkit
Paper
Spigot
Changes
Version: 1.1
Added:
-
Reload Command (
/jreload):- A new command to reload the plugin's events and configuration without restarting the server.
- Command feedback: Displays a success message in green after reloading.
- Example feedback:
"Jawake plugin has been reloaded.""All events have been refreshed."
- Permissions required:
jawake.reload.
-
Stop Command (
/jawakestop):- Stops the
Awakeevent from triggering by unregistering the event listeners. - Command feedback: Displays a red message when the events are stopped.
- Example feedback:
"Jawake plugin events have been stopped."
- Permissions required:
jawake.stop.
- Stops the
-
Start Command (
/jawakestart):- Re-enables the
Awakeevent by re-registering the event listeners. - Sends a title and subtitle to all online players when the event is started:
- Title:
"Danger!!"(Red) - Subtitle:
"Don't sleep!!"(Yellow)
- Title:
- Command feedback: Displays a green message when the events are started.
- Example feedback:
"Jawake plugin events have been started."
- Permissions required:
jawake.start.
- Re-enables the
Changes:
- Main Class (
Main.java):- Added methods to stop and re-enable events dynamically:
plugin.reload()re-registers theAwakeevent listener.stopAwakeEvent()unregisters thePlayerJoinEventandPlayerBedEnterEventhandlers.- Updated
onEnable()to initialize and register theAwakeevent.
- Registered the new commands
/jreload,/jawakestop, and/jawakestart.
- Added methods to stop and re-enable events dynamically:
plugin.yml:
- Added command definitions for
/jreload,/jawakestop, and/jawakestart. - Added permissions for the new commands:
jawake.reload(for reloading)jawake.stop(for stopping)jawake.start(for starting)
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:15zqMNv7:8VbyvBEM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:15zqMNv7:8VbyvBEM"
}

