These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Player Features and Ideas Discussion

 
  • Topic is locked indefinitely.
 

Make kill mails accurate
Author
Previous Topic Next Topic
Tina Twinkletwhat
Blitzkrieg Collection
#1 - 2015-07-04 00:05:55 UTC  |  Edited by: Tina Twinkletwhat
Currently, kill mails are not accurate. I would like them changed to be accurate and reflect all pilots participation on a kill within the normal bounds of kill mail generation. The idea that a player could be on grid causing damage for the kill but not be listed on the kill mail blows my mind.

Yes, I could include a lot more information about this issue, but EULACry
Yes i know that there are lots of issues that could cause you not be listed on a kill mail but im not talking about those, im talking about inaccurate kill mail generation due to their priority for processing on the server.
Rowells
Blackwater USA Inc.
Pandemic Horde
#2 - 2015-07-04 00:09:55 UTC
That's usually bug/server hiccup.
Tina Twinkletwhat
Blitzkrieg Collection
#3 - 2015-07-04 00:11:16 UTC
Rowells wrote:
That's usually bug/server hiccup.


While I cannot give you the exact response I received from the GM because of EULA, i can tell you that it is not a bug.
Zan Shiro
Doomheim
#4 - 2015-07-04 04:49:38 UTC  |  Edited by: Zan Shiro
Tina Twinkletwhat wrote:
Rowells wrote:
That's usually bug/server hiccup.


While I cannot give you the exact response I received from the GM because of EULA, i can tell you that it is not a bug.



You mentioned priority of processing so will assume that is in the response.

That is CCP meeting M$ SQL server and SQL winning probably. Sometime with SQL server you work with it...but in no uncertain terms it will dictate how that will go down. As do the other RDBM's out there. Even good ole open source MySQL says at some point I am the Law and will tell you how its going to be once in a while.

CCP probable has a better vested interest in getting updates processed over reporting if this is conflict they face. The former clears up the db to hopefully stem the fide of lag/td. The latter does not.

To draw an analogy.

You have job that needs to get done now.

The former is the guy just hitting that job hard and getting her done.
The latter is the guy stopping work every minute or so, calling his boss and giving a status update.

One of the guys will get the job done much faster. Its not the guy giving status updates most likely.

That we get almost real time KM reporting is a gift really. Lets not look the gift horse in the mouth. As with most any realtime reporting you get some issues. I see this with even central logging service applications (run on dedicated hardware appliances) that get confused from time to time. These aren't cheap systems either....
Riot Girl
You'll Cowards Don't Even Smoke Crack
#5 - 2015-07-04 05:20:32 UTC
Tina Twinkletwhat wrote:
Rowells wrote:
That's usually bug/server hiccup.


While I cannot give you the exact response I received from the GM because of EULA, i can tell you that it is not a bug.

If you know how something works, you're allowed to explain how it works. It's not top secret information.

Oh god.
Kyeudo Van'mynai
Center for Advanced Studies
Gallente Federation
#6 - 2015-07-04 06:10:58 UTC  |  Edited by: Kyeudo Van'mynai
Riot Girl wrote:

If you know how something works, you're allowed to explain how it works. It's not top secret information.


Posting messages from GMs in public has gotten people banned for EULA violation in the past.