Actually no ?
Originally posted by Nick Brockdorff
Just looked through the thread, and didn't see a definition of BPS ?
But - if the MS start off the rule by defining that "BPS is the space between any two shots, multiplied into the number of shots attainable in a second" (or something similar), that would be fine with me, and put this whole debate on the definition of BPS to bed.
The point is, that because "BPS" may be an industry standard to the techies - it is not to the players - and as the rulebook is written for the players, it should be worded in a way that leaves no room for interpretation...... Interpretation is what gives you another Toulouse, with scores of players banned without intentionally breaking the gun rules.
Nick, should they define every word that might confuse people? Maybe I guess?
BPS, defines itself. Balls Per Second.
That is the definition, and since it's 'per' it's obviously a rate.
But then I guess it isn't for some.
Stunned.
I think they spell it out VERY clearly in saying no shots closer than X ms, which results in a rof of 15.X
The important part being no shots closer than Xms.
I would suggest we don't confuse people by adding more stuff. Just tell them their guns can't fire more than two shots within X ms.
I guess if you want to teach people how to work out rates and what it means that doesn't bother me.
Originally posted by Nick Brockdorff
What then remains, is the whole "buffering/storing" issue, which I think you should look at more closely, as without buffering, you are dropping ROFs way below 10 effectively.
I agree.
The wording is confusing. Is buffering allowed for a single trigger activation to smooth out the inputs?
What do they mean by 'storing shots'.
I don't think you have a hope in hell to tell if a gun is buffering shots, and heck after the gun goes into ramp mode it has to be...
The rule doesn't make sense there.
If you don't allow people to buffer input signals... it will be done anyway and I doubt it will be something you can catch.