SC2Mapster Forums

Development > Data

[Solved!] Dynamic Tooltip (Persistent) not working

This thread has been locked by iATEM4P5.

ofc

  • 4 posts
    #1 Dec 27, 2012 at 16:30 UTC - 0 likes

    So in a weapon's tooltip I have:

    <d ref="Effect,PersistentName,PeriodicPeriodArray[0]"/>

    Normally this works for other effects, behaviors, etc. However, for some reason, I get 0 when I try to get the period duration of a create persistent effect. (I've also heard trying to get the offsets also returns 0).

    Any reason I'm getting 0 instead of the period of the create persistent effect?

    edit: added in period duration* (misleading sentence)

    Last edited Dec 28, 2012 by iATEM4P5
    #2 Dec 27, 2012 at 21:57 UTC - 0 likes

    You know arrays need a different format of query right?

    That is just asking for the first period in the array. The duration is a combination of the periods and the number of periods executed.

    #3 Dec 28, 2012 at 04:38 UTC - 0 likes

    @DrSuperEvil: Go

    No I just want the duration of one period. In this case, I only want the duration of the first period. However, SC II is returning 0 instead of the period of the effect.

    So for example, I have a persistent effect with:

    Duration 5.000
    Period count: -1
    Period duration: 0.25

    I'm trying to grab the period duration using:
    <d ref="Effect,PersistentName,PeriodicPeriodArray[0]" precision="2" />

    But, that reference is returning 0 instead of 0.25
    Any1 know why?





    edit: For those of you that have never used dynamic tooltips, you can learn how to use them here:
    http://www.sc2mapster.com/forums/resources/tutorials/17879-data-button-tooltip-referencing/

    Last edited Dec 28, 2012 by iATEM4P5
    #4 Dec 29, 2012 at 08:24 UTC - 0 likes

    Fixed!

    I just used the built in clickable browse/insert data reference thing in the tooltip instead of typing it myself. I guess I had a typo that I just couldn't see? or this specific reference only works when the editor generates it for you? either way, fixed now.

  • 4 posts