For your convenience, click here to be taken to that post.

With the Last Stand Update having just released, there's been a few issues and bugs that have cropped up. Rest assured, we've spent the past hours working on fixes in order to get them out as soon as possible.

The main issue of servers crashing appears to be related to the sudden influx of players joining the game while the servers are still in the middle of processing the update's new contents, as well as a discrepancy in some files that didn't update and sync properly.
The small dip in performance is due to the large amount of content we've added, all the vscript changes, map files, and everything else builds up and requires PCs to perform a bit more than before, but this is completely normal. The official servers are already sorting themselves out, and we'll have fixes in place soon.

As for other issues people have been experiencing, the vast majority are related to mods and add-ons, specifically the following:

- Mods that change the main menu UI layout. These will not list the Last Stand campaign or other UI changes by default, as the add-on author will need to update their .res files to support it.
- Mods that alter the sequence order. Also known as mods that alter character animations.
- Mods that alter scripts will cause the guns/items to break until they get updated. This applies specifically to the CS weapons and is why some people have been experiencing invisible guns.

In general; script mods, HUD mods, survivor mods and animation mods will need to be updated in order for them to be compatible with the update. The required changes for these mods are simple though, and shouldn't take long to implement.

Now, finding and fixing bugs isn't easy. Not only do the issues need to be documented, but we need to figure out how to reproduce each one reliably, then do it a couple times, try out dozens of variations to narrow down what might be causing it, and then finally figure out what exactly is causing it before being able to look into how it can be fixed.
Therefore, all the reports and info we've been receiving so far have been extremely helpful in locating and fixing issues, so thanks for all the support and reports!

- Don't use any add-ons or mods when testing
- Restart your game to prevent any scripts from taking place
- Play on an official, vanilla server
- Give as many details as possible in relation to the issue
- If you already know how to reproduce an issue, let us know each and every detail
- Console outputs can help us a lot! Make sure to check it after running into issues, chances are the console will say exactly what's going wrong.
- Use net_graph 4 in recordings and screenshots

As is the nature of QA, we investigate every report further and try to figure out the causes to the best of our ability, so don't hesitate to share all the information that you may have, even if you're letting us know that you haven't experienced a specific issue. It's likely that many of these are relating to already fixed issues, or are unrelated to the update, so figuring out all the details is always useful.
All information will help, whether it's console outputs, crashlogs, or just what you were doing before the bug happened - so even if the information seems menial or unimportant, include it anyway; The more details we can work with, the faster we can start fixing.
Thanks again for your understanding and support!

We're not always able to respond to each and every comment here or in the forum as a whole, but we read this thread and check in the various community hubs on a regular basis to document everything, so even if you don't see us around, rest assured we are keeping track of everything with a watchful eye.

If you'd like to proactively help out with the testing process, make sure to check out our Dev Thread for additional active discussion of issues and ideas.