[LordHotPocketHomicide]

Hello. I come here from a relatively popular Freak Fortress 2 community known as NecGaming, where I am a highly trusted Senior Admin/Co-Owner. We run two highly popular servers: one is regular FF2, the other is FF2x10. At least, we used to until Valve released yet another mod breaking update. This may end up being a long story, so please skip to the TL;DR at the bottom if you don't feel like reading it all.

It all started a very, very long time ago; January is when it first happened, I believe. The servers were alive and well, almost always being full. Then Valve released their first FF2-breaking update. It caused rounds to never start, regardless of how many players we had. After a few days, our owner found a temporary fix: typing autoteam into the console at the beginning of a new map would cause it to work perfectly until the map changed again, at which point we would just type autoteam into the console again. We did lose our custom weapons attributes to this update, but we were just glad the servers were fixed again.. After a month, almost everyone on the servers knew of this fix and we were prospering once again. However, about a week ago, when Valve released their update fixing this year's Scream Fortress, it broke things again in a way that we cannot find a solution for: it caused typing autoteam into the console to crash the server, thus setting us back to square one. TL;DR, we cannot get games to start because an update caused the games to never start, regardless of player count. Our only fix, typing autoteam into the console at the start of a new map, now crashes the server.

Does anybody know how to fix this? Our owner isn't exactly a coder, so all he could really do was "update a few things" (he never said what exactly it was that he updated). Any info is greatly appreciated. Also, it's not necessary, but we'd also like to know how to fix our custom weapon attributes.