Yeah, alright, we've fallen into the gimmick of Tracers (again). This time around, it's not just on snipers, it's on every gun; only when you fire ("modern" tracers).

You're a liar! I don't see any of these so called Tracers!
Good. If you haven't selected a tracer colour using sm_tracer, you won't see any tracers from anyone.

I selected a tracer; but now everyone has one!
Good. If you have a colour set, everyone else is assigned a random colour if they're not opted in (or their selected colour, if they are with the good).

I'm a Zombie and not everyone has a tracer anymore!
Good. If you haven't explicitly enabled your tracer, it won't be visible to zombies.

This is available to everyone, if you're a donor or not. The overhead shouldn't be that bad either, but if we start getting strange TE crashes, we're going to have to rethink this. Thanks to @Aprz for being the first consumer (verifying I didn't mess up the shared networking). As an aside, everyone looks like Predator with this enabled. I'm trying to come up with a portable way around this, but for the moment, pretend it's an Alien film.

Thanks to @Detonator for his thread and contributing ideas/code, we now have a party system (I believe in other FPS games they might be closer to Squads). A party is a group of people intending on working together. What a party allows for is for you to "Fly" (teleport) to your fellow group members before zombie's have a chance of turning on the map (using sm_pfly). There's also a party chat (sm_pchat, or Team Chat Key, $ Message) that you may use as well. As a reminder, all chats/actions are logged, so try to remain civil should you use this feature.

There's no protection against people joining random groups. All of your team members should have a common interest, staying alive. If you leak your party name to another user that you don't want in there, they're welcome to join your party and there's nothing you can do about it. Should this happen, you can create a new party (or join a new one) using the sm_party command. You may list current members in your party using the sm_plist command, if you're super paranoid.

You may automatically teleport to a per-round randomized leader for your group using the toggle sm_ptele. You may also leave a party at anytime using sm_pleave (or sm_party "").

Summary:
sm_party - Create a party, or join an existing party.
sm_pleave - Leave your current party.
sm_plist - View current members of your party.

sm_pfly - Fly to a fellow party-mate before zombies have a chance to spawn.
sm_ptele - Automatically fly to a fellow party-mate at round start (after buytime expires).

At the moment these commands are restricted to Donor+ only as we aren't aware of the impact that it could have on the server. We do intend on opening this up if all goes well....

We've been silently rolling out changes for a while. I think the oldest would be a refactor of NT, and the newest would be the Anti-Edging plugin I wrote last night and tested earlier this morning. There's a pretty significant change to AFKMan which will result in idle spectators (regardless of class) being kicked. There are also some older bugs with DamageDisplay, Announcer, and other plugins that were fixed (printing unsigned numbers as signed). Reserved slots should also have better functionality. ZR was updated to the main branch (when the VPK change happened), which resulted in some pretty serious regressions (crashing). While I believe it was fixed last night, please be vigilant and let us know if it continues. There's some freezing, but there are other reports out there that it's a regression from the VPK update. Obviously ZR isn't on MG, and some MG plugins aren't on the zombie servers, so this thread is basically a combination. I'd also like to request some information from you guys, is anything still busted that you use daily? If so, again, please let us know.

About a year ago when AceHigh was testing his Minigame's map (Moovie, or whatever typo it had), someone was kind enough to use a SourceMod exploit to flood the server, disrupting chat. I wrote an emergency plugin to work around the problem, since the exploit is in CPP and in a few base plugins. I made a few patches, but if they're not accepted into the main tree, it's pretty painful to deal with everytime we need to update SM (which is often). So that hack, workaround plugin became a permanent addition to the servers. This created a pretty serious problem, since it would catch legitimate players, resulting in many, many bans. The LSAs have been kind enough to review each case, and ban/unban...

We've updated our SM/MM:S to the official builds once again. The official builds include SDKHooks now, so that was an improvement. I do hope there's no fallout, but everything should mostly be back to normal (well, normal functionality should be, a few plugins are still busted). Thanks for your patience.

We're updating our SourceMod to 1.5 from an older 1.4...

Thanks for your patience!

Update: We're running SM1.5 on all of our servers now (No more mixture, I thought it wasn't, but it was). As well to this, I've been messing with SDKHooks quite a bit, the performance changes could be pretty damaging, not make a difference at all, or be a total win. It's really up to you guys to let me know, I don't think it would hurt anything, though.

It's that time again, we've synced with the official repositories and moved our kernel version up to the 3.6 series. The emulation layer (along with a bunch of other libs) were updated, so hopefully there's a performance win there. While we're expecting a CS:S update this week, it's possible it will be delayed again (probably forever ), so there may be more downtime ahead.

Our IPMI is down yet again, not allowing us to remote into our servers... All servers will be down except for the Web/Mumble/Database/Backup server.

Apparently after tech support looked at the screen, we have bad memory on SB1 so the downtime will be a bit longer. I'd estimate 15m of downtime, but it depends on when I get home.

Thanks for your understanding.

There's about 6~ months of rolling packages updates, so hopefully there's some improvement.

Hi guys,

The IP is: zego.plaguefest.com or 216.245.221.139:27015

Huge thanks to @Dharkk for doing some tedious work defining each map in GameModes_Server.txt and @CyphX for play testing.

Same-ish bugs as ZM. If you notice you're dying too quickly, check your class, you may be a human
^ While I'm adamant it's a CS:GO bug (Never saw it before Update 17) with GetTeamNumber (Getting the same crashes that CS:S does... lol), it's probably something I've done, or a bug I've yet to find in ZR.

Monumental thanks to the content porters/creators who've been churning out maps. Thanks again to Dharkk for compiling the map list, and making my life a lot easier.

Anyways, please report any bugs/suggestions you encounter/think of.
Thanks!

Thanks to GoD-Tony stepping up to the plate on AM, RadiusDamage should be nulled in FlameThink. I didn't fix this, but are there any problems with the hack?.

https://forums.alliedmods.net/showthread.php?t=188093

via https://www.youtube.com/watch?v=YdhAu5IEVVM&hd=1