<!DOCTYPE markdown>

Short Description:

This table holds all the speech text (whisper, say, yell, emote text in speech bubbles and in the chat window) used within SMART_SCRIPTS table and core scripts.

Detailed Description:

Have you ever wondered how a boss like Sindragosa (→ wowhead) is scripted? There is no need to wonder, you can see it for yourself! (→ Sindragosa Script File)

I know, I know - this looks incredibly complex, over 1600 lines of code! However there is no need to understand everything at one time. Let's focus on something simple, but still very important, shall we? 

If you look at the beginning of the code you can find enum named Texts which is composed of 12 elements (numbers from 0 to 11), let's look closer at the first element of this enum:

boss_sindragosa.cpp  Expand source

 enum Texts
 {
     SAY_AGGRO = 0, // You are fools to have come to this place! The icy winds of Northrend will consume your souls!
     ...
 };

You can verify in game for yourself that Sindragosa will yell this when you start a fight versus her. Did you notice something interesting? Actual text is placed after a which means that this information is comment and our compiler will ignore it. On the other hand we clearly see that she is yelling that text, how is it possible? ===== Where is this information stored? How can I find it? ===== You may say - well this is over 1600 lines long, for sure there must be something, we just didn't find it yet. I can assure you, you won't find anything, if you don't believe, use CTRL+F shortcut and have some fun with searching! There is nothing? That's a shame, but maybe, maybe you had a chance to discover something? boss_sindragosa.cpp  Expand source <code cpp> void EnterCombat(Unit* victim) override { … Talk(SAY_AGGRO); interesting! } </code> Do you see the last line of this function? They are using something which shouldn't work! We can conclude that this function will be called when Sindragosa is entering combat (look at function name!), so now we see why she is yelling at start.

There is still one fundamental question - where is information about this text stored? Answer is simpler than you might thought. It is stored in CREATURE_TEXT table!

to be continued…

This is the creature_template.entry to which the script is linked to.

If there is more than one of the same entry (more than one text the creature says), this column is used to choose if it is a random say or an ordered list. If a creature has got more than one say text to be shown in a given order, it must be incremented for each new matching entry (ex. 0, 1, 2, 3…). If there is only one entry or only one group, this value should be 0. If there are multiple groups of texts, this value stays the same within the group while the id increments within the same group.

Example from Stormwind City Guard, creature 68:

Entry for each group of texts. This is the unique identifier when entry (creature) is the same and groupid is unchanged, it must be incremented (ex. 0, 1, 2, 3…). A creature say will be randomly selected from this list based on the groupid it belongs to.

The text the creature will say.

Value from Languages.dbc (+ the wiki table from the dbc file). When set to 0, the current default language will be used.

A value from 1-100 that represents the percentage chance that this text will be executed.

Value must be >=0. If the value does not meet the condition the SQL will fail on creature_text_chk_1.

The emote that the creature plays when the text is executed. Value to use in this field can be obtained from the emote.dbc

Time in ms to see text. 0 is default and calculated by core.

The sound entry this creature will play at the same time the text is executed. Sounds are found in SoundEntries.dbc.

Id of the equivalent text found in broadcast_text

This field allows you to label a text entry.