Five ranged weapons fight as unarmed: absent from the category mapping #147

Closed
opened 2026-08-06 18:09:27 +00:00 by sickday · 1 comment
Owner

Five ranged weapons the cache carries are absent from the weapon-category
item mapping, so each fights as :unarmed — no ranged stance, no quiver, a
melee punch at range one. Found while checking every attack range against
the wiki's Attack range table (the six wrong ranges that check found are
fixed and pinned by PvpStandoffTest; these five are a different fault —
the ids are missing from the mapping entirely, a coverage gap in the source
dump rather than a wrong number):

  • Seercull (6724) — wiki range 8, its own category shape (a shortbow
    that reaches like a long-range crossbow)
  • Ogre bow (2883) — wiki range 10, fires ogre arrows only
  • Comp ogre bow (4827) — wiki range 5, quest-gated, ogre/brutal arrows
  • Phoenix crossbow (771) — wiki range 5
  • Holy water (732) — wiki range 4, thrown, its own ammo rules
  • Mud pie (7170) — wiki range 6, thrown

(Six lines because holy water and the mud pie surfaced in the same sweep;
all six ids decode in the 149 cache.)

The fix is rows in the extractor's source or an overlay beside
@wiki_ranges, not hand-edits to the generated file. Each wants: a
category (existing where the shape fits — phoenix crossbow is plausibly
:crossbow at a corrected range — new where it does not: seercull, the
ogre bows and both thrown items carry their own range/ammo shapes), the
range from the wiki table, and World.Ammo allow-list entries where the
weapon is choosy (ogre bows especially — brutal arrows exist in era).

Related, recorded in the same sweep and explicitly not this issue:
the Dorgeshuun crossbow shares :crossbow and so reaches 7 where the wiki
says 6, and salamanders cannot attack from the diagonal their one tile
allows. Both are range/reach shape questions on existing rows, not missing
ids.

Five ranged weapons the cache carries are absent from the weapon-category item mapping, so each fights as `:unarmed` — no ranged stance, no quiver, a melee punch at range one. Found while checking every attack range against the wiki's *Attack range* table (the six wrong ranges that check found are fixed and pinned by `PvpStandoffTest`; these five are a different fault — the ids are missing from the mapping entirely, a coverage gap in the source dump rather than a wrong number): - **Seercull** (6724) — wiki range 8, its own category shape (a shortbow that reaches like a long-range crossbow) - **Ogre bow** (2883) — wiki range 10, fires ogre arrows only - **Comp ogre bow** (4827) — wiki range 5, quest-gated, ogre/brutal arrows - **Phoenix crossbow** (771) — wiki range 5 - **Holy water** (732) — wiki range 4, thrown, its own ammo rules - **Mud pie** (7170) — wiki range 6, thrown (Six lines because holy water and the mud pie surfaced in the same sweep; all six ids decode in the 149 cache.) The fix is rows in the extractor's source or an overlay beside `@wiki_ranges`, not hand-edits to the generated file. Each wants: a category (existing where the shape fits — phoenix crossbow is plausibly `:crossbow` at a corrected range — new where it does not: seercull, the ogre bows and both thrown items carry their own range/ammo shapes), the range from the wiki table, and `World.Ammo` allow-list entries where the weapon is choosy (ogre bows especially — brutal arrows exist in era). Related, recorded in the same sweep and explicitly *not* this issue: the Dorgeshuun crossbow shares `:crossbow` and so reaches 7 where the wiki says 6, and salamanders cannot attack from the diagonal their one tile allows. Both are range/reach shape questions on existing rows, not missing ids.
Author
Owner
Moved to https://forge.home.arpa/Revenant/Server/issues/47
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Revenant/Server#147
No description provided.