The Meta Rotation announcement ships a new LMG, the RPD, with Update 44.1 in August 2026 — the first new weapon id in roughly two years — with the next rotation following in December (44.2).
Could the corresponding asset updates be published at (or ideally before) the live release?
dictionaries/telemetry/damageCauserName.json — the RPD's entry (WeapRPD_C? the internal id hasn't been announced)dictionaries/telemetry/item/itemId.json — the pickup/item entry- the
Item_Weapon_*_C weapon icon
Why it matters: many community sites and SDK wrappers vendor these dictionaries. When entries lag the patch, kill feeds across the ecosystem render raw internal ids with missing icons until the repo catches up. With Meta Rotation making new/reworked weapons a ~4-month cadence, day-one dictionary updates (or even just the confirmed internal id posted in the Developer Discord at patch time) would let everyone ship support immediately.
Thanks — the api-assets repo is a huge help to everyone building on the API.
— Eko, pubg.army
The Meta Rotation announcement ships a new LMG, the RPD, with Update 44.1 in August 2026 — the first new weapon id in roughly two years — with the next rotation following in December (44.2).
Could the corresponding asset updates be published at (or ideally before) the live release?
dictionaries/telemetry/damageCauserName.json— the RPD's entry (WeapRPD_C? the internal id hasn't been announced)dictionaries/telemetry/item/itemId.json— the pickup/item entryItem_Weapon_*_Cweapon iconWhy it matters: many community sites and SDK wrappers vendor these dictionaries. When entries lag the patch, kill feeds across the ecosystem render raw internal ids with missing icons until the repo catches up. With Meta Rotation making new/reworked weapons a ~4-month cadence, day-one dictionary updates (or even just the confirmed internal id posted in the Developer Discord at patch time) would let everyone ship support immediately.
Thanks — the api-assets repo is a huge help to everyone building on the API.
— Eko, pubg.army