I've never heard of that being possible. If I remember correctly, network variables have to be the same for all clients and the server.

That should be fixed soon... the current client beta is using the latest version of Chromium.

I think it was actually the game from the night before - most of wood pig has aliases on ESEA that don't match up with the aliases they're most commonly known as. That makes it confusing to understand which players are which, and the aliases are often unwieldy to the point where they are difficult to use in play-by-play commentary.

StatusSpec unfortunately isn't effective right now without premade configs.

There was a discussion on the issue a while back. Simply put, there is no completely accurate way of doing so, and most methods are generally resource-intensive.

It's also worth noting that streams are totally broken on mobile. I'm not sure if it's possible, but showing displaying something different (maybe just the link to the stream?) when it's a mobile device would be nice.

StatusSpec 0.17.0 is now available.

The only major change in this release was adding support for automatically retrieving player aliases from the ETF2L API. Unfortunately, no other leagues can be supported because they do not have an API, but if they do release one with the required features, I would be more than happy to add in support.

Check if your tf/scripts/items/items_game.txt has the text you're seeing in that KeyValues error, and if so, delete it and restart the game and see if it keeps having the same error.

This means that Invite teams can trade players even after the league-wide roster lock.

They still have to abide by the Invite roster restrictions, which for TF2 are:

• Invite rosters are limited to 6 starters, 3 backups, and 1 manager.
  
• Invite rosters are limited to 5 player additions over the course of a season. The beginning of the season starts at the end of registration.
  
• Invite players will be limited to two (2) Invite teams per season.

Spreadsheet went down, I assume it's being fixed.

Have you been using the Steam client when you get that error? In my experience, sometimes the Steam client just refuses to work for community-based things like trading, but using a web browser and trade offers works perfectly fine.

I don't think it's possible to stop the clock from running off during the beginning-of-round "freeze time" (mp_enableroundwaittime). You could try to mess with the end of round time (mp_bonusroundtime), where there isn't a round timer to affect.

However, in either case, the server clock (mp_timelimit) will still run in either case. It will always end time when it is that number of minutes past the map start time.

There's probably a way to hack around all of those restrictions, but that would require server plugins.

Not sure that anyone around here actually runs a server that's custom enough to require a plugin that's not already publicly available, so I'm not sure how much you could get there (from TeamFortressTV at least, you'd have a better bet on AlliedModders).

Stream assets, on the other hand...

StatusSpec 0.16.0 is now available.

This release contains minor (albeit breaking) changes for the MedigunInfo.res file. If you are using medigun info, you need to add a certain variable to each medigun meter. This GitHub diff shows the change more clearly than I can explain it. If you're still confused, I'll try to explain it as best I can.

The local player changes from yesterday are included. In addition, with suggestions from the one and only BLoodSire, I've added the feature to only display the item icon for the active weapon for the loadout icons module, and also the feature to change how the charge meter is displayed depending on the medigun (for example, having light blue for the regular medigun and hot pink for kritz).

As always, I need your feedback and suggestions to make this plugin even more versatile.

Consider it done for the next release.