The part about coding bots to spoof the players isn't hard (in fact, doing such a thing has resulted in a few server owners getting banned from the server browser), but if they've created a bot that can actually function well in an environment heavily dependent on communication, Valve should be jumping all over them to improve their CS:GO bots.

StatusSpec 0.20.1 is now available, with some fixes and minor feature changes.

StatusSpec 0.20.0 is now available. Since 0.19.0, several changes have been made. It's recommended that people read the README to familiarize themselves with the changes (including changes from 0.19.1 and 0.19.2, which were released but not commented on here).

Over the past five months, StatusSpec has released 31 different versions within 469 different commits and now has 15 modules of functionality built in. I'd like to take a moment to thank everyone who's been involved, including bluee (for being a major influence with AdvSpec and offering a lot of help along the way), GentlemanJon (for working with me and making both of our plugins better), the production teams (for helping me to identify issues and to suggest new functionality), everyone who's taken the time to download the plugin and try it out for themselves (for helping me figure out how to make it better and more robust), and the general audience of competitive casts and the TF2 competitive community at large (which inspires me to work several hours a week to maintain and improve this plugin), and everyone else I've forgotten to specifically mention. Thank you for your support!

Well, it appears that Valve has reverted all of the changes that they've made, so this plugin is back up and running again!

StatusSpec 0.19.0 has just been released and includes a whole lot of changes. Read the changelog on GitHub and ask questions about anything you're confused about.

I've managed to fix quite a few of the issues that have cropped up. VGUI stuff is still broken, though, and as a result medigun info and some other modules are broken.

I hope to make a minor release soon which adds features and fixes everything else.

It looks like Valve has decided to break everything. This may be unrecoverable without an SDK update from Valve.

Confirmed broken, I haven't had a chance to look into a possible fix. It might be permanently broken.

Try verifying all of your content, and if that doesn't work, backup your stuff (demos, custom stuff, configs, etc.) and reinstall TF2.

If/when that doesn't solve the issue, we'll need to come up with a better way. Ideally you could compile a debug build yourself and then debug it to find the exact point of the crash, but that would depend on how much you want to solve the problem.

Can you investigate if the sniper zoom FOV changes based on fov_desired (as in a person with a lower fov_desired has a lower FOV when zoomed, and a person with a higher fov_desired has a higher FOV when zoomed)?

I might have a solution for fixing it, but it probably hinges on that detail.

You know, I investigated how to do this a long time ago and never found a good way to do it... and now I've discovered a simpler solution that can be implemented much more easily and will probably work.

Expect it soon.

I'll look into this, but I don't think this is possible that easily.

Yeah, I'll try to get that fixed. It's not intended.

Yeah, it appears this is just the map pool for ESEA this season.

Was anything else enabled when you crashed? Also, does the demo crash when StatusSpec isn't loaded, and does it crash when StatusSpec is loaded but with no modules enabled?

BLU: rgba(88, 133, 162, 255)
RED: rgba(184, 56, 59, 255)

As for dynamic meters, here's the file I gave to BLoodSire a long time ago:

"Resource/UI/MedigunInfoDynamicMeters.res"
{
	"Medi Gun"
	{
		"fgcolor_override" 	"173 223 255 255"
	}

	"Kritzkrieg"
	{
		"fgcolor_override" 	"246 96 171 255"
	}

	"Quick-Fix"
	{
	}

	"Vaccinator"
	{
	}
}

Hm... this might be difficult to diagnose, as I can't replicate any sort of crash.

Could you check that it doesn't crash when you load into insecure mode without any plugins at all?

CompCtrl 0.2.3 is now available. It's a pretty minor release, fixing issues caused by last week's update (that somehow didn't cause crashes but only weird behavior???), adding an experimental player ready HUD (currently untested - feedback would be appreciated), and displaying a message when an automatic team switch is scheduled before the next period starts.

I apologize for getting this update out late and any inconvenience it has caused, especially to ozfortress, which had trusted my work enough to test it out on their servers. I'm sorry that I let you down.

Good would be 100%+, I'm assuming, meaning that TF2 gets all of the CPU that it wants.

Nice to know that 16/38 = 42.1% is close to 25%.