...
The `spell_ranks` table
Table used by the core for grouping ranked spells in spellbook, aura stacking checks, some tables data loading, in one word everywhere where spell ranks(gray text you see in game in ranked spells) are used. In this table spell rank chain has linear structure (there can be only one rank 2 of a spell), and one spell cannot belong to 2 different rank chainsto group different ranks of spells (the gray text seen on ranked spells) into one stem. This partly involves checks for aura stacking (e.g. different levels of the same spell). One spell can not be linked to multiply rank chains (they are "unique").
Structure
Field | Type | Attributes | Key | Null | Default | Extra | CommentSpell ranks tc2 |
int(10) | unsigned | PRI | NO | 0 |
| ||
int(10) | unsigned |
| NO | 0 |
|
| |
tinyint(3) | unsigned | PRI | NO | 0 |
|
|
Description of the fields
first_spell_id
SpellId from Spell.dbc which is first rank of spell rank chain, . It identifies the whole chain.
spell_id
SpellId from Spell.dbc
rank
An integer which tells the core which rank of a spell rank chain is SpellId in ranks the spell within the chain of spell ranks for the given `spell_id` column. Can be different from . It can differ from the rank text in game (for example, some ranks in client begin start with level 0, here only with 1). There must be at least 2 ranks defined for spell rank chain, one of them has to be first rank, there must be all ranks defined between highest and lowest `rank` column value for a spell rank chainwhile the server always starts from level 1 onward). Several conditions have to be fulfilled:
- At least two levels are required
- There can be no jumps between ranks (e.g. one spell being level 3 and one being level 5 while level 4 is missing altogether)
- There can be no duplicates in ranks.