Assembly Hall

[Proposal] Cloning Vat Change

Abstract:
Cloning Vat's are not used frequently, and I believe that with a few small changes more people would find them useful and utilize them.

At Present:
Currently, there are two shiptypes that can use cloning vats: Rorquals and Titans.
Both of these ships are sometimes used to install jump clones, more so the Rorqual. However, the main issue, is that the characters whom jump in will have no implants. Currently, these ships are more used as a method when a character needs another jumpclone, not when they are deploying to a new site.

The Proposal:
Allow the users to instal either a "fresh" jumpclone (like current), OR move one of there current jumpclones INTO the cloning vat from another location.
This can be done two ways. One way is to allow an offsite (one that you are not currently in) to be loaded into the vat.
OR
Your current clone get's loaded into the vat, forcing you to jumpclone to one of your other clones upon loading the vat.

Example:
I have 3 jumpclones.
A) Non-implant PvP clone.
B) Mining Implant and +3 sets.
C) +5 empire set.

Option 1
I am currently in jumpclone A. My corp wants to deploy in way off NPC 0.0 to do a mining op for the weekend. We rendezvous with the rorqual(s) in lowsec. After getting an invite to instal a clone I select from a drop down box which clone of all of my clones to select to install. I then select B as the installed clone.
Rorqual(s) move to target system, and all of us miners/haulers jump to rorqual(s) in our mining implant set.

Option 2
I am currently in jumpclone B. My corp wants to deploy in way off NPC 0.0 to do a mining op for the weekend. We rendezvous with the rorqual(s) in lowsec. After getting an invite to instal a clone, it asks me if I would like to instal a new clone, or current clone. I select current clone. Current clone gets loaded into rorqual, and I jumpclone to A or B.
We wait 24 hours. Rorqual(s) move to target system, and all of us miners/haulers jump to rorqual(s) in our mining implant set.

Hypothetical outcomes of change:
More small corps will use this for "weekend operations".
More corps will assume the risk/rewards of null/ lowsec.
PvPers will have more targets.

Conclusion:
It would be nice to see more versatility and usefulness out of cloning vats. One of these small changes may help pave the way for more corp ops, as well as corp bonding.


Anyone have any thought's of feedback?



-Ice

It's pretty odd that the one instance in which clone vat bays would legitimately be useful in - wormholes- is also the instance they're specifically banned for.

That said, I think the best way to make clone vats useful is to have a mechanic for remotely installed clones as above. Either by installing a new clone to an active clone vat in a fleet, or a system to move clones from an outpost (perhaps with some suitable outpost upgrade). There also has to be a system to jump back again afterward from the clone vat ship to a station.

It should also be possible to change medical clone settings at a nearby clone vat, even if you can't actually respawn there. There are plenty of characters that spend days or weeks away from stations, so the ability to remotely upgrade or move their clones would be very useful indeed.

Problem with the implant idea is the ships owner has the ability to destroy your jump clone, or the ship could be destroyed all together.

I'm sure everyone would appreciate getting their jump clone with billion isk implants destroyed just for kicks. :)

The option to upgrade a medical clone would be nice though.

You might also want to propose the idea of "unloading" the clone into a station. Cause there is a limit to the number of clones that can be in a clone vat, and i am sure the pilot won't want to have to choose which billion isk clone to destroy to allow someone else in the corp or alliance to create a jump clone.