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.
Previous page12
 

Jump Clone suggestion, little thing may change world

Author
Rivr Luzade
Coreli Corporation
Pandemic Legion
#21 - 2015-12-16 10:01:52 UTC
Alexis Nightwish wrote:
"Don't fly what you can't afford to lose."
Well, I've got my HGs in my head for 19 more hours, guess I won't be flying until then...

That is your decision. If you are afraid of not being able to "fly for 19 more hours" because you are in your precious HG Slaves, don't jump into your HG Slave set when you do not want to do things for 20 hours in that clone, or alternatively do not fly in an area of space where you can easily lose them, or do not fly ships with which you can easily lose them (that Sabre + HG set, by the way, is a ridiculous example. Only daft people would fly a sabre if they are in this kind of clone; thus, that example is moot as a reason for the change.).

UI Improvement Collective

My ridicule, heavy criticism and general pale outlook about your or CCP's ideas is nothing but an encouragement to prove me wrong. Give it a try.

Morrigan LeSante
Perkone
Caldari State
#22 - 2015-12-16 10:04:52 UTC
Amarisen Gream wrote:
Now - unlike many of the people above me, I do tend to fly in crazy expensive clones, but generally speaking only because I can be bothered with PVP'n for 30 minutes and having to wait the next 20 hours to JC again. Generally speaking, I will undock for larger fleet ops, but never do solo PVP.



Yes, for a fleet fight (or really anything well organised) that's fine but things like a rage undock or a T3D/frigate roam someone fancies then I'll decline as it's just not smart.

I mean, I've a bunch of alts it isn't the end of the world but it is stupid.

I like the overall cooldown as it is attached to travel, same station/system I wouldn't mind being looked at one day.
Xe'Cara'eos
A Big Enough Lever
#23 - 2015-12-16 11:35:56 UTC
Rivr Luzade wrote:
Alexis Nightwish wrote:
"Don't fly what you can't afford to lose."
Well, I've got my HGs in my head for 19 more hours, guess I won't be flying until then...

That is your decision. If you are afraid of not being able to "fly for 19 more hours" because you are in your precious HG Slaves, don't jump into your HG Slave set when you do not want to do things for 20 hours in that clone, or alternatively do not fly in an area of space where you can easily lose them, or do not fly ships with which you can easily lose them (that Sabre + HG set, by the way, is a ridiculous example. Only daft people would fly a sabre if they are in this kind of clone; thus, that example is moot as a reason for the change.).


what if (as is all too common), I've been on a bit of a break doing some long shifts, come back, hop into my PVE clone, then within about 5-6 hrs, someone invites me to a roam into low/null, and I'm thinking "I've got my expensive head on", I could travel to the location of the usual fleet form-up in about 20 mins, with a 'ceptor or cov-ops, and hop into the clone, so you're not preventing me travelling, just from going out and blowing **** up.

my point is, sometimes you don't know that a fleet is gonna form, or that someone IRL will say something that makes you wanna go and ruin someone elses day.

I don't see anything wrong with changing jump-clones at the same station without a timer (but maintain not allowed to STORE more than 1 jc/station)
Legacy code is likely the bigger issue.

For posting an idea into F&I: come up with idea, try and think how people could abuse this, try to fix your idea - loop the process until you can't see how it could be abused, then post to the forums to let us figure out how to abuse it..... If your idea can be abused, it [u]WILL[/u] be.

Morrigan LeSante
Perkone
Caldari State
#24 - 2015-12-16 13:54:21 UTC
Rivr Luzade wrote:
Alexis Nightwish wrote:
"Don't fly what you can't afford to lose."
Well, I've got my HGs in my head for 19 more hours, guess I won't be flying until then...

That is your decision. If you are afraid of not being able to "fly for 19 more hours" because you are in your precious HG Slaves, don't jump into your HG Slave set when you do not want to do things for 20 hours in that clone, or alternatively do not fly in an area of space where you can easily lose them, or do not fly ships with which you can easily lose them (that Sabre + HG set, by the way, is a ridiculous example. Only daft people would fly a sabre if they are in this kind of clone; thus, that example is moot as a reason for the change.).



That's entirely my point.

I risk my implants when I fly in them. I'm happy in an armor machariel fleet with triage using HG slaves. I risk them there and I get benefits meriting the cost and the risk (massive cost, massive gain, acceptable risk terms).

However in that clone I would NEVER fly a dictor. This means what when spontaneous content arrives which requires "I NEED DICTORS AT XXXX NOW!" that means the HG toon isn't going. Flat out not happening, ever.

The question at hand is simply: Is that healthy? As I say, it's no skin off my nose, I'll play fallout. But those who would fight with me, or against me? They lose out, because of a risk and decision I took hours before.

