Darkshore

Sulfuras · area entry 148 · 72 quests set here · 17 areas filed under it · 15 fishing sources · the daemon sets weather here

Entry

148

Name, as the realm stores it

Darkshore

Where it sits

a zone of this realm

Map id, as stored

1

Areas filed under this one

17

`area_level`, as stored

0

`explore_flag`, as stored

227

`flags`, as stored

64

`team`, as stored

2

Every one of these columns holds 0 in this row: liquid_type. This realm's source has no named constant for any of them, so they are named by column and left at that.

`area_template` carries no patch column on this realm: 1,081 rows for 1,081 entries, so this page answers from the one row that exists and is not choosing between copies. Where a related table is patch-versioned -- the quest table, `map_template`, the graveyard rows -- this site takes the newest row it can see, and the map row above came from the newest `patch` row in this realm's own `map_template` (patch 0). Neither number says which patch this realm runs: the daemon's own load queries add a bound against a number only the running server holds.

Where this area sits

This row carries no parent: 122 of this realm's 1,081 area rows are built that way, and a row that points at itself would be a different convention -- none does.

The realm's own `map_template` names map 1 “Kalimdor”.

Quests set in this area

This realm's quest table files 72 quests under this area id in `ZoneOrSort`, counted one per quest entry at its newest patch row. This page lists the first 25 by entry and stops; the realm files more here than any page should print.

The weather this daemon rolls here

These are the stored chances, one row per season, in the daemon's own column names. They are not measurements: the daemon reads exactly these columns (`Weather.cpp:451`) and compares rain, then rain+snow, then rain+snow+storm against a single draw of 1 to 100 (`Weather.cpp:172-181`), so a 25 is one chance in a hundred of that daemon's own random draw.

Resurrections

2 rows of `game_graveyard_zone` name this area as their ghost zone, stored as faction 0, which this realm's source gives no player-facing name for. The daemon keeps only the rows whose `patch_min`/`patch_max` window contains the patch it is running (`ObjectMgr.cpp:7457`) and skips a row naming a zone its area table does not know (`:7493`); both numbers are ones this site cannot read from a database connection, so the count above is of the realm's rows, not of what a player would actually be sent to.

Spells the realm restricts to this area

By spell id, because the realm's spell_area table stores ids and no names.

1 row of `spell_area` restricts a spell to this area; the daemon loads that table at `SpellMgr.cpp:2438` and rejects a row whose area id its area table does not know (`:2511`). The table stores spell ids and no names, so they are listed by id.

Fishing and bound items

15 rows of `fishing_loot_template` are filed under this area id -- the key's meaning in the daemon's own words, from its registration line `LootStore LootTemplates_Fishing("fishing_loot_template", "area id", true)` (`LootMgr.cpp:46`). What each row drops is the item page's job, and this site does not link an item it has not read.

No item in this realm's item table names this area in `area_bound`; an item that is bound nowhere stores 0 there. The realm binds 31 items to some area, and none of them is this one.

Where this realm starts a character

No row of this realm's `playercreateinfo` starts a character in this area. The realm has 40 such rows for other zones, so this is the realm's own choice of starting places.

Browse areas Search quests Search creatures Search game objects Search items