All versions
v4.5-PLUGIN
Release
ScreentextPlugin v4.55 hours ago 3
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
1.21.11
1.21.8
1.21.4–1.21.5
1.21.1
1.20.4
1.20.1
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
ScreenTextPlugin 4.5
New Features
- Background textures:
/stp display,/stp timerand/stp counternow support the newbackgroundtextureoption, with its ownbgopacityandbgscale. - Texture path autocomplete: when typing a texture path, Tab suggests the textures found in the target player's client (or every online client for
@a). - Placeholders for the new client: placeholders the client can resolve are now sent to it, so they update every frame. Server-only placeholders (TPS, statistics, bed spawn, op status...) are still resolved by the plugin.
- Updated
placeholders.txt: every placeholder is now marked as client or server only. - Wider compatibility: one plugin jar for Spigot and Paper servers from 1.20.1 to 26.2, compatible with Fabric, Forge and NeoForge clients.
Persistence Improvements
- Displays removed with
@aare now also removed for players who were offline, once they join. - Finished timers no longer start again when a player rejoins.
- Timers are sent with their real remaining time when a player joins, staying in sync with other players.
- Paused timers stay paused after rejoining.
- Global timers are saved and restored after a server restart.
@acommands now work and are saved even when no players are online.
Fixes
- Fixed live placeholder updates resetting timers for players who joined after the timer started.
- Fixed old placeholder templates still updating after replacing a display with the same ID.
- Fixed health, armor and attack placeholders on newer server versions.
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:YRoxkhTS:S8IWlf1m"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YRoxkhTS:S8IWlf1m"
}

