Apothic Ascension

Changed the naming style of files since my old one kinda defeated the entire purpose of the Major.Minor.Patch format that the entire industry pretty much agreed was perfect, my bad. But anyways;

# Apothic Ascension 1.0.0 - Beta 11.0

Due to college takingn a lot of my time, Beta 11 is primarily a stability, compatibility, and UX release. It rather intentionally does not expand the progression ladder or introduce another major content batch; the goal was to harden the systems introduced through Beta 10 before continuing development since with my tendency for feature creep, it woulda been a month before y'all saw another bugfix otherwise.

## Highlights

- Fixed Ascension rarity tooltip handling so Apothic Ascension no longer claims ordinary vanilla or third-party items.
  - Removes the unwanted `rarity: Common` line from unrelated items.
  - Stock Apotheosis rarities remain owned by Apotheosis.
  - Foreign tooltip component trees and styling are preserved instead of flattened.
  - Added Full, Compact, and Off client tooltip presentation modes, with independent rarity-label, item-name, and frame controls.
(Originally brought to my attention by JakeDaJester)

- Reworked rarity ownership checks throughout the mod.
  - Ascension rarities are now identified by registry identity rather than numeric sort index.
  - Prevents unrelated mods using similar rarity sort values from being mistaken for Ascension rarities.
  - Applies to natural generation, intrinsic scaling, Apex reforging, boss classification, diagnostics, and qualification.

- Hardened Ascension boss classification.
  - Fixed an initialization-order case where querying a boss too early could cache a permanent negative result.
  - Third-party boss metadata remains authoritative when explicitly provided.

- Major workstation transaction hardening.
  - Workstation previews are now bound to the exact component-aware input stacks that created them.
  - Input substitution, stale previews, changed costs, changed progression state, and changed reforge context cancel safely before consumption.
  - Hardened shift-click/result extraction behavior.
  - Improved handling of interrupted Apex operations, menu lifecycle changes, concurrent access, and stale block-entity references.
  - Reforge inputs, materials, rebirth sigils, XP costs, seed state, and generated offers are revalidated at commit time.
  - Cancellation does not partially consume inputs or experience.

- Codex UX overhaul.
  - Codex pages now support mouse-wheel/touchpad scrolling.
  - Text properly wraps within the reading area.
  - The progression-status line participates in the same wrapping/layout calculation.
  - Scroll position resets cleanly when changing pages.
  - Updated the Ascension Codex item texture.

- Restored the intended Apex Bench presentation.
  - Restored the authored Apex Bench and Ascension Pylon preview textures that had been accidentally omitted from the later asset set.

- Improved corrupted-data and malformed-input handling.
  - Hardened legacy player-stage and gem-grade migration.
  - Invalid persisted values clamp or fail closed instead of destabilizing progression.
  - Non-finite/overflowing attribute, affix, probability, radial, and version values are contained rather than propagating NaN/overflow state.

- Compatibility and packaging cleanup.
  - Audited strict Apotheosis mixin contracts across supported Apotheosis 8.5.4, 8.6.0, 8.6.1, and 8.7.0.
  - Audited all 95 resources intentionally shipped under the `apotheosis` namespace.
  - Hardened optional Ars Nouveau, Iron's Spells 'n Spellbooks, Spartan Weaponry Unofficial, and JEI absence/version handling.
  - Corrected Iron's loader-version metadata to match its actual `1.21.1-3.x` version format.
  - Tightened release metadata and JAR resource verification.

## Content / Balance

Beta 11 intentionally makes no gameplay-datapack expansion over Beta 10.

The rarity ladder, progression stages, affix content, recipes, workstation progression, and balance data remain the Beta 10 gameplay baseline. This release is focused on making that baseline safer and more reliable before further expansion.

## For Modpack Authors

The largest compatibility change is stricter semantic ownership.

Apothic Ascension should no longer interpret another mod's rarity as an Ascension rarity merely because it happens to use the same numeric sort index. Optional integration data is also validated so absent optional mods do not become required registry dependencies.

More extensive third-party compatibility precedence and dedicated-compat yielding behavior is planned for Beta 12 rather than being rushed into this stability release.

## Release Qualification

A bit of a technical nugget for my more technically inclined users, but the final Beta 11 JAR was compiled against the real Minecraft 1.21.1 / NeoForge toolchain and passed the project's runtime-JAR integrity verifier after the final Codex and Apex asset fixes, since my test modpack is wayyy too heavy to spin up for every "does it launch" test, if you wanna know more about my toolingn specifically feel free to PM me, I don't mind sharing, I just can't spare the time to give super detailed explaination lol