Jump to content

More Informative Killboards?


6 replies to this topic

#1 wamX

    Member

  • PipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 57 posts
  • Twitch: Link
  • LocationUnited States

Posted 23 July 2015 - 12:42 PM

So you've been destroyed, almost randomly. How? By what? What hit you? Looking at the immediate post death screen, I see my battlemechs damage readout; okay, my three torsos are gone and I'm missing a leg... okay I guess I got cored, but by what? Scanning the middle panel I'm greeted by "Damaged by this" , "Damaged by that", "Arm destroyed". And lastly how I did up till my death. So... how did I die?

Perhaps we need a more informative kill board. One that states who, what, and where.


For example:

Instead of

Jagermech_Player [has killed] Catapult_Player

Perhaps we could implement this:

Jagermech_Player [AC/5] [CT] Catapult_Player

Reading that I know exactly what did the killing blow and I dont have to sift through a bunch of junk information.

Just a simple weapon listing and then the shorthand for the death:

[CT] - Center Torso Destroyed
[XL-RT] - Engine Destroyed in the Right Torso (For XL engines)
[XL-LT] - Engine Destroyed in the Left Torso (For XL engines)
[HD] - Headshot
[LL] - Legged mech killed with left leg remaining
[RL] Legged mech killed with right leg remaining

And then the additional death codes for:

[EJT] - Pilot Ejected
[OHT] - Overheat death (like shutting down on Terra Therma in the volcano)
[XOHT] - Overridden Heat Death
[MASC] - MASC Leg Destruction
[WEXP] - Weapon Explosion Cause
[OBND] - Out of bounds death
[FALL] - Falling Damage related death.

Just some full examples now:

wamX [C-ER-PPC] [CT] Enemy(A) --- PPC cored enemy mech

wamX [GAUSS RIFLE] [HD] Enemy(A) --- Gauss Rifle headshot

wamX [LARGE LASER] [XL-RT] Enemy(A) --- XL engine destruction

wamX [LRM20] [LL] Enemy(A) --- LRM volley that finished off a legged enemy

wamX [EJT] wamX --- I ejected in CW

wamX [XOHT] wamX --- I overrode my shutdown... rather carelessly

wamX [MASC] wamX --- I left MASC on for too long

#2 CDLord HHGD

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Legendary Founder
  • Legendary Founder
  • 9,190 posts
  • Location"You're not comp if you're not stock."

Posted 23 July 2015 - 12:58 PM

I loved the post match printouts from the Tesla Mechwarrior Firestorm pods.... Hilarious.

#3 bad arcade kitty

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Bridesmaid
  • 5,100 posts

Posted 23 July 2015 - 01:10 PM

do you expect me to learn those codes ><

#4 wamX

    Member

  • PipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 57 posts
  • Twitch: Link
  • LocationUnited States

Posted 23 July 2015 - 01:51 PM

View Postbad arcade kitty, on 23 July 2015 - 01:10 PM, said:

do you expect me to learn those codes ><


They could be changed and modified to be easier to read, or they can be simply left as "Overheating" or "MASC Failure" either way if it were to be implemented.

#5 Clit Beastwood

    Member

  • PipPipPipPipPipPipPipPipPip
  • 2,262 posts
  • LocationSouthern California

Posted 23 July 2015 - 02:01 PM

But why? It does say what killed you when you die. Is this a "just because" idea, or is there a particular destination in mind?

#6 wamX

    Member

  • PipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 57 posts
  • Twitch: Link
  • LocationUnited States

Posted 23 July 2015 - 02:18 PM

View PostFierostetz, on 23 July 2015 - 02:01 PM, said:

But why? It does say what killed you when you die. Is this a "just because" idea, or is there a particular destination in mind?


When I die in game it does say things like engine destroyed and legs destroyed but for a destination I would suppose it would provide clarity to kills in game, also it would confirm headshot kills for players making it easier to track where players are on their achievements. Perhaps it could open opportunities for more achievements (specific kill types) and an ever increasingly needed more advanced skill tracker into MWO by taking into account kill styles and the like.

Just a collection of thoughts to start with as usual.

#7 MrJeffers

    Member

  • PipPipPipPipPipPipPip
  • 796 posts
  • LocationThe Rock

Posted 23 July 2015 - 04:26 PM

I'd rather they just gave us a local battle log file like most MMOs have so that people who want to know the details and stats can track it themselves. Wouldn't put any strain on the servers since it would be all just the local client recording and would help track or identify issues like hit-reg problems vs aim problems.

Edited by MrJeffers, 23 July 2015 - 04:26 PM.






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users