System Periodic Module

[Romek]

> Pretty sure you wouldn't be able to set it on init then, which means every struct type would be forced to have the same period...
That's not a problem.

> Some people don't like 0.03125. I know, I call them crazy too.
Then they can change the constant..

> Whilst I'm fully aware of that, I found that if I excluded that I got compile errors (although I'm not actually using .G.x yet). It should inline anyway.
Weird.

> Personal preference is not to, for various reasons. Does this particularly annoy you (or anyone)?
No, not really. Just 1 less instance. (A minor problem)
It annoys Uberplayer.

 

[Viikuna]

Some people don't like 0.03125. I know, I call them crazy too.

It looks bad for some people. Dont know if it is their eyes or their computers, but I usually use .025 in these days.

 

[Romek]

Then you'd be able to change the constant.
I'm still for it.


Also, this needs a demo map.

 

[Jesus4Lyf]

I still agree with you Romek, except for one point.

What if people release spells written with this on TheHelper, and they use different periods? =/

Anyway, as for a demo map... Could be a little while if Cohadar doesn't opt to write one, because I'm actually still using jasshelper 0.9.E.0. Shhh. :thup:

 

[Romek]

> What if people release spells written with this on TheHelper, and they use different periods? =/
Make the period a non-private constant then.

// Some configuration
private constant real DAMAGE = 100 // Damage per second

// Function
call UnitDamage...  .. (DAMAGE * .PERIOD) // Per second. Regardless of the period.

> because I'm actually still using jasshelper 0.9.E.0
Hint: Update Jasshelper.

 

[Jesus4Lyf]

>Hint: Update Jasshelper.
Lol, I couldn't make it work with NewGen. That was what this thread was originally about. XD

>Make the period a non-private constant then.
What if they want to kill 32 units a second? There's definitely legitimate reasons for using different periods.