Making damage per 1 second, using T32

[shiFt]

Ive made an immolation spell using T32, but im struggling on dealing the damage per second rather than the T32 PERIOD, How do I do this?

 

[Sgqvur]

Never really used it but I think T32 has a hardcoded period of 0.03125.

Well not really hardcoded but:

"// =Cons=
// - Only allows one period.
"

>How do I do this?

Well if you can use T32 then you can surely use some other timer [recycling] system or just
simple create timer + attach stuff to timer + detach stuff from timer + destroy timer combo.

 

[shiFt]

what would dealing my damage amount * T32 Period do?

 

[jrhetf4xb]

Just do tick counting ...

struct Data
{
    integer ticks;

    private  method periodic()
    {
        this.ticks -= 1;
        if (this.ticks <= 0) 
        {
            // Do all your damage stuff and reset ticks
            this.ticks = R2I(1. / T32_PERIOD); // or just 32 with 0.03125 period
        }

    }

    static method create() -> thistype
    {
        thistype this = thistype.allocate();
        this.ticks = R2I(1. / T32_PERIOD); // 32 ticks per sec
        this.startPeriodic();
    }
}

In other words, just use an integer with a value of 1/T32_PERIOD and subtract 1 every period until it reaches 0 (when 1 second has passed).

 

[Sgqvur]

>Just do tick counting ...

This may sound nuts but 32 function calls + 32 comparisons + 32 subtractions per second maybe kinda inefficient compared to 1 function call per second.

 

[jrhetf4xb]

Hmm

Making damage per 1 second, using T32

 

[Sgqvur]

I am just saying that it's kinda ironic that systems designed for speed actually makes the mapper to write code bloat.

 

[Romek]

How about dealing [ljass]DAMAGE * T32_PERIOD[/ljass] every time the timer expires?
The health of the unit would decrease much smoother too.

> I am just saying that it's kinda ironic that systems designed for speed actually makes the mapper to write code bloat.
If you don't need a timer running at such a high frequency, don't use a system that's optimized for doing exactly that. If you need a lower frequency timer, there are plenty of other systems out there (such as TimerUtils) that'll do just that, very efficiently.

 

[Sevion]

How about dealing [ljass]DAMAGE * T32_PERIOD[/ljass] every time the timer expires?
The health of the unit would decrease much smoother too.

This.

Makes no sense doing it any other way unless you WANT it to suddenly do that damage every second.

Every T32_PERIOD would be much smoother.

 

[Sgqvur]

>How about dealing DAMAGE * T32_PERIOD every time the timer expires?
The health of the unit would decrease much smoother too.

Yeah Good point:

So it is now less efficient and to the player watching the units life dropping that fast would be jaw dropping.

Also note that in the worst case instead of the unit surviving for 0.96875 more seconds and being able to be saved by the player's quick reactions the unit dies and brings frustration to the player making him shout `imba` etc..

 

[Romek]

> So it is now less efficient and to the player watching the units life dropping that fast would be jaw dropping.
It would drop at exactly the same rate:
If [ljass]DAMAGE[/ljass] is in health/second, then dealing [ljass]DAMAGE[/ljass] damage every second would have the same effect as dealing [ljass]DAMAGE * 0.03125[/ljass] damage every 0.03125 seconds, just the latter would be smoother. T32_PERIOD is 0.03125 by default, though it can be changed.

Once again, if you think that dealing damage at such a high frequency is inefficient, then don't deal damage at such a high frequency. It's really that simple.

 

[shiFt]

Thanks for explaining Romek, I just thought the smooth damage dealing would raise questions by players as to if the ability is really doing the described damage.