Rework API

[BrainRTP]

The old AbstractMenus/api repo is now part of this one as the :api Gradle subproject. That repo will be archived shortly and no longer maintained. Going forward all API code lives here, alongside the plugin.

What changed

• API moved into this repo as :api. Maven coord stays the same: ru.abstractmenus:api:<ver>.
• New addon system. Plugins can extend AbstractMenus either as a regular Bukkit plugin (Path 1, drop into plugins/) or as a lightweight jar AM loads itself (Path 2, drop into plugins/AbstractMenus/addons/).
• New ProviderRegistry for economy / permissions / levels / placeholders / skins. Multiple providers can register at once; menus pick one with provider: "..." per action, or via a providers{} block in config.conf.
• The plugin now uses its own SPI for built-in types (CoreExtension). If something works for core, it works for addons.

Reference addon: PlayerPointsAddon (separate repo, two branches showing both paths).

Module layout

api/      - public API, published as ru.abstractmenus:api:<ver>
plugin/   - plugin implementation, ships as the shadow jar

Build outputs in build/dist/ (aggregated) plus per-module build/libs/.

New API basics

• AbstractMenusApi.get() - entry point, replaces Types.* and Handlers.* statics.
• MenuExtension - the addon contract. onLoad / onEnable / onDisable plus name/version metadata.
• TypeRegistry<T> - five of these (actions, rules, activators, item properties, catalogs). Replaces Types.register*.
• ProviderRegistry - five sections (economy, permissions, levels, placeholders, skins). Replaces the Handlers static facade.

All public types have proper javadoc.

Addon system

Two ways to ship an addon. Same runtime behaviour, different load-path.

	Path 1 (as-plugin)	Path 2 (as-addon)
Drops into	plugins/	plugins/AbstractMenus/addons/
Manifest	plugin.yml	addon.conf (HOCON)
Loaded by	Bukkit	AM AddonManager
Visible in	/plugins	/am addons

/am addons supports list, info <name>, reload <name>, load <name>, rescan. Tab completion works for all.

Provider system

Old shape: one global handler per kind. New shape: many can register, menus choose.

Resolution order:

1. Per-action provider: "..." field in HOCON.
2. Server default in config.conf providers{} block.
3. Highest-priority registered provider.

Money actions accept both forms for backward compat:

takeMoney: 100                                    # default provider
takeMoney { amount: 100, provider: "vault" }      # explicit

config.conf:

providers {
  economy      = "vault"
  permissions  = "auto"
  levels       = "auto"
  placeholders = "auto"
  skins        = "auto"
}

Core providers register at priority 50; addons typically at 100.

Build outputs

• AbstractMenus-<ver>.jar - shadowed plugin jar, drop into plugins/.
• AbstractMenus-api-<ver>.jar (+ sources + javadoc) - api artifacts.
• <root>/build/dist/ - all of the above in one place. ./gradlew shadowJar, ./gradlew assemble, and ./gradlew build all refresh it.

Breaking changes

Removed:

• ru.abstractmenus.api.Handlers -> use AbstractMenusApi.get().providers().*
• ru.abstractmenus.api.Types -> use AbstractMenusApi.get().{actions, rules, ...}()
• AbstractMenusPlugin -> use AbstractMenusApi
• AbstractMenusProvider -> use AbstractMenusApi.get()

In-tree call sites are migrated. Out-of-tree consumers need import updates.

Migration

- import ru.abstractmenus.api.Types;
- Types.registerAction("foo", FooAction.class, new FooAction.Serializer());
+ import ru.abstractmenus.api.AbstractMenusApi;
+ AbstractMenusApi.get().actions()
+     .register("foo", FooAction.class, new FooAction.Serializer(), this);

- import ru.abstractmenus.api.Handlers;
- Handlers.getEconomyHandler().takeBalance(player, 100);
+ import ru.abstractmenus.api.AbstractMenusApi;
+ AbstractMenusApi.get().providers().economy().takeBalance(player, 100);

register* now takes an extra MenuExtension owner parameter (this if your plugin implements MenuExtension).