Dragonflight Talent System

The main focus of this guide is the new player talent tree system. Professions and "Generic" trees are sometimes mentioned, but professions in particular have some differences that this guide won't dive into. Currently, the only "Generic" tree, is the dragonriding talent tree. If the system turns out to be a success, we can expect more generic trees in the future.

C_Traits contains all the generic APIs and interacts with C_ClassTalents for talent tree specific APIs, and C_ProfSpecs for profession specific APIs.

The hierarchy in the new talent system is: [system] - config >< tree < node < nodeEntry - nodeDefinition - spell In other words (with wow.tools links added when db2 files line up, however, there are usually multiple tables involved for each entity): These entities can all be queried with the C_Traits API, which is listed below

• TraitSystem - specifies Generic trees, e.g. dragonriding talents. This is not part of the hierarchy for player talent trees or professions
• TraitConfig - when you apply your talent choices, you apply it to the config. Switching talent loadouts basically boils down to switching TraitConfig. A config can contain multiple TraitTrees (this is the case for professions, for talent trees there is only 1 TraitTree).
• TraitTree - a tree is basically a list of TraitNodes, and currency cost information. For talent trees, while visually there's a separate class and spec tree, in the API it's all 1 tree. There's 1 TraitTree per class. Professions have a TraitTree for each profession specialization tab.
• TraitNode - a node is roughly equivalent to a button in the tree UI. Nodes can have multiple entries, in particular, choice nodes will have 2, whereas single option nodes have 1.
• TraitNodeEntry - an entry holds information about a specific talent choice itself, including how many ranks it has.
• TraitDefinition - is directly related to a TraitNodeEntry, and will contain the spellID and/or other relevant information, of what a talent will actually do for a player.

Several script and slash commands have been added for accessibility and general use in ClassTalentHelper.lua

• Activate loadout by name:

• Activate loadout by dropdown list order, starting with 1:

• Activate specialization by name:

• Activate specialization by order within the Specializations tab, starting with 1:

• Extracts the list of SpellIDs for the player's current specialization

• Change a selection node choice, and apply the changes.

• Get the currently selected loadout configID. Currently, there is no authoritative API to tell you which loadout is currently selected, so you have to do a best-effort guess instead.

• Checks if a spellID is a learned talent, note that this is an example to explain the API, and that it's generally encouraged to use instead.