Who we are
Anne is a player-run L4D2 community and site for server status, gameplay, stats, and team-up.
The community server has run for years; configs and plugins keep changing. The handbook only keeps practices that still work: copy connect to join, !xx in Anne co-op, count heads before Versus. Expired favorites and generic guides copied from the web do not belong in the body text.
This site is operated by independent community maintainers. It is not affiliated with Valve Corporation and does not represent Steam or Left 4 Dead 2. Game names and trademarks belong to their respective owners.
What this site provides
- Original gameplay guides, server command references, difficulty explanations, and update notes.
- Server status, player statistics, map records, and public ban information.
- Team finding, player reports, ban appeals, file downloads, and community sponsorship services.
Left 4 Dead 2 browser playtest
Explore official Left 4 Dead 2 campaign maps in your browser, with co-op play, special infected training, and spawn testing.
This community-made browser playtest is still being refined. Gameplay and collision behavior may differ from the original game.
Operating principles
We try to keep the servers stable and the calls fair. Rule changes and maintenance go in announcements, the guide, or the update log.
Public chat, nicknames, team notes, and report materials are user-submitted content. Administrators may hide, edit, or remove inappropriate content under the community rules.
How our content is produced
Gameplay and settings come from the current server config and plugin docs. Troubleshooting and report notes come from problems we actually hit. We don't mass-rewrite other sites.
Maintainers review the pages. A date means the config was checked recently. Links go to the Knowledge Base, command index, or a page you can use.
For each individual article the process runs like this:
- Decide which single concrete question it answers. One article, one question — "how to check a ban" and "how to write a report" are two articles, not one "community rules overview".
- Mechanical numbers are checked against the plugin source. Spawn timelines, distance bands, difficulty tiers — all verified in infected_control and the dynamic AI plugins before they go into the text. No second-hand claims from elsewhere.
- Modes and commands are checked against the current match config catalogue and the command index. A cfg that is not in the menu does not get written up; a command not enabled on the servers does not get listed.
- Map tactics are rewritten around this server's spawn rules. The route-learning guides for official maps found elsewhere do not apply here, because the spawn logic is different.
- Every article carries a publication date and a last-reviewed date. When configuration changes, we go back and amend the article and move the review date forward.
That is why some pages say "per the current config" or "go by what !xx shows". It is not a disclaimer but the truth: server configuration keeps moving, hard-coded numbers go stale, and a method you can run yourself does not.
Who writes this
The maintainers are a small group who have played on these servers for a long time and who also run the servers and the plugins. The people writing the handbook overlap with the people changing the plugins, which is why the mechanics articles can be written straight from source rather than summarised from feel.
That is also the biggest difference between this site and a general L4D2 guide site: what is written here is the configuration actually running on this set of servers, not general knowledge about the game. By the same token, the content here does not necessarily apply away from Anne's servers — we do not pretend it is a universal guide.
Plugin-level changes are recorded in the devlog, stating what changed and why. If you want to know when some number last moved, that is faster than asking.
What happens when we get it wrong
We do get things wrong. An article lagging behind a config change, a digit copied wrong, one server's special case treated as the norm — all of these have happened. When something does not match, tell us which page, which section, and what you actually saw.
After verifying we amend the text and move that page's last-reviewed date forward. Larger changes get a line in the update log. We do not quietly edit a number and pretend nothing happened.
What keeps this site running
Machines, bandwidth, relay routes and web hosting all cost money, and the money comes from voluntary player sponsorship. The community has no company behind it; the sponsorship tiers and what they grant are set out on the sponsor page, and the maintainers manage income and spending.
The site displays third-party advertising. The ads are unrelated to the articles and do not influence what we write or recommend — which config plays well and which route is stable has nothing to do with them. Cookie and advertising details are in the privacy policy.
Contact us
Contact methods and the report and appeal entries are collected on the contact page.