Forum

As the person that modified weaponpicker, I can confirm that as of right now it works - without honor of course.  My suspicion is that people (admins) voted out mods because they were tired of seeing people populate those servers vs coming to a regular (their) server.  Players, 'pro' or not, can always choose where they want to play.  Mods were not forced upon 'pro' players at all.  82nd's pipeline with weaponpicker was extremely popular.  We also ran regular servers.  Our only agenda was about seeing what players liked and had nothing to do with cheating the honor system.  I can see some truth in that 'pro' players were 'disappointed' with the mod players, and I think a bias exists here but really,  I think the 'pro' players were not willing to sit in a server and get it populated with other 'pro' players to keep their own servers populated.  Of course the players that liked the modded servers never got on here and voted on it, and so now you have this community, not a majority of players.  Which is fine I guess, since they're the ones actively keeping the game alive.  In the end, game/server popularity won't come from allowing or banning mods.  It comes down to having active, enjoyable admins manning the servers, which is why I think your idea of using a mod forceclassing for players isn't the best solution.  The best solution is to have admins in the server actively playing and doing this, and not all the time. 

These attacks are botnet attacks directly targeting the AA gameport and the queryport (+1).  They are using an exploit in the Unreal 2.5 engine that causes high (100%)  cpu utilization of the server (thus crashing AA and lagging any other server program like httpd, teamspeak, ect) when sending malformed packets to the game and query ports.  So, if you are NOT running the default ports (1716), an attacker still has to find your IP and Ports.  To do this, I suspect they're grabbing a list of IPs and ports off of Battletracker.  If not, they're simply clicking through the Assist client server list and gathering the information, or worse they're getting this information from Assist by other means.  My point is, if you take your server off of Battletracker, and if Assist did not give ip/port information (which it doesn't need to) and you DO NOT RUN THE STANDARD PORT then the attacker would have to connect to every server to get that information.  A determined attacker can do what they want.  You can just restart your server with the -Port= option with a random port and the ongoing DDOS doesn't affect AA server anymore. The attacker's information becomes old quickly. Somebody doing it for the fun and lulz might not bother doing this with a bunch of servers if the information was harder to get to.

What they seem to be doing is going down a list of multiple servers when they do the attacks.  Where they get that list of ips/ports, I am not sure if it's Battletracker (which publishes XML sources of ips), or if they're going into the assist client and writing/copying the addresses down.  If the address information was blocked from the Assist client, to get information on each server they would have to connect to each server and use networking tools to get the ip/port information.  So, they would have to work harder for their effort.  If it was just a matter of one server, I'd agree with you on that.
This may not even be anyone part of the Assist community.  They are spamming specific AA ports I use, but could be working a list off of Battletracker.  I'm seeing ports 8777 and 1716 (I don't use 1716) being spammed as well.  It may not even be an Assist providing the information.  But we do not use or need specific ip address/port information for connecting to servers anymore.  Assist handles that, so I would think it isn't needed anymore.

I don't know if these attacks are annoying anyone or not.  Apparently whoever is doing them doesn't much usage of the LOIC and they don't last long.  But, I have some ideas on making it harder for whomever is doing it to work harder doing it.

First thing I'd like people to do is look at the Assist server list and see who may be benefiting - who's left.  Maybe there's a douchebag trying to drive player traffic their way.  The other possibility is that somebody is just being a douchebag and has no interest.

I hate to go to this extreme, but I think I will have to pull server information out of Battletracker to keep IP and port information private.  Same goes for GameTracker and other similar sites as well.  These attacks are targeted towards AA ports using a known problem in the Unreal 2.5 engine.  I would ask that Assist remove both the IP information and Port information from the Assist client.  Individual users do not need them to connect anymore.  The information should stay private within the Assist client.
While some of us may not have the flexibility to change IP addresses, we do have the flexibility to change our ports.  And yes, I know technically a person can still get that information, but would have to go through a hell of a harder time to do so, especially with multiple servers.  I'd rather take the fun out of it for them.

new site looks great!
Couple of suggestions:

You are missing the favicon.ico in dist/imgs (or at least it's not showing in firefox). 
In case you need one, made one
Mobile browsers have a problem logging into the site, and this just isn't this look, it was the previous one as well.  Maybe the  divs (class brand) are stomping over the login ul block.  Nothing happens if you are able to press login.
Here is a screenshot in mobile (webkit)

That's exactly what I said you SHOULDN'T do. Assist runs on 2.5, but what I said was to use 2.8.5.

Never mind.  That's what it was, the 2.8.5 version somehow escaped my attention, as bad as it is   

is it tracked?

No.

That's what I did.
Went to start-> typed in ArmyOps.exe, found the version in Assist, opened that folder, went up a folder and dropped in Maps, then ran ArmyOps.exe and used the 'open' command.  'start OBT' doesn't work either