Tags
Creators
Details
2.0
Compatibility
Changes
📦 PulseEvents 2.0 — Changelog
✨ New Features
🏆 Survival Streak Rewards
Players who survive an event to the end can now build survival streaks and earn rewards.
Includes:
- survival streak rewards for players who finish events alive
- configurable reward milestones in
streak-rewards.milestones - multiple reward types:
vaultitemcustom-itemcommand
Streak resets when a player:
- dies during an active event
- leaves during an active event
📁 File-Based Custom Events
Custom events are now loaded directly from individual .yml files inside the events/ folder.
Example included event files:
meteor-shower.ymlgravity-well.ymlhot-potato.yml
Additional improvements:
- custom event chance changes are now saved back into each event file automatically
- easier event editing
- cleaner project structure
- simpler event sharing between servers
🗳️ Event Voting System
Added a new player voting GUI for choosing upcoming events.
Features:
- players can vote for the next event
- vote cost configurable via
voting.cost - automatic free voting fallback if Vault economy is unavailable
- voted events receive priority during random event selection
Voting behavior:
- voting resets when an event starts
- if multiple events tie for first place, PulseEvents uses the existing weighted random system to decide the winner
🔧 Changes
Config Structure
- removed embedded custom events from
config.yml - moved custom event configuration into separate files inside
/events - updated streak reward configuration format:
from simple numeric values → to structured entries with
mode+value
Command Updates
/pe events now behaves differently depending on permissions:
- Admins → Event Management GUI
- Players → Voting GUI
🌍 Language / Messages
Added new language messages for:
- streak reward notifications
- voting feedback
- vote success / error messages
⚠ Important Update Note
Required for updating to 2.0
Before starting the new version:
- Stop server
- Delete
/plugins/PulseEvents/ - Install PulseEvents 2.0
- Start server
- Reconfigure settings if needed
❤️ Thanks
Thanks for using PulseEvents — more updates coming soon.
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:XXcQ6J0Y:jEfEorHS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XXcQ6J0Y:jEfEorHS"
}

