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

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

Jita Park Speakers Corner

 
  • Topic is locked indefinitely.
 

Remove NPC corps from employment history
Author
Previous Topic Next Topic
Khadhir Hashul
Ministry of War
Amarr Empire
#1 - 2014-04-29 07:07:45 UTC
They're unnecessary lag-inducing clutter, especially if one changes corps more than once throughout their EVE career. They should be invisible in the employment history. Is there really any reason that they should continue to be visible?
Kaarous Aldurald
Black Hydra Consortium.
#2 - 2014-04-29 09:52:39 UTC
It actually does give some information, actually. So it's not "unnecessary".

For instance, it can tell you if someone swapped corp between two player corps, or may have been kicked out of their last one into an NPC corp.

Then you get to ask why.

As for being lag inducing, I will agree there. Try opening Psychotic Monk's corp history. The last time I did that it actually crashed my client.

"Verily, I have often laughed at the weaklings who thought themselves good because they had no claws."

One of ours, ten of theirs.

Best Meltdown Ever.
Revolution Rising
Last-Light Holdings
#3 - 2014-05-12 05:04:23 UTC
I rarely leave corp and don't go into an NPC corp. Most of the time I am leaving a corp because of burnout and just want a rest from ... all the people ;)

I don't think you'd find too much "valuable information" in the NPC corps in my corp history.
(I don't think I've EVER been kicked from a corp - altho it's been many years perhaps..)

.
Benny Ohu
Royal Amarr Institute
Amarr Empire
#4 - 2014-05-12 05:19:47 UTC  |  Edited by: Benny Ohu
Kaarous Aldurald wrote:
For instance, it can tell you if someone swapped corp between two player corps, or may have been kicked out of their last one into an NPC corp.

that info can also be gained from player corp join/leave dates, so nothing's lost by dropping npc corps from corp history

it might also be useful to allow players to set a default timeframe for the corp history display. for example, the default would be three months with a dropdown menu to increase that to six months, a year or all-time. the same way the market history works.

e: not knowing how computers or the client actually work, i imagine the client'd say to the server 'send me three months of player x's corp history' instead of asking for the lot
Draconian Maass
Diadem Enterprise
#5 - 2014-05-30 05:21:29 UTC
I think it wouldn't me much of a problem to see this info go away. But since we are on the subject. I think there can be more info on the corp log like whether or not someone was kicked or left mabe even some notes from the last employer like a resume.
Malcanis
Vanishing Point.
The Initiative.
#6 - 2014-05-30 07:21:26 UTC
Khadhir Hashul wrote:
They're unnecessary lag-inducing clutter, especially if one changes corps more than once throughout their EVE career. They should be invisible in the employment history. Is there really any reason that they should continue to be visible?


How do they cause lag?

"Just remember later that I warned against any change to jump ranges or fatigue. You earned whats coming."

Grath Telkin, 11.10.2016
Benny Ohu
Royal Amarr Institute
Amarr Empire
#7 - 2014-05-30 08:13:11 UTC
Malcanis wrote:
Khadhir Hashul wrote:
They're unnecessary lag-inducing clutter, especially if one changes corps more than once throughout their EVE career. They should be invisible in the employment history. Is there really any reason that they should continue to be visible?


How do they cause lag?


A long employment history can take an annoyingly lengthly time to load, and can disable your client in space. NPC corps add to the list, it's possible their inclusion increases the time the history takes to load.
Khadhir Hashul
Ministry of War
Amarr Empire
#8 - 2014-05-31 05:15:45 UTC
Malcanis wrote:
Khadhir Hashul wrote:
They're unnecessary lag-inducing clutter, especially if one changes corps more than once throughout their EVE career. They should be invisible in the employment history. Is there really any reason that they should continue to be visible?


How do they cause lag?




Allow me to illustrate: http://www.youtube.com/watch?v=H5W0Dm0K95Q&feature=youtu.be
Malcanis
Vanishing Point.
The Initiative.
#9 - 2014-06-01 12:32:27 UTC
Benny Ohu wrote:
Malcanis wrote:
Khadhir Hashul wrote:
They're unnecessary lag-inducing clutter, especially if one changes corps more than once throughout their EVE career. They should be invisible in the employment history. Is there really any reason that they should continue to be visible?


How do they cause lag?


A long employment history can take an annoyingly lengthly time to load, and can disable your client in space. NPC corps add to the list, it's possible their inclusion increases the time the history takes to load.


Huh I didn't know that. Sounds like some optimisation of what should be a pretty tiny text file reference is in order.

"Just remember later that I warned against any change to jump ranges or fatigue. You earned whats coming."

Grath Telkin, 11.10.2016
Meytal
Doomheim
#10 - 2014-06-02 16:26:53 UTC
Malcanis wrote:
Huh I didn't know that. Sounds like some optimisation of what should be a pretty tiny text file reference is in order.

It's actually not just reading a few lines of text from the database.

At a minimum, it checks each corp in the list to determine whether that corp still exists or has since closed, resulting in multiple database calls between client and server. It may even do more than this behind the scenes that players aren't aware of.
Malcanis
Vanishing Point.
The Initiative.
#11 - 2014-06-02 17:11:48 UTC
Meytal wrote:
Malcanis wrote:
Huh I didn't know that. Sounds like some optimisation of what should be a pretty tiny text file reference is in order.

It's actually not just reading a few lines of text from the database.

At a minimum, it checks each corp in the list to determine whether that corp still exists or has since closed, resulting in multiple database calls between client and server. It may even do more than this behind the scenes that players aren't aware of.


Those the kind of slow changing data that can be updated on a batch run eg: DT

"Just remember later that I warned against any change to jump ranges or fatigue. You earned whats coming."

Grath Telkin, 11.10.2016
Meytal
Doomheim
#12 - 2014-06-03 12:00:07 UTC
Malcanis wrote:
Meytal wrote:
Malcanis wrote:
Huh I didn't know that. Sounds like some optimisation of what should be a pretty tiny text file reference is in order.

It's actually not just reading a few lines of text from the database.

At a minimum, it checks each corp in the list to determine whether that corp still exists or has since closed, resulting in multiple database calls between client and server. It may even do more than this behind the scenes that players aren't aware of.


Those the kind of slow changing data that can be updated on a batch run eg: DT

True, though you lose some accuracy. Only the closed corps can really be cached long-term if you want to be accurate.

And if we don't care about accuracy in this information anymore, there's no need to report it, really :) Which is actually an option: no longer report the "(closed)" status of corps in Employment History? Interested parties can always look up the corps themselves anyway.
Tipa Riot
Federal Navy Academy
Gallente Federation
#13 - 2014-06-07 18:05:21 UTC
IMO there are two major use cases for reading the corp history: 1) quick check about age and recent affiliations during fights or short encounters, and 2) careful evaluation in case of long term engagement or if high values are involved. The first has to be executed without lag, but you only need the birthdate and the last let's say 5 corps. For the second reason you can just offer a 'detailed' button which expands to the full info and may take some seconds.

I'm my own NPC alt.
Iain Cariaba
#14 - 2014-06-12 15:52:20 UTC
So cyno and cloaky camper alts get no employment history at all?