the staff don't need a anit-ddos ... they need to TAKE CARE OF THE SOURCE. And by source i mean the people hitting us over and over and over. The staff are smart enough to do just that.
no, i am implying that we need to either confront them about it, or take legal action.
Here is the thing though, do they have money to take legal action and do they have the resources to track them down. . . My guess is highly unlikely. I saw we turn this project to a private project and start a screening process.
Almost make it like a private torrent site in a way. . . Just my suggestion. That way we atleast know that only 100 people have the IP and if we are still getting DDoS, we know its on the inside
nononnononono this is a open project, for the people, not for a select group. This would only allow a certain community to play and everybody would know each other and almost never see new faces. What we need to do, is only allow a certain amount of connections to the ip at once from the same ip. This person is obviously sending hundreds or thousands of connections from his ip, so to prevent this, we need to code a thing where if more than two people log in it will say "Too many connections from the same address" and this will also help the multilogging situation going on. But the solution your suggesting, could only go downhill.