EVE General Discussion

Too many rage responses.
I assume all of you wouldn't like an infinite hours skill queue.
(lol).

Fine, at least you keep training even if you run out of game time [/sarcasfm off]

yes.

CCP is selling their other customers the content that you create - and it is much more likely that you create content that other players are willing to pay for (e.g. by getting yourself blown up, trolling in some chat channel, ...) when you are logged in than when you aren't.

Also don't underestimate the power of corpmates who see you logging in during a supposed period of absence and guilt-trip you into joining their fleet.

People disagree with you. Nothing wrong with that. And yes, an infinite skill queue would be terrible.

I think that 24 hours is a bit low these days.

72 hours would be a bit more reasonable for characters around the 3-10mill SP area.

There are plenty of reasons why people may not be able to login/remember and if you lose a subbie at that stage then you're unlikely to get them back.

Not everyone uses OOG tools like Evemon at that stage of character development either.

I know the arguments for and against but I think its time the skill queue was extended a little.

Looking back, it took a disgustingly long time to implement.

I'm not going to disagree there, I just say: learning skills.

Maybe go back to zero and play again from scratch. All that time spent popping skills into queue without a clue and swapping them out as you realize it is more important to train something else immediately is somewhat engaging between and during tutorials.

It doesn't work on alts.

Even though I agree with you, listen to what others have said: if you know you will be seriously AFK for extended periods, put a really long train-time skill in the queue. I have used Minmatar Freighters V many times and it is still has 15 days on it !

My dream is to have an interface between EvEMon and EvE. Just set up a training plan in EvEMon and give it your API key - done - trains for the next year without intervention. Technologically it's possible, but you need both hardware and software to make it happen...

But I agree that I see no reason at all to limit the queue to a weird 24 hour rule with embedded gotchas.

This will be possible with the new CREST API CCP is building (it will have read/write capability to the TQ DB server). But I believe that CCP will not allow skill changing through it for obvious reasons.

It's laughable that the only grounds for keeping the current system is the reluctance for change. "That's how it has been for years" is not a justification for the queue being capped at 24 hours. If it can be improved, then it should be. There is little to no logical reason mandating a 24 hour cap.