Character -> Clone State "Alpha/Omega"

[Legedric]

It is absolutely critical for skill training calculations to know if a character is an Alpha or Omega clone. Unfortunatelythere isn't any information about this in ESI on the character or clone endpoints.

An extension of the character's public information (or a new non-public endpoint similar to XML CharacterSheet) like below would be great.

{ "ancestry_id": 19, "birthday": "2015-03-24T11:37:00Z", "bloodline_id": 3, "corporation_id": 109299958, "description": "", "gender": "male", "name": "CCP Bartender", "race_id": 2, "clone_state": "Alpha" }

[HakShak]

By no means will we be exposing account specific information on the character level. This was a large discussion with the CSM.

What will be happening for the skills endpoint is the addition of "active skill level". This should solve the skill training calculation problems. This may also need to include a "potential skill level" as well. That would be a more important discussion to have on another issue.

For now I will be closing this, but if there is more functionality around clone state that cannot be achieved, I would like to target the problem instead directly in another issue.

[markrwilkins]

Hey folks: (Note to non-CCPers, I'm not on Team Tech Co, so I'm asking from the standpoint of an API user.) It sounds to me like the functionality that's being requested is having some way to access one of (1) base character training rate (before implants/attributes), (2) current character training rate (after implants/attributes), or (3) completion time of skills in the queue rather than a direct query of account "alpha" vs. "omega" status. Maybe if a follow-up issue requested access to one or more of those, it might more directly address the issue and avoid questions of querying account data as such. (Nick's willingness to consider adding "active" vs. "potential" skill level indicates that it isn't necessarily a problem to be able to infer that account-level information, the question is whether it's exposed directly.)

…

On Tue, Nov 29, 2016 at 4:38 PM, Nicholas Herring ***@***.***> wrote: Closed #95 <#95>. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#95 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFGeUKtzeteibaIcrLK-4pkG1s7qHy-Vks5rDFUEgaJpZM4K1rdT> .

[Kupuyc]

It's not a problem of skill training speed only. For example I want to know clone status for sure that character should be kicked from teamspeak.

[polarina]

I want to know clone status for sure that character should be kicked from teamspeak.

Why would you want to kick Alpha players from Teamspeak?

[Kupuyc]

Why not? Spies for free, alliance politics, etc. Kick - just example. On the other hand it's good idea to set them TS group - to prevent join some channels or see that they are alpha players. A lot of examples.

[Legedric]

It is not only about training times but also about what the character is able to train. As the list of trainable skills is quite limited for an Alpha state clone we definitely need some kind of information about the clone state of a character to list the trainable skills for example.

[markrwilkins]

But, you do not need to know the clone state (which is a property of the account, not the skill), only whether the skills in question are trainable for the character (or any active limits.) - Mark

…

On Dec 6, 2016, at 8:49 AM, Chris K. ***@***.***> wrote: It is not only about training times but also about what the character is able to train. As the list of trainable skills is quite limited for an Alpha state clone we definitely need some kind of information about the clone state of a character to list the trainable skills for example. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[Legedric]

It doesn't matter what "label" CCP puts onto this but one way or another you have to know the clone state for a character. It doesn't matter if you provide something like a "trainable skills" list for each character, provide some kind of base training time multiplier (that determines the training speed) or just put a simple flag "clone state" on the character endpoint.

Whatever will get to the ESI at the end it will and it has to enable us 3rd party developers to "read" the clone state of a character from it, no matter how you call it. I understand that you do not want to expose it directly but exactly this (a simple flag on a character) would be a) sufficient and b) the simpliest solution.

I do understand you don't want to expose it directly but at the end of the day we (as 3rd party developers) will be able to read the clone state from a character so making the ESI part about this topic complex just to hide this status somewhere but with the same result (being still able to read it somewhere in some way) is somewhat inefficient from a development perspective.

For me personally it is still possible to let the user just flag a character as Alpha on my site, that's ok for me but that's not what a user may expect to do but expects to come from the API instead :)