Tags
Creators
Details
1.4.0
Compatibility
Changes
š Join Our Discord for Giveaways & Events! š®
Join our Discord Server š for monthly giveaways & events where you can win coupon codes or plugins like AstralSwords Premium or TrimBlades! šØš
FaithBreak v1.4.0
Release Date: February 23, 2026
šÆ Summary
Player modes update ā choose between Kick, Reminder, or Opt-Out with persistent preferences, a smarter kick screen, and tab completions.
Changes
- š§ Player Modes System ā Three distinct modes: Kick (default), Reminder (chat-only), and Opt-Out
- š§
/muslim [kick|reminder]Command ā Opt in and select your preferred prayer time mode - š§ Smart Kick Screen ā Kick screen now displays current mode and how to switch to Reminder or Opt-Out
- š§ Tab Completions ā
/muslimcommand now suggestskickandreminderon Tab - š§ Persistent Mode Storage ā Player modes saved to
playerdata.yml, survives restarts - š§ Auto-Migration ā Old
optout.ymldata automatically migrated to the newplayerdata.ymlsystem - ā” Null Safety ā Added location null checks to prevent potential crashes in
kickPlayerForPrayer
Commands
| Command | Permission | Default |
|---|---|---|
/muslim |
faithbreak.use |
true |
/muslim kick |
faithbreak.use |
true |
/muslim reminder |
faithbreak.use |
true |
/non-muslim |
faithbreak.use |
true |
/fb lang [code] |
faithbreak.use |
true |
/fb kick <prayer> |
faithbreak.admin |
op |
Compatibility
- Paper/Spigot 1.21.x ā
š„ļø Need a Server?
š Looking for reliable Minecraft hosting? Check out Atlass Hosting ā affordable, fast, and perfect for running FaithBreak! ā”
š¬ Got suggestions or found a bug?
Jump into Discord and let me know!
ā Support Me on Ko-fi
If you like my work, consider buying me a coffee:
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:Jghhg4Vq:SDf5TJu8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Jghhg4Vq:SDf5TJu8"
}

