Skip to content

Azeroth Navigator 0.8.1

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 14 Oct 18:02
· 1039 commits to main since this release
d11853e

Azeroth Navigator 0.8.1 — local content-pack repair preview

Developer prerelease for Windows. Desktop data remains imported snapshot state;
permitted game observations remain inside the informational Lua addon.

Changes

  • Local content-pack parsing accepts the schema1 typed explicit empty
    payload.map_embeddings array as equivalent to its omitted default. The exception
    changes only comparison shape after validation; unknown/duplicate/future/malformed
    fields remain refused and original input bytes stay unchanged.
  • Existing Forever sources now have a typed schema1 registry sidecar derived from
    recorded source declarations. Unknown licenses/revisions and date-only retrieval
    times remain unknown; the owner's composite-only assertion remains conditional
    and does not grant third-party permissions.
  • The existing Forever directory can be built and verified as a local_reference
    pack. It remains distribution-ineligible and is not a release asset. Historical
    reference70205/16001, forever-atlas-r1, producer0.1 and all imagery bytes remain
    unchanged; the registry is the sole intentional content addition.

Assets

AzerothNavigator-0.8.1-x64-setup.exe, AzerothNavigator-addon-0.8.1.zip,
CANDIDATE_NOTES.md, SOURCE_COMMIT.txt and SHA256SUMS.txt. Verify the checksum manifest
and exact source metadata before using these developer artifacts.

Evidence limits and next audit

These repairs establish bounded local preparation behavior, not new redistribution
rights, verified playable records or native/live acceptance. Real catalogs, four
role models, verified Deadmines records, complete comparable sessions, recorded70338
field/event/restriction/plan/HUD/taint evidence and actual party message formats
remain missing or unverified. Native focus/hit-testing/DPI/monitor/installation/
performance acceptance and official Forever endpoint/auth/terms evidence remain
unverified. World expansion stays focused-release/evidence gated; hosting is deferred.
After actual publication, re-audit the released tag before claiming that all ready
engineering is exhausted. External prerequisites remain explicit and unmet.