What is verified — and what is not

Reference benchmark first — no game installation required

v1.17 numerical reference benchmark PASS for these 50 cases only. The detailed table below shows the original 15 cases; all 35 additional exact inputs, source AR outputs and evidence are documented in the 50-case report. Browser input evidence: first full 15-case public UI run and independent recheck. Our v1.17 numerical results: AR computation run. For new cases see first full 50-site run and independent 50-site recheck. The final raw-sum aggregation follows 50-input rounding evidence. This does not certify every weapon, all mechanics, actual PvE damage or the current Regulation 1.17.3 game client.

Tarnished.dev publicly labels its Elden Ring calculator data v1.17 (site update 28 August 2026). We use that site as our primary functional and calculation-output benchmark for a separately implemented v1.17 reference calculator, not as a claim that every value is independently certified against the newer Regulation 1.17.3 game client.

Non-blocking website release rule: real-game screenshots are optional for a clearly marked third-party reference based v1.17 feature, once a reproducible set of same-input weapon/affinity/upgrade/attribute/one-hand/two-hand cases agrees with Tarnished.dev and all known discrepancies are labelled. Do not imply that simply linking to Tarnished.dev is equivalent to a successful numerical comparison. The pinned v1.17 reference AR engine now meets the documented representative 50-case external parity matrix; this is limited to these cases and not a blanket patch-accuracy claim.

Strictly separate claim: saying verified current Regulation 1.17.3 game-client AR still requires current-version evidence. If a numeric case disagrees, display or block that specific result; do not silently use the competitor as an absolute ground truth, copy its proprietary software or redistribute its full data. Source permits an independent implementation, not automatic relicensing.

Working reference-AR path: local v1.17 weapon data workbench (free pinned public JSON, opt-in download; no account or paid API). 487-weapon reference catalog shows named published +0 candidates. The former screenshot queue remains an optional research track, not a prerequisite for user-facing v1.17 benchmarked reference tools.

Live catalog evidence audit

Counts below are generated during the same build as this site from the exact bundled weapon JSON, not manually transcribed. A present field is not proof of current-patch accuracy. Weapon requirements and weights are community-reported; this preview does not contain fully validated per-weapon AR profiles.

Unresolved source conflicts (7 catalog entries)

Source snapshot version: not established; do not assume 1.17.3 compatibility. Upstream revision: 1d2626ceda5eb8c08997e345e303344a64edc106. This is a catalog consistency audit, not game-client QA. Open build-generated machine-readable evidence.

Seven unresolved weapon-source disagreements

These are two contradictory published data sources, not two sets of game-client screenshots. The first value is from our attributed community +0 reference; the second comes from the pinned Regulation 1.17 parameter source after applying the +0 reinforcement factor. Data order for attacks: Physical / Magic / Fire / Lightning / Holy; for requirements: STR / DEX / INT / FAI / ARC. A source disagreement is not proof that either side is correct for App 1.17.2 / Regulation 1.17.3.

Tracked version continuity (not weapon-menu certification): 1.17 → 1.17.1 had 184 hash-identical parameter tables; 1.17.1 → 1.17.3 had no tracked headline numeric changes, while some projectile and animation tables changed. The complete 1.17.3 regulation binary is not asserted identical, nor are the six exact weapon +0 vectors independently verified by that patch comparison.

Unversioned third-source +0 checks: 6 of 6 published base-attack disputes match the pinned Regulation 1.17 vector. This favors the pinned source as a provisional published-data candidate for these six weapons. However, the third-party weapon pages lack an explicit current App/Regulation version and do not document independent data extraction lineage. Agreement is NOT game-client verification. All six original source disagreements stay open; trusted AR and upgrade calculations continue to block the disputed +0 figures.

Current-patch corroboration: 1 of 7 historical disagreements. Fire Knight's Shortsword also has a contradiction inside the same wiki page: its basic Stats section says PHY 75 / FIRE 32, while the Standard +0 row says PHY 72 / FIRE 22. The pinned Regulation 1.17 source says PHY 75 / FIRE 22. These three different published readings are shown for provenance, not spliced into a manufactured answer. See the original article. Madding Hand FAI 20 in an independently published Regulation 1.17.3-labelled parameter reference agrees with pinned Regulation 1.17; unversioned wiki reports FAI 13. This supports 20 as a version-labelled source reading, not an original game-menu screenshot or definitive verified wield verdict. Six +0 attack disputes remain without independent comparable current-patch +0 game-menu readings.

