Establish the Milestone 6 behavior contract before porting effects. Inspect the user-provided Mystcraft Legacy 0.13.7.06 classes and corresponding source for AgeController, InstabilityController, Deck, InstabilityData, providers, decay handlers, and default config values.
Acceptance criteria:
Document how missing, repeated, dangling, conflicting, and extra symbols affect Legacy instability, including rank/score/deck thresholds and any uncertainty in the source.
Inventory Legacy decay, erosion, scorching, potion, lightning, explosion, meteor, and extra-tick effects; map each to a safe NeoForge 1.21.1 implementation, deliberate adaptation, or explicit deferral.
Define which writing errors remain fatal in Rivencraft versus which may create a valid but unstable Age. Do not silently ignore an unsupported authored effect.
Record default server-safety policy, per-Age limits, config requirements, asset provenance, and M6/M7 boundaries in docs/LEGACY_INSTABILITY_AUDIT.md. No gameplay behavior changes in this audit.
Establish the Milestone 6 behavior contract before porting effects. Inspect the user-provided Mystcraft Legacy 0.13.7.06 classes and corresponding source for AgeController, InstabilityController, Deck, InstabilityData, providers, decay handlers, and default config values.
Acceptance criteria:
- Document how missing, repeated, dangling, conflicting, and extra symbols affect Legacy instability, including rank/score/deck thresholds and any uncertainty in the source.
- Inventory Legacy decay, erosion, scorching, potion, lightning, explosion, meteor, and extra-tick effects; map each to a safe NeoForge 1.21.1 implementation, deliberate adaptation, or explicit deferral.
- Define which writing errors remain fatal in Rivencraft versus which may create a valid but unstable Age. Do not silently ignore an unsupported authored effect.
- Record default server-safety policy, per-Age limits, config requirements, asset provenance, and M6/M7 boundaries in docs/LEGACY_INSTABILITY_AUDIT.md. No gameplay behavior changes in this audit.
dnorberg
added this to the Milestone 6 — Instability milestone 2026-10-08 06:08:57 -04:00
Completed the source audit in docs/LEGACY_INSTABILITY_AUDIT.md, covering Legacy score inputs, controller/modifier penalties, deck gates and provider costs, active versus dormant effects, asset provenance, server-safety proposals, and M6/M7 boundaries. The subsequent user-requested writing-repair implementation is included in release V0.5.1.1; its provisional score is persisted but runtime instability effects are not active yet. Those remain in #64–#73. Validation: 39/39 focused GameTests, Gradle build, release JAR/checksum, and in-game pass.
Completed the source audit in docs/LEGACY_INSTABILITY_AUDIT.md, covering Legacy score inputs, controller/modifier penalties, deck gates and provider costs, active versus dormant effects, asset provenance, server-safety proposals, and M6/M7 boundaries. The subsequent user-requested writing-repair implementation is included in release V0.5.1.1; its provisional score is persisted but runtime instability effects are not active yet. Those remain in #64–#73. Validation: 39/39 focused GameTests, Gradle build, release JAR/checksum, and in-game pass.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Establish the Milestone 6 behavior contract before porting effects. Inspect the user-provided Mystcraft Legacy 0.13.7.06 classes and corresponding source for AgeController, InstabilityController, Deck, InstabilityData, providers, decay handlers, and default config values.
Acceptance criteria:
Completed the source audit in docs/LEGACY_INSTABILITY_AUDIT.md, covering Legacy score inputs, controller/modifier penalties, deck gates and provider costs, active versus dormant effects, asset provenance, server-safety proposals, and M6/M7 boundaries. The subsequent user-requested writing-repair implementation is included in release V0.5.1.1; its provisional score is persisted but runtime instability effects are not active yet. Those remain in #64–#73. Validation: 39/39 focused GameTests, Gradle build, release JAR/checksum, and in-game pass.