Bijou
Sulfuras · creature entry 10257 · humanoid (type 7)
- Entry
- 10257
- Name, as the realm stores it
- Bijou
- Level
- 58
- Creature type
- humanoid (type 7)
- Elite rank
- elite (rank 1)
- Pet family
- no pet family (0)
- Stat class (`unit_class`)
- 1
- Faction id
- 35
- NPC flags
- 2
- Patch row answered
- 0
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 once. 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
| Factor | As stored |
|---|---|
| Base health for stat class 1 at level 58 | 2,871 |
| Base armor | 3,361 |
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
Both money columns hold 0, and the daemon skips money entirely when the maximum is 0 (`LootMgr.cpp:737`): this creature would carry none.
Quests this creature is part of
| Relation | Quest |
|---|---|
| starts | Bijou's Belongings entry 4982 |
| starts | Bijou's Reconnaissance Report entry 4983 |
| starts | Bijou's Belongings entry 5001 |
| starts | Message to Maxwell entry 5002 |
| is handed back for | Operative Bijou entry 4981 |
| is handed back for | Bijou's Belongings entry 4982 |
| is handed back for | Bijou's Belongings entry 5001 |
These links come from this realm's own relation tables -- `creature_questrelation` and `creature_involvedrelation` -- and the titles come from the quest table, newest patch row. One creature can both start a quest and take it back, and the same quest then appears twice on purpose.
Browse creatures Search areas Search quests Search game objects Search items