#21

I don’t think this is correct? -80% shield delay means dividing the shield delay by 1.8. So a Bee with 6.16s delay should be 3.42s and at -40% delay 4.4s. It certainly feels that way to me. Which also means that even at really large badass rank you can’t have a 0.00s shield delay. (Unless there’s something in the code that would truncate/round down to 0)

2 Likes
#22

I have to say, this is some damn good info. Thank you for firing up the science blender, mine is in the shop. :+1: :wink: I’m going to link to your post in the DLC gear thread in case anyone cruising over there wants to have a look. Thank you for the good works my dude.

4 Likes
#23

You’re right. I should have checked before taking a tooltip at face value. :man_facepalming:

I recorded the delay time after dropping a grenade at my feet. Recording is 30 FPS, so there’s a 33 ms window of error, or about 0.033 seconds. Blue is your calculated value, yellow is my measured value. In both cases the result is right at what you calculated.

Base delay: 5.74
Div by 1.4: 4.1
5/5 Ward: 4.07
Div by 1.8: 3.19
10/5 Ward: 3.15

I don’t use BAR, so I hadn’t really thought about the potential to hit -100%. I can definitely feel the difference between the 4.04 and 5.20 second delays on my old Bee (7.28 delay), even though 1.2 seconds doesn’t seem that impressive.

2 Likes