Skip to content

Release 1.0.0 - #30

Merged
WilyFoxM merged 2 commits into
mainfrom
release/1.0.0
Nov 13, 2026
Merged

WilyFoxM merged 2 commits into
mainfrom
release/1.0.0

Conversation

@WilyFoxM

@WilyFoxM WilyFoxM commented Nov 13, 2026 •

Copy link
Copy Markdown
Owner

Problem and resulting behavior

Releases Trajectory Projected 1.0.0, out of beta: mod_version 0.2.0 → 1.0.0. No code changes beyond main 69831f3.

The README no longer calls the mod a beta, and its Accuracy section gains two results:

  • The zone's rings against real shots. The log has the spread the server drew for each arrow. Of 291 logged bow shots, 48.8% fell inside the half ring (95% confidence 43–55%) and 92.4% inside the 90% ring (89–95%), counted across the launch direction before the flight bends the spread. 43 shots the server counted at another draw tick are left out. The limit that said the rings were unchecked is removed; the widened zone for draw timing is still listed as unchecked.
  • The fishing rod. Local runs: real casts within 0.09 blocks of the prediction. On my own server I didn't notice a cast landing outside the ghost, even on the very edge of a block; that was by eye, not logged, and the limits say so.

Validation performed

  • GitHub checks (build, unit-tests, spotless): run on this PR.
  • Local checks actually run (JDK 25.0.4):
    • On the release commit: ./gradlew spotlessApply build, 105 unit tests pass.
    • On main 69831f3, which differs from this commit only in the version and the README:
      • The full local client run passes with no other mods and with Sodium 0.9.2.
      • The rod scenes pass with improved transparency, and the rod and Iris scenes pass with Iris 1.11.4 and Complementary Reimagined r5.8.1 and BSL v10.1.8.
      • In those runs, 24 real casts came to rest within 0.09 blocks of the prediction, and every arrow launch stayed within the spread limit.
      • A sweep of the aim over a copy of my world found no aim without surfaces for the zone.
    • runReleaseSmoke on the 1.0.0 JARs, alone and with the add-on: both pass.
    • JAR contents:
      • Release JAR: 107 entries, 4 mixins, no development code.
      • Add-on: 14 entries, 1 mixin, requires exactly 1.0.0.
      • No shared or test classes; en/ru keys and placeholders equal.
    • SHA-256: trajectory-projected-1.0.0.jar 34f2247ba29b32aa88fc39f944eb947a7fe3fad2a2363acc6fa739ab303cceaf, trajectory-projected-dev-1.0.0.jar 6f78c809e2390587bfe821d42af6b412ba02a595e0cbcb440c410382453741bd.
  • Prediction accuracy evidence: the ring check above, from the existing bow logs; the rod casts above, in singleplayer.

Limits and compatibility

  • The server results still come from one server and one evening.
  • The widened zone for draw timing has not been checked against real shots.
  • On a server the fishing rod was checked by eye only.
  • Tag, GitHub Release, Modrinth and CurseForge follow after merge.

@WilyFoxM
WilyFoxM merged commit 48400eb into main Nov 13, 2026
6 checks passed
@WilyFoxM
WilyFoxM deleted the release/1.0.0 branch November 13, 2026 18:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant