/
model_destiny_definitions_destiny_node_step_definition.go
48 lines (47 loc) · 6.27 KB
/
model_destiny_definitions_destiny_node_step_definition.go
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
/*
* Bungie.Net API
*
* These endpoints constitute the functionality exposed by Bungie.net, both for more traditional website functionality and for connectivity to Bungie video games and their related functionality.
*
* API version: 2.18.0
* Contact: support@bungie.com
* Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
*/
package D2Client
// This defines the properties of a \"Talent Node Step\". When you see a talent node in game, the actual visible properties that you see (its icon, description, the perks and stats it provides) are not provided by the Node itself, but rather by the currently active Step on the node. When a Talent Node is activated, the currently active step's benefits are conferred upon the item and character. The currently active step on talent nodes are determined when an item is first instantiated. Sometimes it is random, sometimes it is more deterministic (particularly when a node has only a single step). Note that, when dealing with Talent Node Steps, you must ensure that you have the latest version of content. stepIndex and nodeStepHash - two ways of identifying the step within a node - are both content version dependent, and thus are subject to change between content updates.
type DestinyDefinitionsDestinyNodeStepDefinition struct {
// These are the display properties actually used to render the Talent Node. The currently active step's displayProperties are shown.
DisplayProperties *AllOfDestinyDefinitionsDestinyNodeStepDefinitionDisplayProperties `json:"displayProperties,omitempty"`
// The index of this step in the list of Steps on the Talent Node. Unfortunately, this is the closest thing we have to an identifier for the Step: steps are not provided a content version agnostic identifier. This means that, when you are dealing with talent nodes, you will need to first ensure that you have the latest version of content.
StepIndex int32 `json:"stepIndex,omitempty"`
// The hash of this node step. Unfortunately, while it can be used to uniquely identify the step within a node, it is also content version dependent and should not be relied on without ensuring you have the latest vesion of content.
NodeStepHash int32 `json:"nodeStepHash,omitempty"`
// If you can interact with this node in some way, this is the localized description of that interaction.
InteractionDescription string `json:"interactionDescription,omitempty"`
// An enum representing a damage type granted by activating this step, if any.
DamageType int32 `json:"damageType,omitempty"`
// If the step provides a damage type, this will be the hash identifier used to look up the damage type's DestinyDamageTypeDefinition.
DamageTypeHash int32 `json:"damageTypeHash,omitempty"`
// If the step has requirements for activation (they almost always do, if nothing else than for the Talent Grid's Progression to have reached a certain level), they will be defined here.
ActivationRequirement *AllOfDestinyDefinitionsDestinyNodeStepDefinitionActivationRequirement `json:"activationRequirement,omitempty"`
// There was a time when talent nodes could be activated multiple times, and the effects of subsequent Steps would be compounded on each other, essentially \"upgrading\" the node. We have moved away from this, but theoretically the capability still exists. I continue to return this in case it is used in the future: if true and this step is the current step in the node, you are allowed to activate the node a second time to receive the benefits of the next step in the node, which will then become the active step.
CanActivateNextStep bool `json:"canActivateNextStep,omitempty"`
// The stepIndex of the next step in the talent node, or -1 if this is the last step or if the next step to be chosen is random. This doesn't really matter anymore unless canActivateNextStep begins to be used again.
NextStepIndex int32 `json:"nextStepIndex,omitempty"`
// If true, the next step to be chosen is random, and if you're allowed to activate the next step. (if canActivateNextStep = true)
IsNextStepRandom bool `json:"isNextStepRandom,omitempty"`
// The list of hash identifiers for Perks (DestinySandboxPerkDefinition) that are applied when this step is active. Perks provide a variety of benefits and modifications - examine DestinySandboxPerkDefinition to learn more.
PerkHashes []int32 `json:"perkHashes,omitempty"`
// When the Talent Grid's progression reaches this value, the circular \"progress bar\" that surrounds the talent node should be shown. This also indicates the lower bound of said progress bar, with the upper bound being the progress required to reach activationRequirement.gridLevel. (at some point I should precalculate the upper bound and put it in the definition to save people time)
StartProgressionBarAtProgress int32 `json:"startProgressionBarAtProgress,omitempty"`
// When the step provides stat benefits on the item or character, this is the list of hash identifiers for stats (DestinyStatDefinition) that are provided.
StatHashes []int32 `json:"statHashes,omitempty"`
// If this is true, the step affects the item's Quality in some way. See DestinyInventoryItemDefinition for more information about the meaning of Quality. I already made a joke about Zen and the Art of Motorcycle Maintenance elsewhere in the documentation, so I will avoid doing it again. Oops too late
AffectsQuality bool `json:"affectsQuality,omitempty"`
// In Destiny 1, the Armory's Perk Filtering was driven by a concept of TalentNodeStepGroups: categorizations of talent nodes based on their functionality. While the Armory isn't a BNet-facing thing for now, and the new Armory will need to account for Sockets rather than Talent Nodes, this categorization capability feels useful enough to still keep around.
StepGroups *AllOfDestinyDefinitionsDestinyNodeStepDefinitionStepGroups `json:"stepGroups,omitempty"`
// If true, this step can affect the level of the item. See DestinyInventoryItemDefintion for more information about item levels and their effect on stats.
AffectsLevel bool `json:"affectsLevel,omitempty"`
// If this step is activated, this will be a list of information used to replace socket items with new Plugs. See DestinyInventoryItemDefinition for more information about sockets and plugs.
SocketReplacements []DestinyDefinitionsDestinyNodeSocketReplaceResponse `json:"socketReplacements,omitempty"`
}