[Powerlord]

Originally Posted by Chdata There's no point in doing that if you set the next attack to 3 years from now. PHP Code: // Sarysa variables #define FAR_FUTURE 100000000.0      // This is about 3 years

I would test that first, though. The game may very well clamp values to what it considers a reasonable range.

[Phil25]

Originally Posted by Powerlord I would test that first, though. The game may very well clamp values to what it considers a reasonable range.

If you want to test whether you will be able to attack after 3 years, be my guest ;)

Originally Posted by Chdata There's no point in doing that if you set the next attack to 3 years from now.

And isn't it generally better to work with smaller values? I mean, I understand that it's pretty much impossible to get past that limit but I look at it like at the infamous water/glass analogy: while having a large volume of water you either get a huge-ass glass for it or distribute the water into regular glasses, adding one when you need it.

It all comes down to preference, anyway.

[Starbish]

Originally Posted by Chdata There's no point in doing that if you set the next attack to 3 years from now. PHP Code: // Sarysa variables #define FAR_FUTURE 100000000.0      // This is about 3 years

lol

[Chdata]

Originally Posted by Phil25 If you want to test whether you will be able to attack after 3 years, be my guest ;) And isn't it generally better to work with smaller values? I mean, I understand that it's pretty much impossible to get past that limit but I look at it like at the infamous water/glass analogy: while having a large volume of water you either get a huge-ass glass for it or distribute the water into regular glasses, adding one when you need it. It all comes down to preference, anyway.

Why go through extra typing work to set up a timer that in the end will only waste cycles?

I mean, your example goes both ways. Why transport water in shot glasses when you could distribute water in gallons stored on trucks? Or a better example, why buy one straw from the store every time you need one?

If you look at how often your code is executing, setting it one time is better than constantly setting it again and again to achieve the same thing - in this case you're only writing the value 'when you need it'. You can also re-enable the weapon, only 'when you need to'.

Random code debate aside have a frog: http://imgur.com/p2lkCIK

Originally Posted by Powerlord I would test that first, though. The game may very well clamp values to what it considers a reasonable range.

I tend to use 999999.0 and it works fine.

[Powerlord]

Originally Posted by Phil25 If you want to test whether you will be able to attack after 3 years, be my guest ;)

I meant to read the value and see what it's set to. If it was clamped, you'd get whatever the game is allowing as the max value back.