How to resolve one entry

In the actual App 1.17.2 / Regulation 1.17.3, capture the title-screen version and the exact weapon at +0, default/uninfused state. For six base-attack cases, compare the weapon information panel’s five base damage components, not character AR. For Madding Hand, capture the weapon’s five attribute requirements, not effective two-hand Strength. Keep screenshots locally and record platform, date, file SHA-256, weapon, reinforcement and affinity. A separate reviewer must inspect authentic game images and both version labels before changing a source flag. Numerical agreement between websites alone cannot close an item.

Current accepted game screenshot count: 0 · all seven items UNREVIEWED. Download source comparison and manual verification checklist JSON · Record the seven +0 game readings locally · Open existing local AR/observation workbench. No game files, screenshots or user identifiers are uploaded.

Compare all seven disputed weapons against a current Regulation JSON

A versioned parameter-difference tracker reports all 184 regulation parameter tables hash-identical from 1.17 → 1.17.1, and no changes to its tracked weapon/requirement headline numbers from 1.17.1 → 1.17.3. There are other changes to projectiles and animation data in 1.17.3. This is valuable evidence for version continuity, not a per-weapon original-client verification. Inspect the 1.17.3 diff.

Provide your own legitimately obtained compact JSON with weapons and reinforceTypes arrays/tables (the same research data format as the local AR workbench). This is not a regulation.bin or arbitrary CSV importer. The browser compares six neutral-affinity +0 base attacks and Madding Hand's five requirements, without uploading or changing any live weapon record.

Loading the site's conflict reference data…

App/Regulation labels you enter are not authenticated. A matching local source file, its SHA-256 fingerprint, or identical parameter numbers do not establish an original game client, valid screenshot, distinct extraction lineage or true character AR. Any export stays UNREVIEWED; all seven published conflicts remain unchanged until separately reviewed.

Expanded game-client evidence collection

The previous 7-case capture remains available below. A separate 20-field original-game evidence queue now includes the seven legacy cases plus Stone-Sheathed Sword, Ritual Thrusting Shield, and the eight newly disputed recovered weapons. It records local screenshot fingerprints and UNREVIEWED values only; no screenshots have been independently inspected.

Record real game-menu evidence for the seven disputed weapons

Use this form only while viewing the actual game. It records all five +0 weapon-detail attack components or the five requirement values, not your character's total Attack Rating. Select two local screenshots: the version/title screen and the weapon details. The browser computes SHA-256 file fingerprints; screenshot pixels are not uploaded, inspected or included in JSON.

All exports are UNREVIEWED evidence drafts. Matching one published source, matching a screenshot's hash, or manually typing version numbers never means independent gameplay verification.

Each picture must be a real PNG/JPEG/WebP file of at most 12 MB. This form only verifies file signatures and SHA-256 bytes, not that the image actually depicts the stated game, patch or weapon.

Loading the local seven-case audit…

Collection progress (not verification progress)

0 / 7 player observations captured. 0 independently reviewed.

No data is automatically saved or uploaded. The downloadable JSON contains screenshot filenames, SHA-256 digests, and your typed numeric values, but no screenshot contents. Keep both original screenshots privately to allow separate human review. Reloading this page discards unsaved session entries.

Reopen your seven-weapon evidence checklist

Import a JSON checklist exported above. The page checks all seven cases against the current source catalog, re-derives the numeric source comparisons and rejects altered approval flags. This checks record consistency, not screenshot authenticity.

Choose an exported checklist to recheck. Nothing is uploaded.

Source & licence policy

Data in this preview is limited to small published numerical facts and independently implemented rules. The ERDB data parser is MIT-licensed code, but that license does not automatically authorize redistribution of all data/assets extracted from the game. A different comprehensive public calculator repository offers no license declaration; no code, images, or tables have been copied from it.

For reference-labelled v1.17 AR, require traceable data source and rights assessment, a pinned version, repeatable same-input benchmarks against Tarnished.dev for base/DLC weapons, upgrades, affinities and 1H/2H, plus explicit disclosure of discrepancies. Game-client screenshots are needed only for claims of independently game-verified current-patch accuracy; reference calculations may be published without them after these benchmark tests pass. Enemy damage/PvP claims need their own independent benchmarks.