DC++ Servers

[pylorns]

DC++ hashes your files that you would like to share - game patches, useful stuff, or... non-sanctioned file sharing.. while DC++ could be run for internet - its usually used just on a LAN. It's a client-server configuration so you have a server that directs the traffic and then client software that others install.

Think of it as a cross between an FTP server, a bit torrent server, and limewire/napster style with the exception that it's only accessable to your LAN - and you're not opening it up to the outside world.

Where windows file sharing fails is that the network overhead is too much - where as DC++ hashes your files into packets for transfer and doesn't kill your gaming. (it does slow the hard drive though... if you open up too many slots)

Anyway - no killing the network or the internet - like some dumb kid.

[JasonPowers]

DC++ hashes your files into packets for transfer and doesn't kill your gaming. (it does slow the hard drive though... if you open up too many slots)

I had to do some research to figure this out... I looked at how other LAN parties used this software (see forum links below), and I now understand not only how it works, but why they used it. It's all about file transfer. I read where one guy actually hashed 2.5TB so he could have it ready to share with his friends.

There are two types of LAN parties; those that focus on social (relational) interaction, and those that prefer a more competitive edge. We lean more toward the latter at our events. We've been to competition LAN's all over the United States; from New York to California.. Denver to Dallas. At those events, the tournaments are held in a separate area, using a network separate from the BYOC; this to protect latency. Every gamer dreads the word "lag", which basically means your network performance is slow. It doesn't matter how much you can transmit per second, but rather how fast can your signal get to where it counts. Obviously players who were allowed into the tournament area were there to compete, not to transfer files. That's what the BYOC is for.

And there's nothing like the BYOC; all those computers/players in one gigantic room. We've been to BYOC's that were close to 3k strong, like the CPL tournaments. But large or small, the BYOC can get pretty boring at times. With nothing to do, you're thinking, "Wow... I could be doing this at home". When Jordan and I first started these LAN parties, we decided we'd have zero "downtime"; that nobody would ever be bored, and that our schedule would reflect this endeavor. Because we love FPS games, we decided to run tournaments nonstop, and it's been a huge success. We have three FPS tournaments at our events; with upper and lower brackets. The way we pick teams ensures for an extremely even playing field, so you don't get knocked out first round. I believe that in the past five years we've had at least one tournament hit OT. Just doesn't get much better than that.

So.. as we're competing the majority of the time, one might argue that our entire event is a "tournament area". As a result, we strictly forbid any and all file transfer as it negatively effects latency. This is probably why neither of us has ever heard of DC++ file sharing; we simply have no need for that. Other, more "social" LAN parties, like the two I researched below, have found that software to be pretty useful:

Forums I referenced: Valhalla LAN Party and StreetGeek LAN Parties

[JordanPowers]

I usually have one server dedicated to hosting the games and the other server for patches and stuff. The DC++ is a good idea but I don't know enough about it to implement it yet. Most of the guys that show up to the tourney are already prepared with the latest patches and such or they just use steam and prefer to download if they have to format or something. Never had a problem with LAG at the LAN... like Jason said we have tourney's going around the clock so there really isn't time for porn sharing except after hours when everyone is asleep