Links
Tags
Creators
Details
2.0.0
Compatibility
Changes
ParticleText v2.0.0
Particle Text v2.0.0 is a complete modernization of the plugin for current Paper servers. It introduces a rebuilt rendering pipeline, persistent renderer management, richer customization, and a cleaner administration experience.
Highlights
- Rebuilt with Java 25.
- Render persistent text with configurable particles, fonts, scale, inversion, enabled state, position, and three-axis rotation.
- Create and manage renderers through commands or the interactive inventory menu.
- Resolve PlaceholderAPI values inside renderer text and use the native
particletextexpansion.
Performance and reliability
- Cache bounded text point clouds and rebuild them only when renderer content changes.
- Filter viewers by distance and limit particle density with configurable sampling and point caps.
- Coordinate rendering through a single shared scheduler.
- Persist renderer definitions in a human-readable
renderers.ymlfile.
Configuration and integrations
- Use Adventure MiniMessage and hex colors throughout configurable messages.
- Reload cached settings, messages, renderer data, and render tasks with
/pt reload. - Includes bStats metrics, asynchronous update checks, and compatibility with popular world-management plugins.
Upgrade note
This is a major rewrite targeting Java 25. Back up the existing ParticleText plugin directory and review the included configuration files before upgrading.
What's Changed
- Bump org.junit.platform:junit-platform-launcher from 1.13.4 to 1.14.4 by @dependabot[bot] in https://github.com/Despical/ParticleText/pull/2
- Bump org.junit.jupiter:junit-jupiter from 5.13.4 to 5.14.4 by @dependabot[bot] in https://github.com/Despical/ParticleText/pull/1
New Contributors
- @dependabot[bot] made their first contribution in https://github.com/Despical/ParticleText/pull/2
Full Changelog: https://github.com/Despical/ParticleText/commits/2.0.0
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:6KQ59sXK:T2LoMgIe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6KQ59sXK:T2LoMgIe"
}

