Links
Tags
Creators
Details
Licensed MIT
Published last year
Updated 3 months ago
All versions
0.1.1
Release
PlayerGrowth 0.1.13 months ago 15
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Purpur
Changes
New features
- Gradual growth over played time, from a configurable minimum to a gender-aware maximum, linearly interpolated — driven by actual minutes played, not wall-clock time, and pausable while a player is boxed in by solid blocks.
- Fixed or randomized growth duration. A single configured duration for everyone, or (if a min/max range is set) a random per-player target assigned on first join and persisted across restarts.
- Configurable gender types. Add, rename, or alias as many gender types as needed, each with an independent max height cap, or disable the system entirely for one shared cap.
- Manual height overrides, settable by a player for themselves or by an admin for another player, which take precedence over the growth curve until removed.
- Optional cross-server sync, relaying custom-scale and gender changes between backend servers on a proxied network sharing one database, so changes apply immediately instead of only after a reconnect.
- Configurable storage: H2 (default, zero setup), MySQL, MariaDB, or plain YAML.
- PlaceholderAPI integration, expanded over the course of this rewrite
from 5 to 14 placeholders — current/min/max height (meters and raw
scale), gender, growth percentage, formatted and raw time remaining, and
custom-scale status.
/papi info playergrowthnow documents all of them and shows the plugin's correct display name and author casing (PlayerGrowth/MISQZY), instead of an empty placeholder list and the raw lowercase identifier. - Localized, MiniMessage-formatted messages, bundled in English and
Russian, with more locales addable by dropping in another
messages_<locale>.yml. - FlectonePulse interoperability: if FlectonePulse is installed, PlayerGrowth reuses its server identifier automatically so the two plugins never disagree about which backend server they're each on.
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:K5BdMA2G:DyuIsvul"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:K5BdMA2G:DyuIsvul"
}

