Skip to content

Releases: LegendaryForge/LegendaryCore

v1.0.0-rc3

30 Jan 02:13
@LegendaryForge LegendaryForge
v1.0.0-rc3
4ee94c2
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v1.0.0-rc3 Pre-release
Pre-release

Summary

LegendaryCore v1.0.0-rc3 introduces the minimal “activation primitives” needed for content mods to safely control encounter activation without Core bloat: condition gates, activation authority decisions, and activation sessions.

This release is intended to unblock real content development (e.g., Stormseeker) while preserving strict Core guardrails.

Changes

  • Added Condition Gates API (GateService, ConditionGate, GateDecision) with default internal implementation.
  • Added Activation Sessions API (ActivationSessionService + begin/commit/abort + view/state) with default internal implementation.
  • Added Activation Service API (ActivationService + decision/result primitives) with default internal implementation.
  • Wired GateService, ActivationSessionService, and ActivationService into the default runtime (DefaultCoreRuntime) service registry.

Rationale

Content mods need a deterministic, enforceable activation boundary to prevent player-visible failure modes (double-start, contested activation, retry/disconnect ambiguity) while keeping quest logic and tuning out of Core.

These primitives are intentionally generic and reusable across future legendary encounter types.

Verification

  • ./gradlew spotlessApply clean test PASSING
  • LegendaryContent harness coverage validates runtime registration and core service behavior (gates + sessions).
Loading

v1.0.0-rc2

29 Jan 05:00
@LegendaryForge LegendaryForge
v1.0.0-rc2
92e8038

Choose a tag to compare

View all tags
v1.0.0-rc2 Pre-release
Pre-release

Summary

LegendaryCore v1.0.0-rc2 finalizes Legendary arena enforcement, consequence signaling, and platform-facing UX resolution for participation revocation.

This release establishes a stable, player-visible enforcement baseline suitable for first content mods.

Changes

  • Added arena participation revocation tracking and ACTIVE-only rejoin enforcement (Legendary-only).
  • Introduced a canonical revocation controller and signal-driven revocation events.
  • Added advisory Legendary penalty suggestion events and bridging logic (platform-owned application).
  • Extended the Hytale platform adapter seam to receive penalty suggestions.
  • Added a Hytale reason-to-message resolver for player-facing revocation UX.
  • Added recording penalty applier scaffolding for adapter testing and validation.

Rationale

Legendary arenas require enforceable consequences (anti-griefing, anti-rejoin abuse) without hard-coding platform policy into core logic.
This release delivers those consequences through signal-driven enforcement while preserving a strict Core → Platform boundary.

Verification

  • ./gradlew spotlessApply clean test
Loading