This hotfix stabilizes item data after v3.3 and introduces the first raid leaderboard updates.
Item database and search
- Fixed charm level ranges.
- Fixed charm-only IDs being in
identifications instead of base.
- Fixed leather armour colour responses.
- Fixed charms missing a type.
- Fixed identification values of
1 being rollable; those values now return as raw values.
- Fixed identification rounding.
- Fixed major IDs sometimes being absent.
- Fixed
allowCraftsman not being returned.
- Fixed quest requirements not being returned.
- Fixed spell cost identifications being treated as negative IDs.
- Fixed ingredients missing
droppedBy, item-only IDs, and related fields.
- Fixed
levelRange being returned as an identification.
- Fixed identified items returning raw damage IDs instead of ranges.
- Fixed base defences and health returning as rolled stats.
- Fixed material and ingredient crafting data.
- Fixed weapon damage minimum and maximum values being swapped.
- Fixed weapon elemental damage being omitted when the range started at
0.
- Fixed skin texture IDs always using the missing texture.
- Updated the
iron_barding ID.
- Fixed player head helmets being considered leather armour.
- Fixed item tooltips using internal names.
- Fixed spell cost display still being wrong after the first patch.
- Added the
static query parameter.
static returns all available tags with their internal numeric ID.
- Added a type-filter translation map, allowing plural type filters and converting
armor to armour.
Known remaining issue:
- Pagination could still sometimes drop entries.
Leaderboards
- Added per-raid solo raid leaderboards for players and guilds.
- Raid leaderboards count raids completed since Wynncraft: Rekindled World.
- Raid leaderboard scores account for gambit usage.
- Fixed normal raid leaderboards not counting new completions.
- Fixed raid completions being swapped.
- Hunted leaderboards now sort by content completion, combat level, then total level.
Known data issue:
- Normal raid completion display data could be chaotic immediately after the fix because old swapped raid data still existed. Player rankings were valid; displayed raid data was corrected as players connected.