Tags
Creators
Details
0.1.0
Compatibility
Required content
Changes
✨ FrPass - Advanced Battlepass System
A next-generation, packet-based Battlepass & Quests plugin for your server.
FrPass is designed from the ground up to provide the absolute best Battlepass experience for your players without causing any server lag. By utilizing PacketEvents, all GUI interactions are handled seamlessly over the network, making it completely immune to traditional inventory duplication bugs.
⚡ Key Features
- 🛡️ Lag-Free & Safe: Zero main-thread blocking for menus. Forget about TPS drops and item dupes.
- 💎 Free & Premium Tiers: A modern, beautiful 27-slot GUI where players can claim Free and Premium rewards separately.
- 📜 Integrated Quests: Keep your server active with built-in daily/weekly quests! Reward players for mining blocks, killing mobs, or simply playing on the server.
- ♻️ Hot-Reloadable: Edit your menus, tiers, and quests on the fly. No server restarts needed!
- 🔌 Developer API: Rich API and Custom Bukkit Events (
FrPassLevelUpEvent, etc.) for other developers to hook into.
🚀 Commands & Permissions
/frpass- Opens the main Battlepass interface. (No permission required)/frpassadmin reload- Reloads all configuration files. (frpass.admin)/frpassadmin addxp <player> <amount>- Add XP to a specific player. (frpass.admin)/frpassadmin setpremium <player> <true/false>- Grant Premium Pass access. (frpass.admin)
🧩 Placeholders
FrPass has native PlaceholderAPI support!
%frpass_level%- Current tier%frpass_xp%- Current XP progress%frpass_is_premium%- 'Yes' or 'No'%frpass_premium_status%- Fully customizable formatted text
Dependencies: FrPass requires PacketEvents to function. Vault and PlaceholderAPI are highly recommended.
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:NRhQvAdJ:bgJhtaRU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NRhQvAdJ:bgJhtaRU"
}

