Tags
Creators
Details
0.1.1-beta.2+spigot
Compatibility
Changes
SpectraEvents 0.1.1-beta.2
Release date: 2026-10-08 Channel: Beta Java: 25 Environment: Dedicated server
Beta status
This is a public beta, not a final release. Its purpose is to make the plugin and its official client assets discoverable while Modrinth reviews them. Configuration, authoring and command contracts may still evolve within the beta line. Operators should test on a staging server and keep a backup of their SQLite data before upgrading a production server.
Downloads and compatibility
| Server | Minecraft | File | Modrinth version |
|---|---|---|---|
| Paper, Purpur | 26.1–26.3 | SpectraEvents-0.1.1-beta.2-paper.jar |
0.1.1-beta.2+paper — Paper and Purpur |
| Folia | 26.1–26.2 | SpectraEvents-0.1.1-beta.2-paper.jar |
0.1.1-beta.2+folia — Folia only |
| Spigot, CraftBukkit | 26.1–26.3 | SpectraEvents-0.1.1-beta.2-spigot.jar |
0.1.1-beta.2+spigot — Spigot and Bukkit |
Folia 26.3 is intentionally not supported by this beta. The Paper-family JAR refuses startup on that runtime before initializing SpectraEvents or touching event data, and tells the operator to install a newer release when support returns.
Resource packs
Release automation publishes the following independent client ZIPs to the separate SpectraEvents Assets Modrinth project before publishing the plugin distributions. They are not interchangeable:
| Client release line | File | Modrinth version |
|---|---|---|
| 26.1 | spectraevents-profile_26_1.zip |
0.1.1-beta.2+26.1 |
| 26.2 | spectraevents-profile_26_2.zip |
0.1.1-beta.2+26.2 |
| 26.3 | spectraevents-profile_26_3.zip |
0.1.1-beta.2+26.3 |
The server selects the matching release-line pack only when an administrator configures the
official Modrinth resource-pack project in resource-pack.yml. Player delivery remains disabled by
default until real-client acceptance is recorded for the exact hosted ZIP and client profile.
Highlights
- Fresh install → bundled Metin template → validation → start → restart recovery is covered by a real-server workflow.
- Meteor, Airdrop, Metin, Piñata and Boss Portal remain data-driven reference definitions using the shared engine rather than event-specific systems.
- Bundled Blockbench sources are validated as vanilla-compatible cuboid geometry before startup.
- Resource-pack generation is deterministic and emits a separate profile for each supported client release line.
Verification
The release candidate is verified by ./gradlew clean check build, release-artifact checks, all
three resource-pack profile builds, and the required real-server lifecycle, cleanup and restart
recovery matrix before publication.
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:WhwKe8Qt:kQVpC11T"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:WhwKe8Qt:kQVpC11T"
}
