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

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

EVE General Discussion

 
  • Topic is locked indefinitely.
Previous page12
 

Clone jumping destroying implants - WHY
Author
Previous Topic Next Topic
Malcanis
Vanishing Point.
The Initiative.
#21 - 2016-12-09 11:50:17 UTC
Vortexo VonBrenner wrote:
Don't we get a warning now, at least?


We always did. Some people disabled theirs.

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

Grath Telkin, 11.10.2016
Major Trant
Brutor Tribe
Minmatar Republic
#22 - 2016-12-09 12:09:43 UTC
Caviar Liberta wrote:
However with the new citadels you can have multiple jump clones in it and you can jump between them with no cool down period as long as it's the same citadel.

You can't store multiple clones in the same Citadel.
Marcus Binchiette
Federal Vanguard
#23 - 2016-12-09 17:00:20 UTC  |  Edited by: Marcus Binchiette
I don't have any issue with the one clone per station limitation. But, the language in the error message is unclear and frankly it creates an extremely annoying problem.

Okay, so you have a clone installed at home station with some rather expensive implants. Because you died previously, you end up in a medical clone at the home station, and then soon after want to clone jump back into the region where you previously died.

But, an error message pops up saying "there is already a clone located here. If you clone jump then your current clone located here will be destroyed". So, you accept this, because, you only need one clone in the home system. But instead of destroying your current clone, (which is completely clean), it goes and destroys the damned stored clone with all the expensive implants.

WTF CCP..... If you say you're going to destroy the CURRENT CLONE. Then destroy the bloody current clone! Not the one which is inactive. Saying that you're going to destroy the, "current clone located here", does not tell me whether you're going to destroy the current inactive clone located here, or the current active clone located here. So, if you're not going to change this please at least provide some clarity and consistency between what you say, and what will actually happen...

Or better yet, please give me some control over which clone is going to be destroyed. I would have actually preferred the active clone as the default clone to be discarded. Because, I already have the option to discard inactive clones. I don't have that option with the active one.
Princess Adhara
University of Caille
Gallente Federation
#24 - 2016-12-10 02:36:34 UTC
Marcus Binchiette wrote:
I don't have any issue with the one clone per station limitation. But, the language in the error message is unclear and frankly it creates an extremely annoying problem.

Okay, so you have a clone installed at home station with some rather expensive implants. Because you died previously, you end up in a medical clone at the home station, and then soon after want to clone jump back into the region where you previously died.

But, an error message pops up saying "there is already a clone located here. If you clone jump then your current clone located here will be destroyed". So, you accept this, because, you only need one clone in the home system. But instead of destroying your current clone, (which is completely clean), it goes and destroys the damned stored clone with all the expensive implants.

WTF CCP..... If you say you're going to destroy the CURRENT CLONE. Then destroy the bloody current clone! Not the one which is inactive. Saying that you're going to destroy the, "current clone located here", does not tell me whether you're going to destroy the current inactive clone located here, or the current active clone located here. So, if you're not going to change this please at least provide some clarity and consistency between what you say, and what will actually happen...

Or better yet, please give me some control over which clone is going to be destroyed. I would have actually preferred the active clone as the default clone to be discarded. Because, I already have the option to discard inactive clones. I don't have that option with the active one.


Maybe that's because "you" <> "your current clone"?
"you" = "you who are reading the error message right now"
"your current clone" = "that suspended animation body lying somewhere in the station"
Nicolai Serkanner
Incredible.
Brave Collective
#25 - 2016-12-10 12:24:08 UTC
Marcus Binchiette wrote:
I don't have any issue with the one clone per station limitation. But, the language in the error message is unclear and frankly it creates an extremely annoying problem.

Okay, so you have a clone installed at home station with some rather expensive implants. Because you died previously, you end up in a medical clone at the home station, and then soon after want to clone jump back into the region where you previously died.

But, an error message pops up saying "there is already a clone located here. If you clone jump then your current clone located here will be destroyed". So, you accept this, because, you only need one clone in the home system. But instead of destroying your current clone, (which is completely clean), it goes and destroys the damned stored clone with all the expensive implants.

WTF CCP..... If you say you're going to destroy the CURRENT CLONE. Then destroy the bloody current clone! Not the one which is inactive. Saying that you're going to destroy the, "current clone located here", does not tell me whether you're going to destroy the current inactive clone located here, or the current active clone located here. So, if you're not going to change this please at least provide some clarity and consistency between what you say, and what will actually happen...

Or better yet, please give me some control over which clone is going to be destroyed. I would have actually preferred the active clone as the default clone to be discarded. Because, I already have the option to discard inactive clones. I don't have that option with the active one.


nm
AlexHalstead
Viziam
Amarr Empire
#26 - 2016-12-10 13:05:34 UTC
Princess Adhara wrote:
Marcus Binchiette wrote:
I don't have any issue with the one clone per station limitation. But, the language in the error message is unclear and frankly it creates an extremely annoying problem.

Okay, so you have a clone installed at home station with some rather expensive implants. Because you died previously, you end up in a medical clone at the home station, and then soon after want to clone jump back into the region where you previously died.

But, an error message pops up saying "there is already a clone located here. If you clone jump then your current clone located here will be destroyed". So, you accept this, because, you only need one clone in the home system. But instead of destroying your current clone, (which is completely clean), it goes and destroys the damned stored clone with all the expensive implants.

WTF CCP..... If you say you're going to destroy the CURRENT CLONE. Then destroy the bloody current clone! Not the one which is inactive. Saying that you're going to destroy the, "current clone located here", does not tell me whether you're going to destroy the current inactive clone located here, or the current active clone located here. So, if you're not going to change this please at least provide some clarity and consistency between what you say, and what will actually happen...

Or better yet, please give me some control over which clone is going to be destroyed. I would have actually preferred the active clone as the default clone to be discarded. Because, I already have the option to discard inactive clones. I don't have that option with the active one.


Maybe that's because "you" <> "your current clone"?
"you" = "you who are reading the error message right now"
"your current clone" = "that suspended animation body lying somewhere in the station"

That's bad language. Lost in translation or something. If the pop up said current clone one would not be in error to assume that's the clone the player is active in. If it said older clone will be destroyed then it would had cut down complaints about losing the clone with implants and actually describe what would happen.
Previous page12