We could argue that "hangover" of the clone jump timer is additional punishment for jumping in the first place but that's ass backwards because if that where the case, the cooldown would in fact be a blocker that you need to wait down before first jumping (like when you biomass). This would also suck, by the way.

The limitation to stop mass instant transit is good, lifting that limitation to same station clones would also be good.

For my personal viewpoint it would ONLY increase my availability to interact with others - and honestly, that can only be good on the whole. Certainly one could say no-one is forcing me to stay logged off/docked however I do not think anyone would seriously contend that such action is anything but smart?

I suppose it comes down to the value people place on content which might have been.
Donnachadh
United Allegiance of Undesirables
#25 - 2015-12-16 14:52:30 UTC
Neither for or against this idea, just some thoughts I did not see addressed and the basis for my comments is best illustrated by this part of a post by Morrigan LeSante.

Morrigan LeSante wrote:
However in that clone I would NEVER fly a dictor. This means what when spontaneous content arrives which requires "I NEED DICTORS AT XXXX NOW!" that means the HG toon isn't going. Flat out not happening, ever.

To be blunt here you want to change your ability to project force at a moments notice and not only the force you personally can project, but the ability of your entire fleet / corp / alliance as well. I understand and could even support the idea of unrestricted same station clone jumping from a fun / hr basis I am not convinced that it should out weight the potential for affecting force projection on a more localized scale.

For this next one we have to accept that there are no technical limitations that keep you from having multiple jump clones in a single station. Whether that is true now or in the future is not relevant to the basic idea here so we will ignore that part.
How many jump clones do we allow?
Can you have 2, or maybe all of them all in the same station?
How does this affect force projection on a more localized scale when every player can have the "perfect" clone available in whatever station they need them in.

In the end assessment and I know this is un-popular but I think CCP needs to just remove ALL implants in the game they are a huge balance issue that ALWAYS tips the scales in favor of those who have the most ISK to spend. To me the cost and ability differences the various fitting pieces bring to the table are enough of a boost for those with large ISK reserves they do not need the added advantage given by implants.
Khan Wrenth
Viziam
Amarr Empire
#26 - 2015-12-16 14:55:40 UTC
Same station may never happen because of legacy code, but if this idea came under reconsideration by the devs, it could be implemented through same system jumping.

Or, if they're feeling generous, I thought it would be nice to actually have a slightly more scaled system. Right now we have "Infomorph Synchronizing" skill which reduces cooldown by 1 hour per level. Let's keep that in mind and make a new system where you generate cooldown based on number of systems between clones (a system like this is already in place for calculating distances between stations for station trading). Each systems between the clones creates 10 hours of cooldown, up to the limit of 24. But...with the Synch skill, reduces that cooldown to 5 hours per system. So, if you jump within the same system to a different station - no cooldown. If you jump to the next system over, 5 hours. Three systems over, 15 hours.

Jump fatigue is more nuanced based on distance, with the oft-said message of "you don't generate fatigue if you use gates". So if you don't try to fast-travel, you get no fatigue. Well, why not bring some of that slack to jump cloning? If you don't use it for fast travel, get no fatigue. If you do use to for travel, generate fatigue rapidly.

Yes, I know it's been shot down before, but things get reconsidered from time to time. I keep thinking to myself that the HIC focused scram buff is going to be reconsidered eventually. But, for either case, I don't hold my breath.
zielonyPL
Caldari Provisions
Caldari State
#27 - 2015-12-19 17:10:44 UTC
Khan Wrenth wrote:
Same station may never happen because of legacy code, but if this idea came under reconsideration by the devs, it could be implemented through same system jumping.

Or, if they're feeling generous, I thought it would be nice to actually have a slightly more scaled system. Right now we have "Infomorph Synchronizing" skill which reduces cooldown by 1 hour per level. Let's keep that in mind and make a new system where you generate cooldown based on number of systems between clones (a system like this is already in place for calculating distances between stations for station trading). Each systems between the clones creates 10 hours of cooldown, up to the limit of 24. But...with the Synch skill, reduces that cooldown to 5 hours per system. So, if you jump within the same system to a different station - no cooldown. If you jump to the next system over, 5 hours. Three systems over, 15 hours.

Jump fatigue is more nuanced based on distance, with the oft-said message of "you don't generate fatigue if you use gates". So if you don't try to fast-travel, you get no fatigue. Well, why not bring some of that slack to jump cloning? If you don't use it for fast travel, get no fatigue. If you do use to for travel, generate fatigue rapidly.

Yes, I know it's been shot down before, but things get reconsidered from time to time. I keep thinking to myself that the HIC focused scram buff is going to be reconsidered eventually. But, for either case, I don't hold my breath.



Very good idea my friend, i hope CPP read this, and takin that serious ;)
Previous page12