EVE Information Portal

I understand your point, but I have to point out that the code part that you keep referring to is actually very small, in the region of ~6MB for the code we've written. There are of course other code resources but the majority of the client is art and audio assets (approximately 11GB)

There are a few reasons why I wanted to go with Bittorrent, and none of them revolve around cost.

To explain, every time we patch, there are many people who exist behind restrictive proxies or bad networks that simply can't update their EVE client, with the only recourse being to fully re-download the entire thing. You can see what I mean if you take a spin through some of the other forums, for example here (21 pages), here (16 pages) and here (5 pages).

We have also seen people in various parts of the world getting low transfer rates, which compound the problem for a large client download. By implementing BitTorrent we can work towards solving both of these problems by using a protocol and framework that has been designed and tested for distributing large amounts of data. We no longer have to maintain a custom library, and can benefit from the wisdom of others, whilst also reducing my own burden of having to provide patches as a fallback, for people (which is an imperfect solution as it is).

We also have a nice technical benefit of being able to phase out the Repair Tool and SisiLauncher, further reducing our technical burden, since the single EVE Launcher will be able to service all these roles.

I understand that you don't want to help out other players, or open yourself up to any perceived vulnerabilities, but we're trying to help all the players, including the large quantity of people who simply don't read or comment on these forums. Those saying that "this will do nothing for me" are the lucky ones who are currently in a position where everything works as intended. I wish all our customers would be there, but unfortunately they aren't, and we have to provide a solution to help them play the game.

Well, this actually doesn't addressed anything of what I said. There's still no valid point, for me, to have this enabled by default. Ok, so you have a customers who can't use the current launcher and BT will solve their problem. That's fine and very cool of you guys to figure out a solution for them. That solution however can't be using someone elses bandwidth to do so.

In all honesty, I don't care about CCPs burden, nor do I care about the problems of anyone else. It's their problem. I'm not their product publisher. I'm not responsible for the gaming experience that they have. What do I get out of allowing CCP access to my bandwidth? Nothing? The warm fuzzy feeling of helping out a fellow player?

All the technical details are valid but don't require you to enable BT by default on the launcher. It's a simple point. You put the option in, you seed whatever is needed. Anyone who wants to use BT, gets the added bonus of "sharing" bandwidth with anyone else that's either downloading using BT or explicitly said "I want to seed!".

I think that your description of the new launcher, working almost as a source control for the binaries, is awesome. I thank you for all the work you guys put into it, but I can't see one single reason as to why the BT part is ON by default.

Even though I have no lack of bandwidth or have any privacy issues, the lack of "real reasoning" from CCPs part, besides "helping out", leads to say I will be blocking all BT traffic on my computer. It will simply have to behave as if I'm in some campus and have no BT.

Sorry mate :)

Funny thing is, if it were off by default, I'd probably have it seeding permanently ;) It's basically my way of saying "I don't agree with the way this is being "forced"".

And this is why we're providing the option to disable it. If we were truly forcing it, there wouldn't even be that option

You can do this in the current EVE Launcher, on Windows, by using the import/export functionality in the settings menu. We actually want to move away from multiple installs so that this won't be something that you need to do.

I currently have a steam install, and an non steam install. How will you enable the functionality to run Eve with or without steam using the same client install?

Easiest option is to junction the client to a new location. No extra space, but you're starting it from a new location, which means a new set of settings. http://wiki.eveonline.com/wiki/Multiple_clients

I have the exact schzoid installation as well. Will there be a migration path spelled out? I don't care whether I stay on Steam or completely off of it.

You better than any player know that 95% of the community doesn't read blogs, doesn't read the forum and simply doesn't care. Enabling it by default is basically taking advantage of all those people to solve your distribution problems. Seems like a sleazy move any way you slice it.

If it's good, people will enable it and use it. There's no need to basically "sneak" this into the launcher.

My 2 cents. I'll still be blocking all BT traffic in my computer just in case ... I'm too lazy to actually check if your launcher is doing what you say it's doing!

Ok ... This right here is where you (CCP) have fallen down so so so many times before.

If you are going to still have the current HTTP patch method for when the Torrent does not work, simply add a check box allowing users to "opt out" of the use of torrent technology.

It does not matter if a user has a solid technical reason why they do not want to use torrent technology, have some moral issue with it, or (as far as you may be concerned) are a member of the tinfoil hat club. If you give the users the option to opt out and use the tech that they already do and that you are planning on still supporting, you end all debate, push back, rabble rousing, or pitchfork wielding.


EDIT:


I got to page 8 before posting the above. After 8 pages of user posts and concerns and prog 10-12 dev responses nobody had said "You will be able to disable the torrent option". If you had thought to include that in the original post or included that in one of the first dev responses we would prob not now be on page 13.