MiniPlaceholders
MiniMessage Component-based Placeholders API for Minecraft Platforms
Added support for Fabric 1.21.11
- Added support to Fabric 1.21.9+
3.1.0 (10/10/2025)
Features
- feat: Sponge commands implementation
- feat: Implement parserel subcommand
- feat: Add --null argument to parse node
- misc: Added bstats metrics
Fixes
- fix: Fixed multiple loading expansions
- fix: Added nullability checks to RelationalAudience
- fix: Fixed command formatting
API Additions
3.1.0 (10/10/2025)
Features
- feat: Sponge commands implementation
- feat: Implement parserel subcommand
- feat: Add --null argument to parse node
- misc: Added bstats metrics
Fixes
- fix: Fixed multiple loading expansions
- fix: Added nullability checks to RelationalAudience
- fix: Fixed command formatting
API Additions
3.1.0 (10/10/2025)
Features
- feat: Sponge commands implementation
- feat: Implement parserel subcommand
- feat: Add --null argument to parse node
- misc: Added bstats metrics
Fixes
- fix: Fixed multiple loading expansions
- fix: Added nullability checks to RelationalAudience
- fix: Fixed command formatting
API Additions
3.1.0 (10/10/2025)
Features
- feat: Sponge commands implementation
- feat: Implement parserel subcommand
- feat: Add --null argument to parse node
- misc: Added bstats metrics
Fixes
- fix: Fixed multiple loading expansions
- fix: Added nullability checks to RelationalAudience
- fix: Fixed command formatting
API Additions
What's Changed
- Fixed Fabric initialization
- Updated minimun Sponge-API usage
Full Changelog: https://github.com/MiniPlaceholders/MiniPlaceholders/compare/3.0.0...3.0.1
What's Changed
- Fixed Fabric initialization
- Updated minimun Sponge-API usage
Full Changelog: https://github.com/MiniPlaceholders/MiniPlaceholders/compare/3.0.0...3.0.1
What's Changed
- Fixed Fabric initialization
- Updated minimun Sponge-API usage
Full Changelog: https://github.com/MiniPlaceholders/MiniPlaceholders/compare/3.0.0...3.0.1
What's Changed
- Fixed Fabric initialization
- Updated minimun Sponge-API usage
Full Changelog: https://github.com/MiniPlaceholders/MiniPlaceholders/compare/3.0.0...3.0.1
Hi! In this new version, which has been in development since February of this year, several changes have been implemented that modernize the MiniPlaceholders code base, as well as improving performance for both regular and advanced use. In addition to adding ExpansionProvider, a new convention for creating expansions in MiniPlaceholders, without the need to rely on a specific platform.
Expansion Provider
As mentioned above, ExpansionProviders have been added, which are a type of independent project that can provide an Expansion according to the configured requirements. In addition, it is multiplatform and does not require an individual initializer for each platform you want to support. If you want to see an example of its use, you can check out its wiki page or directly review a practical example in the Template Expansion.
Rewritted API Usage
From now on, an audience will not be required when obtaining placeholders. This allows for greater efficiency, as it avoids creating multiple unnecessary objects by delegating the function of providing the required audience to the parsing phase. For this reason, to use MiniPlaceholders Audience placeholders, you must include the Audience in the target field of the
MiniMessage#deserializemethod so that it can be recognized by the corresponding placeholders. In addition, you now have the ability to create type-safe placeholders by including the target class as the first argument. You can find more information about this in the wiki.Due to these changes, most projects created for MiniPlaceholders v2 are incompatible with MiniPlaceholders v3. Please be patient while your favorite projects are updated to the new version.
At the time of writing this changelog, there are more than a dozen expansions already available for MiniPlaceholders v3, such as the PlatformInfo, ProxyConnection, Player, Spark, LuckPerms, PlaceholderAdapter, Vault, and more expansions...
These new expansions, as mentioned above, are no longer installed as separate plugins/mods. Now, you simply need to place them inside the MiniPlaceholders folder in the expansions folder.
If you liked this update and would like to contribute in some way, we have pull requests available so you can contribute to this project. You can also contribute financially via PayPal or GitHub Sponsors.
Full Changelog: https://github.com/MiniPlaceholders/MiniPlaceholders/compare/2.3.0...3.0.0
Hi! In this new version, which has been in development since February of this year, several changes have been implemented that modernize the MiniPlaceholders code base, as well as improving performance for both regular and advanced use. In addition to adding ExpansionProvider, a new convention for creating expansions in MiniPlaceholders, without the need to rely on a specific platform.
Expansion Provider
As mentioned above, ExpansionProviders have been added, which are a type of independent project that can provide an Expansion according to the configured requirements. In addition, it is multiplatform and does not require an individual initializer for each platform you want to support. If you want to see an example of its use, you can check out its wiki page or directly review a practical example in the Template Expansion.
Rewritted API Usage
From now on, an audience will not be required when obtaining placeholders. This allows for greater efficiency, as it avoids creating multiple unnecessary objects by delegating the function of providing the required audience to the parsing phase. For this reason, to use MiniPlaceholders Audience placeholders, you must include the Audience in the target field of the
MiniMessage#deserializemethod so that it can be recognized by the corresponding placeholders. In addition, you now have the ability to create type-safe placeholders by including the target class as the first argument. You can find more information about this in the wiki.Due to these changes, most projects created for MiniPlaceholders v2 are incompatible with MiniPlaceholders v3. Please be patient while your favorite projects are updated to the new version.
At the time of writing this changelog, there are more than a dozen expansions already available for MiniPlaceholders v3, such as the PlatformInfo, ProxyConnection, Player, Spark, LuckPerms, PlaceholderAdapter, Vault, and more expansions...
These new expansions, as mentioned above, are no longer installed as separate plugins/mods. Now, you simply need to place them inside the MiniPlaceholders folder in the expansions folder.
If you liked this update and would like to contribute in some way, we have pull requests available so you can contribute to this project. You can also contribute financially via PayPal or GitHub Sponsors.
Full Changelog: https://github.com/MiniPlaceholders/MiniPlaceholders/compare/2.3.0...3.0.0
Hi! In this new version, which has been in development since February of this year, several changes have been implemented that modernize the MiniPlaceholders code base, as well as improving performance for both regular and advanced use. In addition to adding ExpansionProvider, a new convention for creating expansions in MiniPlaceholders, without the need to rely on a specific platform.
Expansion Provider
As mentioned above, ExpansionProviders have been added, which are a type of independent project that can provide an Expansion according to the configured requirements. In addition, it is multiplatform and does not require an individual initializer for each platform you want to support. If you want to see an example of its use, you can check out its wiki page or directly review a practical example in the Template Expansion.
Rewritted API Usage
From now on, an audience will not be required when obtaining placeholders. This allows for greater efficiency, as it avoids creating multiple unnecessary objects by delegating the function of providing the required audience to the parsing phase. For this reason, to use MiniPlaceholders Audience placeholders, you must include the Audience in the target field of the
MiniMessage#deserializemethod so that it can be recognized by the corresponding placeholders. In addition, you now have the ability to create type-safe placeholders by including the target class as the first argument. You can find more information about this in the wiki.Due to these changes, most projects created for MiniPlaceholders v2 are incompatible with MiniPlaceholders v3. Please be patient while your favorite projects are updated to the new version.
At the time of writing this changelog, there are more than a dozen expansions already available for MiniPlaceholders v3, such as the PlatformInfo, ProxyConnection, Player, Spark, LuckPerms, PlaceholderAdapter, Vault, and more expansions...
These new expansions, as mentioned above, are no longer installed as separate plugins/mods. Now, you simply need to place them inside the MiniPlaceholders folder in the expansions folder.
If you liked this update and would like to contribute in some way, we have pull requests available so you can contribute to this project. You can also contribute financially via PayPal or GitHub Sponsors.
Full Changelog: https://github.com/MiniPlaceholders/MiniPlaceholders/compare/2.3.0...3.0.0
Hi! In this new version, which has been in development since February of this year, several changes have been implemented that modernize the MiniPlaceholders code base, as well as improving performance for both regular and advanced use. In addition to adding ExpansionProvider, a new convention for creating expansions in MiniPlaceholders, without the need to rely on a specific platform.
Expansion Provider
As mentioned above, ExpansionProviders have been added, which are a type of independent project that can provide an Expansion according to the configured requirements. In addition, it is multiplatform and does not require an individual initializer for each platform you want to support. If you want to see an example of its use, you can check out its wiki page or directly review a practical example in the Template Expansion.
Rewritted API Usage
From now on, an audience will not be required when obtaining placeholders. This allows for greater efficiency, as it avoids creating multiple unnecessary objects by delegating the function of providing the required audience to the parsing phase. For this reason, to use MiniPlaceholders Audience placeholders, you must include the Audience in the target field of the
MiniMessage#deserializemethod so that it can be recognized by the corresponding placeholders. In addition, you now have the ability to create type-safe placeholders by including the target class as the first argument. You can find more information about this in the wiki.Due to these changes, most projects created for MiniPlaceholders v2 are incompatible with MiniPlaceholders v3. Please be patient while your favorite projects are updated to the new version.
At the time of writing this changelog, there are more than a dozen expansions already available for MiniPlaceholders v3, such as the PlatformInfo, ProxyConnection, Player, Spark, LuckPerms, PlaceholderAdapter, Vault, and more expansions...
These new expansions, as mentioned above, are no longer installed as separate plugins/mods. Now, you simply need to place them inside the MiniPlaceholders folder in the expansions folder.
If you liked this update and would like to contribute in some way, we have pull requests available so you can contribute to this project. You can also contribute financially via PayPal or GitHub Sponsors.
Full Changelog: https://github.com/MiniPlaceholders/MiniPlaceholders/compare/2.3.0...3.0.0
What's Changed
- feat(api): expansion metadata
- Add LegacyUtils methods to check if a string contains legacy characters
- misc: Updated to Java 21
- Updated to Cloud v2
- Finished Cloud 2 implementation
- update to 1.21.1
- 1.21.4
- build: Updated gradle to 8.12.1
- fix(docs): Fixed Dokka docs generation and updated to V2
- Added expansions subcommand
Sponsors
Now you can support the development of MiniPlaceholders with your sponsor! https://github.com/sponsors/4drian3d
Full Changelog: https://github.com/MiniPlaceholders/MiniPlaceholders/compare/2.2.4...2.3.0
What's Changed
- feat(api): expansion metadata
- Add LegacyUtils methods to check if a string contains legacy characters
- misc: Updated to Java 21
- Updated to Cloud v2
- Finished Cloud 2 implementation
- update to 1.21.1
- 1.21.4
- build: Updated gradle to 8.12.1
- fix(docs): Fixed Dokka docs generation and updated to V2
- Added expansions subcommand
Sponsors
Now you can support the development of MiniPlaceholders with your sponsor! https://github.com/sponsors/4drian3d
Full Changelog: https://github.com/MiniPlaceholders/MiniPlaceholders/compare/2.2.4...2.3.0
