It is what it is... a cannon that acts like an autoloader

So, I was reading the forums when I stubled upon one about making cannons fire in bursts

So I made a cannon that fires in bursts(well, I made a lot of versions of it, though a lot of them were just utter garbage)

Anyway, moving on, In this demonstrator, there are two cannons; Version 0.5.00 and Version 0.9.01(I kinda just made up those numbers, but I did try probably at least 25 versions of 3 different expressions)
We will assume the following :
- Reload Rate(seconds) = n
- Duration of Burst(seconds) = m

Version 0.5.00##

is highlighted in red

This uses a version of the first expression I came up with(it uses uses a basic repeat and smooth function):

floor(repeat(sum(clamp01(FireWeapons)), )) (n + m) >= n

This is pretty basic and less buggier than 0.9. But it does come with some downsides(well, one):
- To reload, you have to hold FireWeapons
- If you just consecutively tap the Fire Weapons button, you can fire more shots than what the "clip" supposedely has

Version 0.9.01

is highlighted in blue

This is a bit more complex(and incredibly messy). This is the second kind of expression I came up with:

smooth(n * clamp01(smooth(clamp01(FireWeapons) * m, FireWeapons = 1 ? 1 : clamp01(smooth(n * clamp01(sum(1) > .1),1) = n) ) != m),1 + (n * 10 * clamp01(smooth(clamp01(FireWeapons) * m, FireWeapons = 1 ? 1 : clamp01(smooth(n * clamp01(sum(1) > .1),1) = n)) = m))) = n

Sooooooo. Yes. Time to explain. Basically, what this does is it does not require you to hold FireWeapons in order for you to reload. Heck, if you don't press it for long enough, it "reloads" it even if it's not done with the burst sequence.
Now, you might be wondering, wtf is this smooth(n * clamp01(sum(1) > .1),1). Well, I realized that the a ? b : c operator only starts storing values for b or c when it is selected, and smooth(x,rate) automatically reverts to x at the start(it doesn't start from 0). So I had to make it so that every time c was active, the smooth function started from 0
Anyway, It functions like this; the first part checks whether the gun has been fired for m seconds. The second part initiates the reload. And lastly, the = 15 at the end checks whether the reload has been completed

Now, pros and cons:
- As stated earlier, you don't need to hold FireWeapons to reload
- Reloads automatically after n seconds, even when clip is not finished
- If you hold the FireWeapons for to long after the clip is finished, it resets the reload time(so after firing, don't hold; not a problem for mobile users I think)
- If you just consecutively tap the Fire Weapons button, you can fire more shots than what the "clip" supposedely has

Yes, the last point, I couldn't figure out a way to fix this. Well, I tried, but that would be expression 3, and we don't talk about no.3

Finally, if you want to compute for the delay of the gun, because you need to have a proper delay(This is not related to funky trees, but it has something to do with the functionality):

(ReloadRate/60 * RPM) / ClipSize

or you can just get some accurate stuff from the internet

P.S. I like the 0.9 better than the 0.5, even if it's a bit messy