Tags
Creators
Details
1.3.1
Compatibility
Changes
Version 1.3.1 - 2025-06-06This update introduces major configuration enhancements, a complete overhaul of the chat prefix system for better compatibility, and improved command consistency.AddedPvP Protection System Toggle: A new master toggle, pvp_protection_system_enabled, has been added to config.yml to completely enable or disable the faction PvP protection feature. It is disabled by default.When this feature is disabled in the config, the /f togglepvp command is hidden from /f help and cannot be used by players.The "PvP Protection" status line is also hidden from the /f info screen if the system is disabled.Configurable /f info Screen: A new section, who_screen_display, has been added to config.yml.This allows server administrators to enable or disable every individual line item on the /f info (or /f who) screen, providing full control over the information displayed to players.The ability to see a faction's home block coordinates (show_home_location) is disabled by default.ChangedChat System Overhaul: The internal chat prefix system has been replaced with full PlaceholderAPI integration. This is a major change that ensures GFactions prefixes work seamlessly with other chat management plugins like EssentialsXChat. Public chat formatting is now handled by setting placeholders (e.g., %gfactions_prefix% or %gfactions_tag_prefix%) in your chat formatter's configuration.Standardized Public Chat Prefix: As part of the new chat system, the default public chat prefix is now the full faction name, e.g., [MyFaction] PlayerName: message. This is provided by the %gfactions_prefix% placeholder.Claimfill Cost: The power cost for using the /f claimfill command is now directly tied to the standard claim_chunk cost, removing the separate claim_fill cost variable from config.yml for better consistency.FixedChat Prefix Conflicts: Resolved a long-standing issue where faction chat prefixes would conflict with or be overridden by other plugins. The new PlaceholderAPI-based system prevents these conflicts entirely.Claimfill Cost Consistency: Addressed an issue where the cost for /f claimfill was confusing. The cost is now identical to using /f claim for each chunk, making the command's behavior more intuitive.
Optional dependencies
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:ZnRNqaal:UwDYRn2N"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZnRNqaal:UwDYRn2N"
}

