Java Edition field instrument

OlderCraft

Repair bench version core

Compatibility is a recorded fit, not a promise.

Pick a version. See what still connects.

Manual
METHODOLOGY
Record
Java Edition
Edition
2.0.0

Bench method MT–01 Deterministic verdicts

Methodology

The workbench reads published protocol records. This sheet separates the calculation from everything it cannot establish.

Dataset
1.1.0
Coverage
2025-07
Live probe
Unavailable

Method / output

What a verdict is

The workbench compares the recorded network protocol of two published, high-confidence releases. Equal protocols yield protocol match; unequal protocols yielddirect mismatch. Missing, unsupported, or verification-hold inputs yield unknown. The function is deterministic and shipped with the page, so the same inputs always produce the same verdict offline.

Limits / explicit

What a verdict is not

  • Not a login promise: authentication, allowlists, mods, and proxies are separate constraints.
  • Not a bridge detector: translation layers are server-side and cannot be inferred from version numbers. Averified bridge tier exists in the design but is deliberately unreachable until authenticated, first-party inventory evidence exists.
  • Not a live observation: nothing on this site pings arbitrary servers today.

Record / confidence

Confidence tiers

Every dataset row carries published with high confidence or verification-hold. A held row remains readable and stays out of the sitemap, but cannot produce a positive or negative class. Coverage ends at 2025-07; missing rows render as Unknown, never as a guess.

Unavailable / live state

What this static desk cannot observe

OlderCraft does not perform Server List Ping requests. A safe live checker would need public-hostname rules, private-range rejection, rebinding defenses, strict timeouts, response caps, and an explicit freshness window; none of those observations exist on this property. Server availability, reported software, bridge inventory, and current protocol therefore remain Unavailable rather than borrowing confidence from the static release record.

Dates / substantive

Freshness rules

Dates on this site are content dates, not build dates. The release record updates only when a source diff is verified; page lastmod values change only for substantive edits. When a fact expires, the page keeps the last-known-good value with its date and labels it stale rather than silently refreshing it.