Tags
Creators
Details
2.1.0-BETA
Compatibility
Changes
Minecraft 26.3 support.
26.3 inserted three new packets, which shifted the team packet that glowing rides on from id 109 to 111. Every earlier build is refused by PacketEvents on 26.3 and disabled on startup.
Tested on a real Paper 26.3 server: the plugin enables cleanly, all glow teams are created and parsed correctly by the client, setting and clearing colours works, and the red/blue correction for clients on 26.1 and newer behaves as it should.
Why BETA: PacketEvents has the 26.3 support merged but has not released it yet, so this build bundles the official snapshot. Nothing in GlowAPI itself changed. The next version will be a normal release built against the PacketEvents release, with no further changes.
On 26.2 and older, 2.0.1 keeps working.
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:dyy71SJC:wZ2luf1L"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dyy71SJC:wZ2luf1L"
}

