I played around with the option to create new default stuff for the data editor.
Lets say, I want to have a base ability, which by default selects a button with the same id as the ability.
So I create a new ability, type Effect Target, check Defines Default Values. I call it Effect Target Template, which gets the id EffectTargetTemplate.
Then, I edit the CAbilEffectTarget_CmdButtonArray_DefaultButtonFace field in raw data to (##id##|), which works correctly. It shows up as EffectTargetTemplate (Unknown) in normal view, so it tries to access a button with the same id.
Now, I try to use this template, so I create another ability called Test, type Effect Target, based on Effect Target Template.
However, it doesn't work as expected. The ability also references the EffectTargetTemplate - button, instead of the Test - button, even if the first one doesn't exist and the second one does.
Checking in raw data reveals, that the ##id## reference was automatically changed to ##parent##.
So, how do I circumvent this? How could I create my own template?
€ ah, okay -.- I was under the (obviously flawed) impression, that values entered in raw data mode are directly applied to the xml files. This is not the case, the xml values still referenced the literal id of the template instead of the ##id## - token. Changing the xml file solved this.
Hey.
I played around with the option to create new default stuff for the data editor.
Lets say, I want to have a base ability, which by default selects a button with the same id as the ability.
So I create a new ability, type Effect Target, check Defines Default Values. I call it Effect Target Template, which gets the id EffectTargetTemplate.
Then, I edit the CAbilEffectTarget_CmdButtonArray_DefaultButtonFace field in raw data to (
##id##
|), which works correctly. It shows up as EffectTargetTemplate (Unknown) in normal view, so it tries to access a button with the same id.Now, I try to use this template, so I create another ability called Test, type Effect Target, based on Effect Target Template.
However, it doesn't work as expected. The ability also references the EffectTargetTemplate - button, instead of the Test - button, even if the first one doesn't exist and the second one does.
Checking in raw data reveals, that the
##id##
reference was automatically changed to##parent##
.So, how do I circumvent this? How could I create my own template?
€ ah, okay -.- I was under the (obviously flawed) impression, that values entered in raw data mode are directly applied to the xml files. This is not the case, the xml values still referenced the literal id of the template instead of the
##id##
- token. Changing the xml file solved this.If you really want to make Templates (and make super duper powerful Templates), check out this program that I made: http://www.sc2mapster.com/assets/starcraft-2-data-manager/
With it, you'd be able to make Templates that use more variables than just
id
AND the variables would actually get filled in like you'd expect.