ProgressionAPI

# ProgressionAPI When you run multiple custom plugins, the real pain is consistency: item IDs, matching logic, shared services, and “why does this behave differently here?”. ProgressionAPI solves that by being the single source of truth for your ecosystem—especially for reliable custom item identity. Less duplication, fewer bugs, cleaner updates. # Highlights: Central services for your plugin ecosystem Consistent item identity logic (spec-based workflows) Built for maintainability and clean multi-plugin setups Perfect for: servers running multiple custom Progression plugins. # Why you’ll love it One “source of truth” for your plugins Less duplicated logic = fewer weird bugs Makes updates and maintenance significantly easier # Features Central services/interfaces for ecosystem plugins Consistent item identity / spec-based workflows Clean integration layer for multi-plugin setups # Setup Install as a dependency plugin Ensure dependent plugins load after it Configure item identity/spec handling if applicable # Compatibility Platform: Paper / Spigot (Paper recommended) Intended as a dependency for Progression ecosystem plugins