Player Features and Ideas Discussion

Seriously, why is this "feature" (impediment) even there? You've cleverly set up a game structure wherein skills are trained in real time...so to a large extent, my $15 a month is at work even when I'm not playing the game. Which makes me super pissed when I log in to see that my pilot hasn't been training for the last XX hours because I foolishly forgot to restart my skill training after that last clone jump.

You may be thinking "That's totally your fault, quit being a tard". I agree. It is my fault. My point is that the entire mechanic is unnecessary and annoying. It's not like EvE is an easy game to start with. The layers of detail and minutae are overwhelming. Being acknowledged as a difficult game doesn't justify putting in little "traps" like this which change logging in from a fun experience to a "*#&$$WTFBBQ I haven't been training these last two days" experience.

So, please CCP, remove this nastly little pitfall would you? It serves no purpose at all other than to **** off your customers.

Of course there's something that can be done about it...the whole game is just a bunch of ones and zeros. Rearrange some of them.

The question is whether CCP will bother putting in the time to fix the issue. Sadly my guess is no.

Why not just code the jump to pause skills at beginning of jump and unpause after? Not hard at all.

Spoken like a true computer illiterate.

However, the OP does have a point, it is entirely feasible to cause the clone jump method to call the pauseTraining() method before executing the jump and the resumeTraining() method afterwards (I don't know the exact internal names, but you get the point). The exact same thing should happen when you plug in implants too. It isn't exactly a priority project, but it would be nice to see some day (one of those 'low hanging fruit' fixes).

I like the fact that you have to pause skills before you jump because it prevents accidentally jumping. While incidents where this could happen are few, if you were, say, looking at implants of your different clones with this new feature implemented, you could possibly lose all implants if you were sitting in a station with an extra clone before you jumped. Furthermore, it could land you in the middle of a station surrounded by hostiles with no ships and therefore are stuck for 24 hours.

Again, very limited circumstances, but I like it for that extra layer of idiot-proof-ness

I see your point, but the same end is better achieved with a simple confirmation popup. They already have one alerting you to unintentional clone destruction.

I do not think that would be the same thing. For implants you have to actively right click and choose the option to even try to do it. Meanwhile, theres that big red evil JUMP button.

lol, I find it amusing how you instantly assume that you know both my age and proficiency with computers and assume that you are superior to me (or know anything about me at all). I was simply addressing your post that "..the whole game is just a bunch of ones and zeros. Rearrange some of them." Yes, it might boil down to binary data, but it is grossly understating the complexity of reworking the system to remove the need to pause skills before clone jumping and is the kind of statement that people who know nothing about programming often make.

And, as I went on to say in my post, I know it's completely feasible to make a system that would keep from making you pause/unpause skills before and after each clone jump and implant. I even gave an example of the simplest way to do so without having to do a complete overhaul of any major code.

That's what you think. Allow me to give a few pointers why it might be not that easy:

• The state must be saved. The character might not be training a skill at all before jumping, maybe for the valid reason that another character on the same account is training. In that case, after the jump, training should not be restarted.
• Depending on the initialization of the character after the jump, the restart of the skill queue may need to be delayed, because there might be a time window where the implants are not properly initialized, so that starting training at that point would effect in starting training with no implants. Or worse, attributes set to zero.
• Changes in skill times must be observed. If you jump into a clone with worse implants (or none at all), skills might drop off at the end of the queue.

Too much hassle to counter the thoughtlessnes of a single user. It's not that the lit icon, the tooltip messages of said icon and maybe the warning message in the CQ (if enabled) already don't give it away that there is something amiss.

To be honest, I do have a clone somewhere, but I do not use it all that much. However I never forgot the restart my skills when I did.

I will say it is a bit of a pain to have to feck around with pausing and unpausing when jumping, but there are more serious issues to be delt with out there. (The automatic pause/unpause on jump is a good fix, I and I would guess, fairly easy to implement fix).

Oh, and I gave you a 'like' for the name Mr. Sparklypants!

Cheers!
Fly Safe!