Jump to content

Gause Er Lrg And Ac5 = Ct Dead Cataphract


3 replies to this topic

#1 Korps

    Member

  • PipPipPip
  • Bad Company
  • 55 posts
  • LocationRound Rock, Texas

Posted 18 September 2014 - 07:41 PM

how do those 3 weapons take out 71 armour and destroy a cataphract one hit each no other damage the whole match

those were the only hits recieved not even half the armour and it fell over dead.

No ammo in ct to explode

it is starting to feel like the armor allocation is backwards cause I can take a pounding in the RCT for ever and walk away is it possibly a bug or is there some kind of crit system in place for gauss I did not see or read about

#2 Hospy

    Member

  • PipPipPipPipPip
  • Knight Errant
  • Knight Errant
  • 162 posts

Posted 18 September 2014 - 07:51 PM

How do you know they only shot you once with each?

I mean, you can tell the number of large lasers, but the number of gauss and autocannon hits?

#3 Mcgral18

    Member

  • PipPipPipPipPipPipPipPipPipPipPipPip
  • CS 2019 Top 8 Qualifier
  • CS 2019 Top 8 Qualifier
  • 17,987 posts
  • LocationSnow

Posted 18 September 2014 - 07:56 PM

You were hit by multiple of the same system.

#4 DEMAX51

    Member

  • PipPipPipPipPipPipPipPipPip
  • Elite Founder
  • 2,269 posts
  • LocationThe cockpit of my Jenner

Posted 18 September 2014 - 07:59 PM

View PostHospy, on 18 September 2014 - 07:51 PM, said:

How do you know they only shot you once with each?

I mean, you can tell the number of large lasers, but the number of gauss and autocannon hits?

Indeed - if you're only going by the Death Screen readout, the number of each type of weapon that hit you isn't actually shown. It could have been dual Guass, multiple ER Larges (if you didn't see them hitting you, obviously), and multiple AC5s.

There is also, however, a hit-detection glitch that will occasionally apply damage taken on the front of your 'Mech to your Rear's armor - if you didn't look to see whether it was your front armor or rear armor that was gone on the Death Screen, that might be the culprit.





2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users