this makes a lot more sense now. On Tue, Jan 20, 2015 at 12:19 PM, James Theunplesant <neonghost@xxxxxxxxx> wrote: > Who knew that you knew math? > > > James C Snyder > > I myself am made entirely of flaws, stitched together with good intentions. > Augusten Burroughs > > On Thu, Jan 15, 2015 at 11:34 PM, chris brooks <cebweb@xxxxxxxxx> wrote: > >> http://youtu.be/WQavsJEOmBo >> >> >> and a Guy on reddit explaining what he thinks is happening. >> >> My personal suspicion is that this relates to taking, say, >99.5% damage >> all at once (as would happen with an L96 to the chest at ~13m). >> >> As we all may recall, there was a time in BF3 when you could live with >> "0" health; if you had 0.49% or less, the display would round down to 0. >> >> The health counter still rounds to the nearest integer, but clearly >> they've made an exception for rounding to zero, as it no longer occurs. It >> *should* obviously round to 1, but maybe going straight from 100 to <0.5 >> breaks that particular line of code, causing it to instead remain at 100. >> >> I'd be interested to see if you could get a player to a different round >> integer (say 20%) and hit them with a weapon that does exactly that (say >> the MP7) from *just beyond* its max damage range (say 9m). That would do >> ~19.7 damage to a 20 health player and *should* either display 1% or 0%, >> but based on this may display 20%. >> >> *TL;DR* Going from 100% to <0.5% would normally cause your health to >> display 0%, because it rounds off. DICE presumably made an exception to the >> rounding so your health never displays 0%, so now it stays on 100% instead. >> >> >