Tags
Creators
Details
1.4
Compatibility
Changes
π FGF Hero β Version 1.4 Changelog
π Major Reward System Improvements
π₯οΈ Console Winner Commands
The game-end reward system has been completely reworked! You can now configure reward commands to be executed directly by the Console instead of the player.
π― New Placeholder Support
Added support for the new placeholder:
{winner}β Targets the winning player directly
Perfect for commands such as:
- Teleporting winners β
/mvtp {winner} Hub - Economy rewards
- Custom plugin integrations
π§Ή Cleaner Configuration
Removed outdated and redundant win-command sections from config.yml to improve readability and simplify setup.
π Visual Enhancements
ποΈ Spectator Identification
Players in Spectator Mode inside the active game world are now marked with a Skull Icon (\uE003):
- In the TAB list
- Above player heads
β οΈ Requires a matching character definition in your Resource Pack font (default.json).
β οΈ Important: The icon display inside the TAB list will not work if the plugin TAB is installed, as TAB overrides the default player list formatting.
π§© PlaceholderAPI Expansion
Added powerful new placeholders for integrations with plugins like TAB, scoreboards, and custom displays.
β€οΈ %fgfhero_hearts_display%
Displays:
- Purple/Gold hearts for alive players
- Red Skull icon for spectators
π %fgfhero_status%
Returns the current player state:
- Lobby
- Spectator
- Eliminated
- Linked Life
- Alive
π οΈ Bug Fixes & Maintenance
β Stability Improvements
Fixed a compilation issue related to team kick-vote data structures.
β¬οΈ How to Update
-
Replace your old
.jarfile with the new version -
Update your
config.ymlwith the newgame_end_settingssection- or let the plugin generate a fresh config automatically
β€οΈ Thank You
Thank you for using FGF Hero! π
Optional dependencies
Known incompatibilities
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:ksbanXU8:EuPDgYUe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ksbanXU8:EuPDgYUe"
}

