Tags
Creators
Details
Licensed MIT
Published 8 months ago
Updated 7 months ago
All versions
1.0.1
Release
ProgressionAPI 1.0.17 months ago 303
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.x
Platform
Paper
Changes
Initial Release
- Bukkit ServicesManager-based service locator pattern for all cross-plugin communication — no hard compile dependencies required
- ProgressionSkillApi — award XP (addXp, addXpPartyShare), query skill level, check skill ownership
- ProgressionXpEvent — cancellable Bukkit event fired on every XP gain; carries player, skill name, amount, and partyShare flag
- EconomyApi — mint physical coin items, give coins directly to player inventory (overflow drops to ground), check if an ItemStack is a valid coin, read coin value from PDC
- HologramApi / HologramServices — create, update, and delete Hologram objects composed of HologramLine entries
- NpcApi / NpcServices — inter-plugin NPC lookup and management bridge
- PartyApi / PartyServices — party membership queries and XP distribution bridge
- QuestInfo DTO — immutable quest data transfer object with fields for ID, name, NPC binding, active state, repeat/cooldown settings, prerequisite quest list, task description, loot, XP reward, coin reward, and item rewards; both JavaBean getters and record-style aliases provided
- QuestInfoProvider / QuestInfoProviders — service point for publishing and querying quest data across plugins
- CustomItemService / CustomItemServices — register and resolve custom item types by PDC key
- ItemIdentityService / ItemIdentityServices — canonical item identity resolution across multiple providers
- TutorialProvider / TutorialProviders — standard integration point for tutorial step injection
- EnchantType / ProgressionEnchantAPI — custom enchantment registry and lookup bridge
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:Q9Ic4CqY:QsWD2kV9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Q9Ic4CqY:QsWD2kV9"
}

