Register Sign in
Sulfuras

Westfall Woodworker

Sulfuras · creature entry 6670 · humanoid (type 7)

Entry
6670
Name, as the realm stores it
Westfall Woodworker
Level
5
Creature type
humanoid (type 7)
Elite rank
normal (rank 0)
Pet family
no pet family (0)
Stat class (`unit_class`)
1
Faction id
12
NPC flags
0
Patch row answered
1

This realm holds 15,217 creature rows for 10,381 distinct entries, and 4,405 of those entries carry more than one patch row. This page answers with the newest row the realm itself carries, and the number above is that row's own patch value -- not a claim about which patch the server is running. The daemon's own load query adds one bound this site cannot: `patch <= <the patch the server is running>` (`ObjectMgr.cpp:1193`).

In this realm's world

This realm places this creature 8 times. Its placement rows carry patch_min 0 and patch_max 10, which is how the daemon decides which builds a placement exists in; this site reports that range and does not resolve it against a live patch.

This row's `loot_id` is 0, and the daemon skips the loot table for a 0 without looking (`Creature.cpp:1643-1646`) -- even in a realm where the loot table has rows filed under this entry's number. Rows that no creature draws are not this creature's loot, so none are counted here.

This row's `skinning_loot_id` is 0, so the daemon offers no skinning at this creature.

This row's `vendor_id` is 0: the daemon's own loader treats a non-zero vendor id as a vendor template and reports a creature that names one without the vendor flag as a data error (`ObjectMgr.cpp:1596-1599`).

Health this creature would have

FactorAs stored
Base health for stat class 1 at level 5 102
Base armor 103

The daemon multiplies those two numbers and one more it reads from the server's own settings -- a per-rank rate that a read-only database connection cannot see -- and the result is the health a player sees (`Creature.cpp:1802-1803`, `:1856-1871`). So this page shows the factors rather than a total: a total printed here would be this site's guess at a setting it cannot read. The rank number is not an ordered scale either: in the realm's own header world boss is 3 and rare is 4, and the code tests rank against `CREATURE_ELITE_ELITE` (`Creature.cpp:2717`), which is why an elite word and a rank number are shown side by side instead of one standing in for the other.

Resistances

Every resistance column in this row holds 0: holy_res, fire_res, nature_res, frost_res, shadow_res, arcane_res.

Money it would carry

The row stores 35 and 51, and the daemon draws a number between them, multiplies it by the realm's money rate -- a server setting this site cannot read -- and pays it out as money (`Creature.cpp:1650`, `LootMgr.cpp:735-746`, `LootHandler.cpp:328`). The two numbers are printed as stored; the realm keeps no unit beside them.

Quests this creature is part of

Neither of this realm's creature relation tables names this entry, so no quest is started or finished at it. That is the ordinary case: 3,908 and 4,069 rows in those tables, against 10,381 entries.

Browse creatures Search areas Search quests Search game objects Search items