Legacy Attribute Field Guide - Herbertofury/Advent-of-Ascension GitHub Wiki
Legacy attribute field guide · 1.12.2
485 source-mapped entities · 2,221 resolved literal getter values. Search by creature name, registry ID or source class; filter by source category; sort by base health or melee value. Each card includes a source-model portrait where available and expandable getter provenance.
What is measured
The reader inspects the official AoA 3.3.6 class files without launching Minecraft or a JVM. It follows the artifact's actual superclass names and accepts only a single literal numeric return, optionally with a supported numeric widening conversion. A nonliteral or abstract override stops resolution; the reader does not incorrectly substitute a parent value. Each result identifies its declaring class, SHA-256, method descriptor and inheritance depth.
The fields cover max-health, melee, projectile, armour/armor, movement-speed and knockback-resistance getters. Spawn-chance-factor getters are included in the detailed evidence, without treating a factor as a percentage. If differently named armour or movement getters disagree, the interface reports multiple getters rather than silently choosing one. Missing, nonliteral and zero are distinct states.
Full artifact getter evidence · Compact viewer data
Base values are not final in-game attributes
Configuration, difficulty logic, attribute modifiers and encounter state can change actual results. For example, AoAMeleeMob applies hardcore-mode multipliers of 2× max health, 1.5× melee damage and 1.25× armour in its attribute setup. This example must not be blindly applied to every unrelated base class.
Movement values are attribute scalars, not travel speed in blocks per second. Projectile getters may be dynamic. A source category such as mobs or animals is a code organization label, not a complete spawn biome or behavioral classification.
Verified examples
- Creep Cow: literal base-health getter 20 and movement getter 0.2 in the artifact.
- Shadow: literal base-health getter 0.5. It has no invented body portrait; its card links to the particle/invisible-body explanation.
- All 485 cards passed construction tests. Search, health sorting, pagination and missing/nonliteral/conflicting-getter cases were tested locally. The deployed browser also passed Creep Cow search/value checks, Shadow’s no-body handling, boss-category health sorting and pagination from 36 to all 65 matching bosses.
Artifact-backed loot inspection
Each creature card has an on-demand loot panel. The extracted AoA 3.3.6 artifact contains 517 bundled loot tables; 432 of the 485 creature records have a fixed, verified table binding. The remaining records explicitly distinguish dynamic getters, null getters and getters outside the inspected AoA classes. A null getter does not prove that a creature has no custom drops.
Open a panel to inspect pool rolls, entry weights, nested tables, conditions and functions, alongside the exact resource path and SHA-256. Nested tables expand only when requested and recursive references are guarded. Weights are not drop percentages. No probabilities are invented from unevaluated conditions, looting, custom functions or runtime events.
For example, Creep Cow’s artifact table includes leather and beef pools, count and looting functions, and a conditional furnace-smelting function when the entity is on fire. The viewer preserves these exact definitions instead of flattening them into misleading guaranteed drops.
The approximately 507 KB loot dataset is fetched only when a panel is first opened, shared across all cards, and retryable after a failed request. Local tests render all 517 tables and exercise all 485 binding records, caching and failure recovery. Download the evidence dataset.
Performance and scope
The viewer loads one approximately 240 KB data file and builds a search index once. It initially creates 36 cards, with more on request; images load lazily. The incremental pagination update appends new cards instead of rebuilding existing ones, preserving open evidence panels. Repeated filtering does not rescan game files or refetch the evidence dataset. The larger provenance JSON remains available separately for inspection.
These records cover source-mapped entities with the selected getter methods. They do not certify a complete runtime entity registry, final stats, spawn probabilities, AI, loot chances, converted gameplay or multiplayer behavior. Portraits remain version-scoped reference renders.