[mdaffa48]

Summary

Hologram selection could probe unnecessary integrations and choose fallbacks in map iteration order. A null provider registration could also disable every server plugin.

The final behavior is:

• Use the configured provider when its plugin is installed and enabled.
• Otherwise select the first available registered provider; discover built-ins in DecentHolograms, FancyHolograms, HolographicDisplays order, stopping at the first usable one.
• Skip unavailable or broken providers. If none is available, warn and keep NextGens running without holograms.
• Ignore invalid or duplicate registrations with a warning, preserving the original provider and leaving plugins enabled.

Closes #16 when merged. Target: master.

The official API getting-started guide, checked October 18, 2026, specifies de.oliver:FancyHolograms:2.9.1. The existing dependency is unchanged. Documentation no longer infers API compatibility solely from a plugin version string.

Also add selection regression checks to CI, document behavior, update bundled configuration guidance, and align CI with the existing Java 25 POM requirement.

Verification

• ./mvnw.cmd -B -ntp -o clean verify passed.
• java scripts/HologramProviderCheck.java: 21 checks passed, covering configured selection, ordered fallback, early stop, aliases, custom providers, missing dependencies, invalid registration, and no-provider warnings. The expanded checks fail on the previous PR commit.
• GitHub Actions Build test JAR passed for b72cb9b620a1c2e4e507d864de40caedbebc69af.
• Shaded JAR contains plugin.yml; one deployable JAR remains in output.
• git diff --check passed.

In-game testing is not required for acceptance of this provider-selection change, as agreed with the maintainer. No live rendering test is claimed.

Tested artifact

• Commit: b72cb9b620a1c2e4e507d864de40caedbebc69af
• Local JAR: NextGens-1.3.5.jar, 1,517,690 bytes
• SHA-256: A55013B44B23ACBE4CB0E423DFDC8D20C50482AE3155FF8C3A6C513CA39674C8
• Java: 25, matching the current POM

Remaining risk

The regression checks exercise the real manager/interface with minimal API substitutes. Existing build warnings concern AdvancedChestsAPI LATEST, deprecated/restricted APIs, and Shade overlaps. No dependency upgrade, release, production deployment, or server restart is included.