Weapon AR research lab
Test a parameter-driven attack-rating engine before real weapon data is licensed and checked in-game. The example below is a fictional weapon, not a playable Elden Ring item.
Research input
Player attributes
Damage component breakdown
| Type | Base | Scaling | Displayed* |
|---|
*Displayed components are floored independently; total is floored after summing the non-rounded components. Real game parity is unverified.
Bring your own parameters (research only)
Load a local JSON file or edit the profile. Required fields: per-affinity base damage; five attribute coefficients; exact 151-point correction curves; attribute/element impact and override rules; reinforcement damage and scaling multipliers. Missing levels are rejected rather than guessed.
The full JSON is read locally in your browser. This preview rejects profiles claiming verified status; real data publication requires independent licence review, actual game-version check and golden tests.
Browse a local versioned dataset
Use the Weapon Data Workbench to load your own compact regulation JSON, search weapon/affinity entries and compare preliminary AR at specified upgrade levels. Data remains local and every output is marked unverified.
Validate AR observations
Import candidate parameters and independently recorded AR values into the local-only AR evidence comparator. Even exact matches remain unreviewed until source and game-client evidence are checked.
What's implemented — and what's not
- Implemented: 5 separate damage types, stat scaling, two-hand strength adjustment, minimum-attribute penalties, scaling overrides, affinity and upgrade selection, JSON validation, final rounding, and missing-parameter refusal.
- Not implemented: actual game weapon profiles, ashes of war, status effects, enemy defenses, motion values, buffs or end-to-end in-game AR accuracy.
- Current regulation reference: App 1.17.2 / Regulation 1.17.3; this demo does not reflect any regulation's real numbers.
Algorithm reference: ERDB AR calculation documentation. Full validation gate is in verification status.