Tags
Creators
Details
All versions
1.15.1
Release
FlectonePulse 1.15.1 Fabric3 hours ago 6
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.4
Platform
Fabric
Supported environments
Dedicated servers only
Required content
Any compatible version
Changes
โจ Features
- Added the
uniformmodule, which intercepts text sent by the server to the client and formats it like FlectonePulse messages. Each type can be enabled separately - Added the
refreshoption to the nameplate, scoreboard, serverlink and tab.playerlistname modules. It sets the internal cache reset interval for sent data. The cache prevents rebuilding and resending the same data every tick, and resetting it lets FlectonePulse pick up changes from other plugins - Added the
max_lengthoption to the padding module, it limits the final padding length - Added the
%flectonepulse_format_<text>%placeholder to PlaceholderAPI, it returns a MiniMessage string formatted like a FlectonePulse message so other plugins can use it - Added the
MessageFormattedEventto the API, it fires after a message has been rendered and lets you replace the ready component or cancel the display - Added the
hasTag(String)method toMessageContextin the API, and abuild(EventMetadata, MessageContext)overload toMessagePipeline - Added the
getFPlayerFromDatabase(UUID)method toFPlayerServicein the API, it reads a player straight from the database, bypassing the cache
๐ง Refactors
- Reworked the message parser: instead of MiniMessage, a custom implementation inspired by QuickMiniMessage is now used. Compared to 1.15.0, in a test with 30 bots and 20 messages/sec, CPU load is now ~50% lower, memory allocation is ~80% lower, and message formatting load is ~90% lower
- Moved the message UUID from
MessageContexttoEventMetadata MessageFormattingEventnow carriesEventMetadata- Message modules are split into public interfaces and implementations, which makes them easier to use from the API
- Added caching for tag arguments and simplified the lazy resolvers, so repeated arguments are no longer parsed again
- Player quit now clears nameplate, serverlink, sidebar and scoreboard value data
- Added offline UUID resolution for players in Hytale
- Bubble now splits long messages into parts while keeping styles and objects, not just text
- The player skin is now updated once, and the profile and head properties are brought to the current format
๐ Bug Fixes
- Fixed
player_headon different Minecraft versions, the head properties are now resolved through reflection - Fixed the bounds when reading the display name and constant indexes
- Fixed placeholder handling in replacement, values are now rendered through tag resolvers
- Replacement now keeps the original text when a replacement fails
- Fixed the padding length cap
- Fixed sidebar removal when a player quits
- Fixed scoreboard objective removal when a player quits
- Fixed the scoreboard value name
- In moderation, duplicate bans and mutes now return early, and ids and pages are parsed through
NumberUtils - Fixed the receivers and action shown in spy messages
- The Hytale tick task is now cancelled on disable
- Fixed Fabric placeholder parsing for PlaceholderAPI
- Fixed the head text visibility rule
- Fixed the permission names of the
spritecommand andauto.announcement, they used to point tospyandauto.sound - The online status of a player is now correctly cleared and saved when they disconnect from the proxy
- Added the
<head>alias for<player_head> - Fixed grammar mistakes in the English localization:
he ignore you,unmuttedandwarned a
๐ฆ Dependencies
- Gradle updated to v9.9.1
- Fabric Loom updated to v1.19.4
- Jackson Dataformat YAML updated to v3.3.0
- Jackson Annotations updated to v2.23
- Netty Buffer updated to v4.2.20.Final
- DeepL updated to v1.18.0
- Hytale Server updated to 0.7.7
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:WiUMnQfl:ikHIdkUs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:WiUMnQfl:ikHIdkUs"
}

